Windows vCenter Server Service Fail Upon Reboot
Previously I mentioned I help one of my customer to reinstate back their Windows vCenter Server here. They have use the Windows Local Account to have the vCenter Server services started on instead of creating an AD service account.
Recently, they did a reboot of the Windows Server after a Windows update. The vCenter Server services was not able to start.
When using the vSphere Web Client, they got this error "503 Service Unavailable" similar to what is stated in this KB.
You might wonder what can cause a vCenter Server service with just a reboot. As stated in the KB, this can be due to the removal of permission to allow the account running the service with Log on as a batch job.
Do make sure when your Windows Server is joined to a domain, the rights need to be assigned explictly for this machine as your Group Policy can revert this if you are uncertain. Else create a service account to run the servce and ensure the permission is provided.
Comments