We ran into the same issue with a few DC's we virtualized. We eventually had to rebuild them clean in the VM environment. Also another tidbit if you are using DRS set the DC's and Exchange servers to Manual, we had issues with replication once they started getting moved around.
This case cannot be fixed because every DC has its own id associate with the server hardware; like you can't clone the DC from one machine to another one. What MS and VMWare recommend to start a clean install, promote it to DC and start you wrok.
Thanks for you reply mate.
I understand what you are saying with the ID's created between Software and Hardware, for i have also heard of issues with replacing motherboads and network cards in domain controllers to find that AD no longer functions correctly.
However, my recently converted Exchange Domain Controller is working perfectly.
I did have to enable replication as stated above, but also ensure my DNS settings were correct and restart my NET LOGON service before DCDIAG gave me a clean bill of health.
Im to migrate yet another DC in the comming weeks. So I will keep you posted how it all goes.
We had a similar issue. After doing a physical to virtual migration, AD replication was working fine, however, file replication was not. It appears that the issue is with hardware / software signatures. I was able to resolve with the following microsoft article: _
http://support.microsoft.com/kb/925633/en-us
_
I feel calling this a problem is the wrong term. One should never P2V a DC always dcpromo ![]()
I don't recommend a p2v on DC's
Actions
More Like This
- Retrieving data ...








