How to join vCenter to Domain?

[crescendas]

Some manuals from vmware said that vCenter required domain to function while some said that vCenter can function in workgroup without domain. Anyway, when I try to add the Virtual Machine installed where vCenter is installed on to the domain and reboot, I can no longer login to vCenter using the VI Client. the vCenter IP is also not pingable.

After logging in to the ESX host IP directly with VI Client, and access the vCenter VM to switch the network back to workgroup, I am able to access and ping the vCenter. Why is this so?

[Linjo]

To make use of AD authenication the vCenter needs to be a part of the AD, but its not a requirement.

The only reason I can think of that makes it block some things is if you have some Domain GPO:s that enables the local firewall, have a look at that.

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[geddam]

vCenter can be installed in Domain as well as workgroup topology. This is tested in our environment. This again makes a lot of difference on what type of environment you are @.

To answer your issue...

1. First a proper call should be made to install vCenter in Domain or Workgroup model.

2. As you have installed it in workgroup model and tried adding to domain...have you checked what do you get in vpxd logs...?

3. Most probably you should change your ODBC DSN connectivity...If you have SQL installed locally (Change SQL server from localhost\SQLEXP_VIM to hostname\SQLEXP_VIM....just the sever name not FQDN...) Again this applies to vCenter installed with SQL Exp locally.

4. Have you tried running a query for vCenter DB for fetching what vCenter Name it is taking...

5. Have you tried changing the service credentials for vCenter Server and Web management service to Domain authentication?

vpxd log will clearly state where is the problem...located in c:\Doc and Settings\All users\App data\Vmware\Vmware virtual center\logs

Thanks,,

Ramesh. Geddam,

VCP 3&4, MCTS(Hyper-V), SNIA SCP.

Please award points, if helpful

http://communities.vmware.com/blogs/rameshgeddam

[crescendas]

Hi guys, just to let you know that the vCenter issue has

been resolved. The vmware support found out that XP Client with SP3 will have

the firewall enabled with maximum security when joining to a domain. This result

in vCenter and even ping inaccessible. Disable the firewall or open the ports required by

vCenter (port 80, 443, 902) will resolve this issue.

Thanks for responsing!

Boon Hong.

[Linjo · Accepted solution]

Glad that it helped!

Please award points if apropriate..

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[crescendas]

haha... sure. I mark your reply as helpful... but have to mark it as answered since I can't mark my answer as answered.

[cdc1]

The same can be said for newer releases of Windows as well. Firewall configuration may need to be changed accordingly after adding a Windows system to a domain.

The network ports required for normal vCenter Server operation are documented in the official VMware docs (in the ESXi Embedded and vCenter Server Setup Guide, and guides for ESXi Installable and ESX too,) and also appear in a window during the vCenter Server setup wizard (in case you have to change any of them during the install.)

[crescendas]

Thanks.

btw, will the vCenter installation automatically add itself and open all the required ports on the Windows Firewall?