SharePoint 2013 – First Bug Found!

Firstly happy New Year, one of my resolutions is to blog more so here goes, first blog post of 2013! And its about SharePoint 2013!

Ok, ok I know the Vegas conference made SP2013 look like the best thing since 2010 but I have started using it and it seems like they are reverse engineering.

First remember, one of the most used features of 2010 was the ability to log in as a different user in the same browser session. Well the link has disappeared!

See here…

To get around the problem you could use different browsers, but if you are a methodical developer / architect like me, you will want to find a better solution

This “Sign in as Different User” menu item is very useful when testing sites, apparently it was purposely left out as it causes problems with opening docs in Office Web Apps like word etc.

You can add the menu item back in, on test or dev servers only though. To do this, repeat this edit on all servers in your SharePoint farm:

  • 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”














Save the File and Wala, your menu item may appear. But be careful, updates to servers in the farm may overwrite this. Perhaps Microsoft will correct the ‘issue’ in their service pack release!



Well done Microsoft, wait to go making developers lives harder, but you know we rise above it and we find fixes for your mistakes, which you subsequently include in your service packs releases and future releases, and you get all the money and we get nothing!


3 thoughts on “SharePoint 2013 – First Bug Found!

    • I’m not sure you can do this without, making a change to the resource file, which will probably be written over with SharePoint 2013 updates. If you really want to change the text maybe a custom navigation menu would be appropriate?

  1. Agree with Tenillebennett. Making changes to SharePoint’s own files is definitely not supported. But on a development environment it’s fine to do so. However, you can also create a couple of Shortcuts on your desktop to Internet Explorer and adjust the Shortcut’s target by adding “runas /user:domain\user” … My guess is that this option now has vanished has something to do with OAuth for Apps etc.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s