There is a change to the way VMware VirtualCenter (VC) starts that could aid in situations where you need VC to fix an issue before you can boot Active Directory (AD) virtual machines. This really only comes into play if you do not have a phyisical AD server, but this is not all that uncommon an issue.
For example I recently needed VC booted while my AD server was not running. This was a requirement for enabling Enhanced vMotion Capability (EVC). How did I get around needing AD?
I simply added the following lines to near the end of the file C:\Documents and Settings\All users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg.
Prior to the closing </config> within the file add the lines:
Once this is entered into the vpxd.cfg file you can start VC even if your AD server is not online thereby alleviating the chicken and the egg situation.