Greetings
I have had some considerable struggles with installing vCenter 5.1 within infrastructures that are not part of an Active Directory domain. The root of the problems seem to be the ability for vCenter to restart after the server rebooting.
I've done some online research and followed suggestions in a few articles, but still cannot resolve the issue. I cannot imagine that vCenter is completely dependent upon a domain?
I've thought perhaps I can create a bogus FQDN and map it in the server's host file.
Has anyone successfully setup 5.1 on a "domain-less" Windows OS? Was this a cut & dry install or was there workarounds required?
Any info from the community is appreciated...
~grc