Note - I realise you shouldn't really be using IE locally on production servers. This is typically a "demo/dev box" problem
Everything is fine until you try to configure some services, and you find that a bunch of links have disappeared! In particular I spent a good 15 minutes working out why "Services on Server" had gone walkabout (for about 10 of those minutes I thought I'd gone mad and forgotten where it was).
You will probably have checked your permissions without any success:
- Are you logged in as an Administrator? (yes)
- Are you in the Farm Admin group? (yes)
- Have you tried rebooting? (yes)
- Turn off "Internet Explorer Enhanced Security Configuration" (IE ESC). This is a pretty standard task for most single server demo / development boxes.
- When starting IE "run as administrator"
If you are running Server 2008 R2 then it is a pretty simple task to just modify the IE shortcut in your taskbar / desktop to "Run as Administrator" and you are good to go.
If you are running Server 2012 though things are not that simple! Sure, you can set the same option, but it won't work (at least it didn't for me).
The only way I could get it to work was to browse to the IE 10 install directory (C:\Program Files\Internet Explorer\) and create my own shortcut to the iexplore.exe application.
I then set that shortcut to "Run as Administrator", pinned it to the taskbar and voila! success!
Just another one of those Windows Server 2012 quirks to get used to I guess...
If you have found an easier / quicker way to do this .. then please let me know in the comments!
This was really bugging me. It also affected my ability to add users to the farm administrators group.
ReplyDeleteThanks so much!!
Its really awesome help by your post.. Thanks
ReplyDeleteSandeep Parandekar
http://www.parandekar.blogspot.com
Great Workaround, thx a lot!
ReplyDeleteFrom Server 2012 if you pin IE to the Task bar you can then right click on IE to display some option. One of which is IE. Clicking on that gives you the option to Run As Admin.
ReplyDeleteAnon,
ReplyDeleteYes, but I didn't want to have to do that every single time I ran it
very useful. thanks!
ReplyDeleteThere is a typo in psconfig invocation: should be "psconfig.exe -cmd create configdb [...]" instead of "psconfig.exe -create configdb [...]"
ReplyDeleteerm .. are you commenting on the wrong article ? :)
ReplyDelete