HOWTO Start the SharePoint 2010 Central Administration Service with PowerShell

I have two web front-ends in my SharePoint 2010 farm with Central Administration running on one of the front-ends. I was having some serious performance problems on the Central Admin-enabled server and wanted to start Central Admin on my other server. The Central Admin service is installed on all web front-ends by default, but is only enabled and started on machines you select.

The following PowerShell command will provide a list of all servers that have the Central Administration service installed, their status, and the Id (GUIDs have been changed ;):

Get-SPServiceInstance | Where-Object {$_.TypeName -eq 'Central Administration'}

TypeName Status Id
——– —— —
Central Administration Disabled 5E1FEB60-87FB-4CDB-9E2E-B8607F003C90
Central Administration Online 390085E6-009F-44E5-B6F7-8FD46CCB103F

I can now focus on just the web front-end with the Disabled Central Administration service by using the Id with the following:

Get-SPServiceInstance | Where-Object {$_.Id -eq '5E1FEB60-87FB-4CDB-9E2E-B8607F003C90'}

The service instance can be started using the following PowerShell command, again restricted to the Id of the service instance I want:

Get-SPServiceInstance | Where-Object {$_.Id -eq '5E1FEB60-87FB-4CDB-9E2E-B8607F003C90'} | Start-SPServiceInstance

This will start provisioning the service instance (note the Status below says “Provi…”), which usually means creating the Central Administration website on the web front-end and starting the central admin service instance:

TypeName Status Id
——– —— —
Central Administration Provi… 5E1FEB60-87FB-4CDB-9E2E-B8607F003C90

You can check the progress by continually entering the previous powershell command:

Get-SPServiceInstance | Where-Object {$_.Id -eq '5E1FEB60-87FB-4CDB-9E2E-B8607F003C90'}

until you hopefully get the status as Online:

TypeName Status Id
——– —— —
Central Administration Online 5E1FEB60-87FB-4CDB-9E2E-B8607F003C90


2 Responses to “HOWTO Start the SharePoint 2010 Central Administration Service with PowerShell”

  1. dimokrat Says:

    Thanks! You saved my instance 🙂

    The only thing I now trying to understand is how to transfer this role from one server from the farm to another. If I just enable it on a new one and disable on a current, it leaves me without access to it either on old or on a new one.

    • gavinmckay Says:

      Do you want to transfer the Central Admin role to another server? It’s *reasonably* straight-forward. The CA role can be installed on all sharepoint servers without issue – the trick is that the *last* server the CA role is installed on becomes the default CA role. So, if you have CA on server1, installing on server2 will make it the new CA role. If you then want server3 to be the CA role, simply install on server3.
      There is a registry entry on each server that sets the URL for the CA location. You can change this manually, but obviously updating registry/take care/don’t break/backup server etc etc 🙂 I have the CA role installed on multiple servers, so if one CA drops out you can just manually connect to another by typing in the URL for the CA on a different server.

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

%d bloggers like this: