Problem with vCenter 5.1(W2K8) & SSO without AD

[John_Balsillie]

Hi all,

I am having problems with my first experiences with vC 5.1 / SSO. I have a vm running W2K8 + DNS but no AD. That's what I want and need. 5.0 had no problem with this but with 5.1 I cannot get all working.

Installation of SSO, Inventory service and vC (all 5.1) all work fine and all associated services start. However, when I then restart the vm, the vC service will not start, all other services start just fine but not vC. It started during the install runtime session, but not after a vm restart. Default install options of using SQL Express dbs for SSO and vC were taken.

vpxd.log has a relevant error of:

“Failure while trying to connect to SSO Admin server: No connection could be made because the target machine actively refused it”.

DNS is fine, forwards and backwards. Despite the warning (attachment), SSO is happy to install without AD present.

I do not understand why vC would run post install but then fail to start post reboot.

Surely vC (Win) 5.1 does not have to be in an AD domain?

What am I missing?

Thanks and Regards,

JohnB

[maxxam204]

I may have spoke too soon regarding Update Manager.  After a reboot of my vCenter server, now my Update Manager plugin is failing to load.  After some testing it looks like Update Manger is failing for the same reason vCenter Service was failing.  I have now set the Vmware Update Manager service from Automatic to Automatic (Delayed Start) and then rebooted.  After the reboot my Update Manager service is now starting and the plugin is enabled without error. Phew.