Yes I know it’s not recommended as stated in the KB (vCenter Best Practice) but due to unreasonable request from my user, I have no choice but to test whether it is possible to let vCenter service running on domain controller machine. As suggested elsewhere, I have to install vCenter application first before I can dcpromo the machine. So the process can be summarized as below :
- Prepare the machine
- Install vCenter
- Change vCenter ADAM port
- Run dcpromo
To test this out, I’ve created one VM running on VMware Workstation 7 and install it with Windows Server 2008 R2. Once finished, I proceed with vCenter 4.1 installation and use SQL Express as for vCenter database. The installation finished as expected and vCenter service can running fine without issue.
Now, I need to change vCenter ADAM. Since AD Ldap will use port 389, to avoid port conflict, ADAM port must use other than port 389 (3899). To do this,
- Open CMD and run c:>net stop VMwareVCMSDS
- dsdbutil:>activate instance VMwareVCMSDS
- dsdbutil:>LDAP port 3899
- dsdbutil:>SSL port 6369
- c:>net start VMwareVCMSDS
To verify that my vCenter ADAM now is using port 3899, I’ve checked it with c:>netstat -an. To make the changes permanent, I’ve modified instance.cfg (Windows Server 2008 R2 C:\ProgramData\VMware\VMware VirtualCenter) and change port 389 to 3899. Then, restart the server and verify your vCenter service is running fine.
From now on, you can proceed with dcpromo. Although I will not discuss it here, you can always refer to this site for how to install your first domain controller.
p/s : This is not supported by VMware at all.
3 Comments so far
Leave a comment