VMware Rollback Causes Server 2003 DC Replication to Fail:

By | May 19, 2010

After installing an update to a DC that happens to be in VMware vSphere the update failed. So, I had to rollback to the snapshot I just took.

after rolling back Replication to other DCs failed. In the Event viewer I found:

NTDS General Errors 1113, 1115, and 2103
NTDS KCC Errors 1308

The problem seems to be that AD replication gets disabled after the VMware rollback and the Netlogon service has been Paused.

 

So after much searching and reading and a server reboot I discovered that replication had been disabled by the USER!

I am sure I didn’t disable anything!

So here is the fix:

  1. Install Server 2003 Support Tools:

http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&displaylang=en

  1. Start the Netlogon service as it is probably paused
  2. Make sure that the DNS serial number under properties is the same as your functioning DCs. You can do this by opening the DNS Admin Tool (msc) under Start>Programs>Administrative Tools>DNS on the DC
  3. Open your Forward Lookup Zone
  4. R-Click on your Domain (should be something like MyDomain.com –or– MyDomain.local)
  5. L-Click on Properties
  6. The “Serial Number” is located on the SOA Tab (Make sure they are the same number between DCs Hint: Never roll back numbers always go to a higher number if needed.)
  7. Restart DNS Service
  8. Restart the Netlogon Service (Not sure if you need this, but I did it.)
  9. Open a Command Prompt
  10. Go to where the support tools are installed (usually c:\program files\support tools)
  11. Type in: repadmin /options -DISABLE_OUTBOUND_REPL
  12. Hit Enter
  13. Type in: repadmin /options -DISABLE_INBOUND_REPL
  14. Hit Enter then close the cmd prompt

After this replication should be working again!

  1. Lastly, check the Registry value “HKLM\System\CurrentControlSet\Services\NTDS\Parameters, “DSA Not Writable” (REG_DWORD) and its value is 0x4.
  2. Delete “DSA Not Writable” (REG_DWORD) from registry and reboot the server.
  3. Reboot your server! DONE!!!

Leave a Reply

Your email address will not be published. Required fields are marked *