VMWorld
4 Replies Last post: May 23, 2008 8:07 AM by hazent  
Click to view Stephen's profile Apprentice 7 posts since
Dec 9, 2007

May 11, 2008 6:40 PM

Converting Domain Controllers to VM - Issue Found!


Hello All

I have just recently converted our exchange server to VM using VMware Converter 3.
In doing so I had noticed in my event logs under Directory Services that my exchange server (DC) was no longer able to replicate Active Directory with corrosponding DC's.

I ran DCDIAG and it had informed me that my replication services for INBOUND/OUTBOUND were disabled.
As a result i ran the following two commands to correct my problem:

repadmin /options -DISABLE_OUTBOUND_REPL
repadmin /options -DISABLE_INBOUND_REPL

I have ran several tests and all appears to be working fine.
has anyone else had this issue? If so do you know what causes this?

Regards

Stephen


Click to view Ryan Marsee's profile Candidate 1 posts since
May 12, 2008
1. May 12, 2008 5:49 AM in response to: Stephen
Re: Converting Domain Controllers to VM - Issue Found!
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.
Click to view Michael Tsang's profile Candidate 2 posts since
May 21, 2008
2. May 21, 2008 9:36 PM in response to: Stephen
Re: Converting Domain Controllers to VM - Issue Found!
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.
Click to view hazent's profile Candidate 4 posts since
Sep 10, 2007
4. May 23, 2008 8:07 AM in response to: Stephen
Re: Converting Domain Controllers to VM - Issue Found!
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

_