Answered by:
differences Chrome vs IE

Question
-
Hi
i don`t understand why we have differences between access to central admin using google chrome or IE, for example to this page: http://sql:9999/configurationwizards.aspx.
As you can see for example google don't let us to configure servers.
please advise we follow the installation of Microsoft Sharepoint 2013 official page
Wednesday, November 21, 2012 8:44 AM
Answers
-
I will second what Trevor has said, in that some of the Central Admin functions make changes to the server and don't show up unless you "Run As Administrator". See the following blog post:
P.S. Please "Mark as Answer" and "Vote as Helpful" if appropriate.
- Marked as answer by JLSF Friday, November 23, 2012 9:10 AM
Thursday, November 22, 2012 4:37 PM
All replies
-
It looks the same to me (Chrome 23.x and IE 10):
SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP - 2012Wednesday, November 21, 2012 11:41 PM -
Hi
yes you are right the issue is not the navigator/explorer. I have two server farms i was using chrome on the server that host the Configuration web application and IE on the other.
so it seems a problem of accounts... but i really don't understand.
server1: host the configuration web app, logged as Domain\SP_Admin on the machine and as Domain\SP_Admin on chrome, not able to launch the configuration.
server2: joined later to the farm, logged as Domain\SP_Admin on the machine and as Domain\SP_admin on explorer, able to launch the configuration.
the installation process was:
install SharePoint on server1 using SP_Admin
install SharePoint on server2 using SP_Admin
launch configuration SharePoint application and creation of the farm using SP_Farm user as DBAccount/FarmAccount on server1.
launch configuration SharePoint application on server2 joining the farm, and everything next next next.
as i was not able to launch the web the configuration wizard from server1 i launch it from server2 and thats all
i check use sids on both serers and are the same as well as the security and groups membership.
how can i continue investigation? i´m afraid because accounts is so important to have a healthy sharepoint farm
Thanks
Thursday, November 22, 2012 9:10 AM -
Are these two servers part of the same farm, or separate farms? If you ran the browser from the server, did you make sure to select Run As Administrator?
SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP - 2012Thursday, November 22, 2012 3:52 PM -
Hello Both servers runs same farm In both cases I run the explorer as SP_Admin the user I use for the setupThursday, November 22, 2012 4:06 PM
-
But did you select "Run As Administrator" when launching IE if you're running IE from the SharePoint Servers?
SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP - 2012- Proposed as answer by Aaron Cutlip Thursday, November 22, 2012 4:37 PM
Thursday, November 22, 2012 4:08 PM -
I will second what Trevor has said, in that some of the Central Admin functions make changes to the server and don't show up unless you "Run As Administrator". See the following blog post:
P.S. Please "Mark as Answer" and "Vote as Helpful" if appropriate.
- Marked as answer by JLSF Friday, November 23, 2012 9:10 AM
Thursday, November 22, 2012 4:37 PM -
Hi Aaron
Thanks for the answer
yes i founded the Jerry bklog post about that, when i tried to create a web application and the new application ribbon access was disabled... but the thing is why in a client server environment as a browser access to the IIS application matter the user you are logged in? what really is happenning in the credentials exchange? or really UAC have some rol on this?
I hope someone have found a link or have the knowledge to explain what is going on the "backoffice"
If not i would check yours as answer :-)
Thanks
Thursday, November 22, 2012 5:09 PM -
This is all due to UAC. When you log into a Windows Server 2008/Vista or higher machine, even if you're in the Administrators group, you only have a User-level token. This is why you have to right click and run IE "As Administrator" in order to gain access to an Administrator-level token. Certain things in SharePoint Central Admin require Local Administrator rights, hence they're grayed out or missing if you don't elevate.
This is normal behavior.
SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP - 2012Thursday, November 22, 2012 5:54 PM