Yes, when it boot's after migration, VMWare adds a virtual nic and Windows hides the physical nic that was in the DC before. However, references to it are still present.
And the virtual nic that VMWare adds, is a DHCP assigned. So that is interesting, a DC/DNS server which had a static IP, boots up with a DHCP assigned adress (if available) and of course, that means the DC can not query the DNS server on itself to locate AD.
I did this one time without knowing of it at that time, but I eventually i got it right, when I set a static IP on the virtual nic and rebooted.
The dcpromo on a new server and then migrate the FSMO roles is a much cleaner way to do it.
Main Topics
Browse All Topics





by: WraithbonePosted on 2009-11-03 at 10:09:15ID: 25731720
to do this i would create a new AD, and use dcpromo to promote the new ad when its done replicating.
ervice/mic rosites/se arch.do? cm d=displayK C&docType= kc&externa lId=100699 6&sliceId= 1& docTypeI D=DT_KB_1_ 1&dialogID =7548984&s tateId=1%2 00%2075521 77
if you insist to convert it take a look here: http://kb.vmware.com/selfs