vSphere 5’s vCenter 5.0 now automatically configures the VirtualCenter Server service with “Delayed Start” and SQL dependency

For those who have come across problems mentioned in 2 of my previous blog posts:

vCenter / Virtual Center Service fails to start with event ID: 1000, 7024, 7001, 18456 http://terenceluk.blogspot.com/2010/07/vcenter-virtual-center-service-fails-to.html

Addressing the VirtualCenter service not starting because SQL service hasn’t started yet
http://terenceluk.blogspot.com/2010/07/addressing-virtualcenter-service-not.html

… would be familiar with the issue of collocating SQL server and VMware vCenter on the same server where the vCenter service fails to start because the SQL services hasn’t started yet.  While deploying a few small nodes with vSphere 5.0, I noticed that the vCenter installation process actually puts the SQL service as a dependency for the vCenter service and also sets it as Delayed Start.  This is definitely a nice touch.