none
Central Administration Site on all Farm Servers

    Question

  • Hi,

    We have SharePoint 2013 Enterprise with Sep 2016 CU Patch in Farm with 4 Servers

    While running the SharePoint Products Configuration Wizard, we have left the default option of Central Admin to be hosted on that server as it is.

    Now, when we browse the Central Admin with each server's URL it works but we have observed that Database Status report differently for each Server's Central Admin URL.

    Should we keep Central Admin only in one Farm Server as best practice and remove the others or is that mandatory to have Central Admin on all Farm Servers ? Kindly advise.

    P.S. The Central Admin accessed by remaining Server URL's never used and remains idle.

    Thank You!

    Azhagiri Jayaram Yadav

    Tuesday, April 11, 2017 5:02 PM

All replies

  • Hi Azhagiri,

    A SharePoint Farm only have a Central Administration Website, but it can host on multiple servers.

    In general, hosting the central administration website on one server is enough. We can host it on multiple server when we want to improve the farm’s performance and reliability. For instance, If for some reason you are unable to connect to the Central Administration Web site on one server you can use the other server to manage your SharePoint server farm.

    So it’s available that keep central administration site on one server or multiple servers, it depends on your requirement.

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, April 12, 2017 7:36 AM
  • Hi Grace,

    Thank you for the information.

    In our case, the problem is Central Administration URL for Primary Server where it is hosted reports all Database Status as "No Action required" whereas in the Secondary servers their respective Central Admin URL's report some Database's Status as "Database is updated but some sites are not completely upgraded".

    We can see a clear difference between the Primary Central Admin URL and other Server's Central Admin URL's in reporting Status about Farm Content Databases.

    What would be the solution for all Central Admin's to report in a uniform manner ?

    Thank you!

    Azhagiri Jayaram Yadav

    Wednesday, April 12, 2017 4:51 PM
  • You can add the Central Administration site to other servers in the farm if you want or need high availability for this site. It is not mandatory to run on all servers in the farm.

    Wednesday, April 12, 2017 5:07 PM
  • Hi Azhagiri,

    Have you already install CU and run the SharePoint Products Configuration Wizard on all servers in SharePoint farm?

    If not, please do that and view the database status again.

    If yes, using PowerShell commands in the article below to find out what causes this error on Secondary servers.

    http://www.softvative.com/blog/2016/04/database-is-up-to-date-but-some-sites-are-not-completely-upgraded/

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, April 13, 2017 2:10 AM
  • Hi Grace,

    Thank you for the update.

    We have completed running the Option1 > PSConfig Wizard and it is successfully completed on all Farm Servers.

    We will execute the solution given in the article on all Farm Servers including Primary and Secondary asap and update here the outcome about problem Secondary Central Admin URL's and Farm.

    Best regards,

    Azhagiri Jayaram Yadav

    Thursday, April 13, 2017 3:33 PM
  • what is the outcome after running config wizard? it should fix the issue.

    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -Waqas Sarwar(MVP) Blog: http://krossfarm.com

    Thursday, April 13, 2017 4:03 PM
    Moderator
  • The outcome of Config Wizard was successful on all Servers before the actual issue and still Database status remain as I highlighted in Secondary Central Admin URL's.

    As a next step we will execute the steps in the article on a preferred date in QA and will update here.

    Best regards,

    Azhagiri Jayaram Yadav

    Wednesday, April 19, 2017 3:40 PM
  • Hi Azhagiri,

    Is there any update?

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Sunday, April 23, 2017 9:50 AM
  • Hi Grace,

    While we executed the Steps in the article below last week, we got to know that status in the "localupgradestatus" is giving "CANNOT UPGRADE" in our case whereas the article gives inputs for "NEEDS UPGRADE"

    http://www.softvative.com/blog/2016/04/database-is-up-to-date-but-some-sites-are-not-completely-upgraded/

    The Databases / Sites that Cannot be upgraded are SharePoint 2010 version Databases/Sites hosted inside SharePoint 2013 Enterprise environment.

    For this "CANNOT UPGRADE" issue, we followed another new article with URL below.

    http://sharepointfordummies.blogspot.in/2015/08/sharepoint-2013-returns-to-upgrade.html

    After we executed the below Powershell command given in new Article aforementioned for the sites that CANNOT UPGRADE we got back the same result "Sites cannot be upgraded" for these SharePoint 2010 based sites.

      Upgrade-SPSite https://mysite.sharepoint.me/sites/myname -versionupgrade

    Your inputs for this will be helpful.

    Thank you!

    Azhagiri Jayaram Yadav


    Tuesday, May 02, 2017 9:35 AM
  • Hi All,

    Any updates on the last outcome ?

    Thank you!

    Azhagiri Jayaram Yadav

    Friday, May 05, 2017 8:44 AM
  • Hello Azhagiri,

     As a best practice and for redundancy you should host the central admin site on 2 servers.  Setting that on all servers certainly is not required. 

    For the current problem you may remove it from all servers that has issues by running the PSConfig wizard and unchecking the "central admin site" in adcanced tab, this would remove the site from the server on which PSconfig has been executed. Just keep it running one server.

    YOu may launch PSConfig again and enable central admin site back on the server you need it. 

    Hope this helps. 

    Faisal


    Faisal

    Friday, May 05, 2017 1:40 PM
  • Hi Faisal,

    Thank you for the inputs.

    Any ideas with respect to the "localupgradestatus" giving "CANNOT UPGRADE" for SharePoint 2010 Databases in our SharePoint 2013 environment.

    Thanks in Advance.

    Azhagiri Jayaram Yadav

    Monday, May 08, 2017 1:17 PM
  • Hello Azhagiri,

    Which database\component are you getting that error on? 

    Have you installed the update on all servers connected to the far and ran the PSConfig startng from the server that has the Central admin installed? If not please do that. If that s already done, which server are you getting the error?

    In case the error is for a content database, try detaching the database from the farm and then run the PSConfig and then attach the database back again using powershell. 

    Please also send the logs.

    Regards

    Faisal


    Faisal

    Monday, May 08, 2017 5:32 PM