Add Sign in as Different User to SharePoint 2013

-
This “Sign in as Different User” menu item is very useful when testing applications, but it can lead to problems especially when opening documents, say in Microsoft Word. So, it may be for these reasons that the option has been removed in SharePoint 2013.
                                

Steps
  • Locate the file \15\TEMPLATE\CONTROLTEMPLATES\Welcome.ascx and open in a text editor.

  • Add the following element before the existing element with the id of “ID_RequestAccess”:
<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"
 Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"
 Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"
 MenuGroupId="100"
 Sequence="100"
 UseShortId="true"
 />


Comments

Post a Comment

Popular posts from this blog

[SOLVED] The SharePoint Timer Service service terminated unexpectedly. Event ID : 7031

-
Image
The SharePoint 2013 Timer service terminated unexpectedly.  It has done this  34  time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service Login Name : System Source : Service Control Manager Event ID : 7031 Level : Error                                    Keywords : Classic User : N/A                                       Computer : MyDomain If you are getting above error. Try to do the following steps  1.  Clearing the configuration cache Stop the Sharepoint timer service Go to C:\ProgramData\Microsoft\SharePoint\Config\*GUID Back up Cache.ini Delete all the .xml file ( Do not delete the Cache.ini file ) Open Cache.ini (Edit with Nodepad) Replace the contents with the number 1 and save the file...
Read more

FIX : The password supplied with the username Domain\Username was not correct. Verify that it was entered correctly and try again.

-
Image
This will happen often while trying to create a new web application in SharePoint 2013 central administration site. It gives the following error This usually occur when farm account password is expire and it's password is changed or simply farm account password is changed. In that case, sometimes password stored in SharePoint database is different in Active Directory, so unable to create web application from central admin.  In order to resolve this problem you need to update SharePoint 2013 farm credentials using "STSADM" tool. For that Open PowerShell in administration mode then write the following code stsadm -o updatefarmcredentials -userlogin <UserAccount> -password <New-password> Example : Once you receive operation completed successfully message do a IIS reset !! FYI : In case if you getting an error message " stsadm not recognized as an internal command " Follow these instructions.. Happy Coding !! ...
Read more

FIX : stsadm is not recognized as an internal command

-
Image
If you try to run SharePoint STSADM.exe in powerShell and getting this error To resolve the error message you need to edit the profile.ps1 file Its located in C:WINDOWS\SYSTEM 32\WindowsPowerShellL\v1.0\ if the profile.ps1 file dose not exists, just create a new file and add the following code Set-Alias -Name stsadm -Value $env:CommonProgramFiles"\Microsoft Shared\Web Server Extensions\15\BIN\STSADM.EXE" Happy Coding  !!!
Read more