Running a MS Domain Controller in Vmware

[GFFG]

Hi I have a clustered Vmware 3.5 setup with a physical Vcenter 2.5. Everything is up to date.

All ESX server's have their Time sync properly to an outside source.

Intenally our Windows 2003 domain has all Netapp appliances (shared storage for vmware) and other DC's pointing internally to an existing dc which serves as the TIME SERVER. That Server points to the outside for it's time source.

I want to create a new win2k3r2 server in Vmware and run dcpromo on it.

Q: Any concerns I should know about ?

Q: Does Vranger network backup work just fine with a DC versus any other VM when backing up? (it's on NFS)

Q: Can you vmotion a DC just fine and the Microsoft machine won't complain?

Q: Can you move from one network to another on the fly and it won't compain?(specifically change from one network label to another)

[jbruelasdgo]

1- basically, the time of the machine, try to synchronize to external source (if the ESX are synchronized in time, you can use VMware tools to do the task)

2.- it does what it has to do

3.- you can vmotion it

4 - I do not think you can change the network on the fly, the DC will complaint in this case (you are talking about virtual switches right?)

regards

Jose

[GFFG]

1 - Since microsoft has its own time service running, I can't see why anything really needs to be done - vmware tools default is to not sync time with the vm and ESX,correct ?

If ESX time service is running and pointing externally the chances gotta be really rare that ESX and the VM's time would be off, since all pc's point to external?? I think I have a good handle on this?

Bottom line every machine should be pointing to a trusted time source so time drifting does not occur.

4 - I changed another vm from V-switch to another and no issue...that I know of. must of notified phsycical switch of change immediately

[GFFG]

I checked the event log of the server and it shows itself connecting to another DC for time sync...So I think I'm in good hands. I think the old days when time esx was in 2x stage there could be time drift issues.

[TomHowarth]

the only DC you need to worry about for time source issues is the one holding hte PDC emulator role. all other DC's will use that one as the trusted and authoritive time source by default. this is what Windows time it :smileygrin:

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "VMware Virtual Infrastructure Security: Securing ESX and the Virtual Environment”.

[TomHowarth]

1 - Since microsoft has its own time service running, I can't see why anything really needs to be done - vmware tools default is to not sync time with the vm and ESX,correct ?

be careful, and verify. I got burnt with a Win2K8 DC, admitidly it was the DC holding the PDC role. royally screwed up Kerberos :smileygrin: lucky only a test environment. LOL

If ESX time service is running and pointing externally the chances gotta be really rare that ESX and the VM's time would be off, since all pc's point to external?? I think I have a good handle on this?

that is correct.

Bottom line every machine should be pointing to a trusted time source so time drifting does not occur.

Time drifing will occur but not significantly enought to cause an issue

4 - I changed another vm from V-switch to another and no issue...that I know of. must of notified phsycical switch of change immediately

you should have and no issue other than a loss of network until you changed the IP address (if required)

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "VMware Virtual Infrastructure Security: Securing ESX and the Virtual Environment”.