SharePoint 2010 : Use PowerShell to Provision a Central Admin Site

is only enabled on the machines that you identify. I went ahead tried to run the psconfig on the server and tried to re-add it, however the install checks were telling me that it could not be joined due to a patch level inconsistency (more on that in a different post). End result was that I was sitting with a farm that did not have a Central Admin site configured…

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

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

TypeName Status Id
——– —— –
Central Administration Disabled 2d35f287-8d0f-4474-8a38-2dc2365c06e7
Central Administration Disabled 2052cc79-fce8-483a-83e4-9802db535237

The service instance can be started using the following PowerShell command, again restricted to the Id of the service instance I want. Doing this will provision Central Admin on the WFE that it correlates with:

 

Get-SPServiceInstance | Where-Object {$_.Id –eq ‘2d35f287-8d0f-4474-8a38-2dc2365c06e7’} | Start-SPServiceInstance

 

Get-SPServiceInstance | Where-Object {$_.Id –eq ‘2052cc79-fce8-483a-83e4-9802db535237’} | Start-SPServiceInstance

This will start provisioning the service instance, which usually means creating the Central Administration website on the web front-end and starting the central admin service instance. Given a minute or two, the Central Admin will appear on the WFE and can be accessed using the normal http://<machine name>:<admin port> standard.