Comments on: Recovering a single Domain Controller from a USN Rollback

By: Ken Rudd

Ken Rudd — Fri, 25 Feb 2011 02:13:53 +0000

Worked like a charm on a 2008 DC. Note that, while this was the only DC in the domain, it was a child domain in a forest with a root domain and one other child.

This was the result of a Virtualization re-home

Woot, thanks again!

By: Paul Cunningham

Paul Cunningham — Sat, 12 Feb 2011 03:41:52 +0000

Justin, the title of this article is “Recovering a Single Domain Controller from a USN Rollback”.

There are no other DC’s in this scenario.

By: Justin

Justin — Sat, 12 Feb 2011 03:36:53 +0000

So after performing this procedure, your DC replicates again. However, you now have a DC in a state where is potentially has many objects or attributes missing from it. (and they won’t be replicated back because other DCs think this one is up-to-date) Some bad advice here… The quarantine put into place was meant to prevent the DC from replicating again for a reason.

By: Mirco

Mirco — Mon, 25 Oct 2010 19:15:18 +0000

Thank Thank Thank You
This Workaround saved my entire weekend…
My Family thanks.

By: Tarek

Tarek — Sun, 25 Jul 2010 12:47:47 +0000

Thank you ,Fixed my problems

By: Happy GoLucky

Happy GoLucky — Mon, 07 Jun 2010 18:05:05 +0000

You are a life saver! Fixed my problems and I’m back in business.

By: Michel Bitton

Michel Bitton — Sat, 22 May 2010 22:11:44 +0000

Thank you for this fix. I am dancing for joy since my DC running exchange 2003 server got messed up (twice actually) first by a hard drive failure and using a partition restore and a month later trying to migrate the physical machine to an ESX VMware server and I was greatly concerned by how to handle this.

May the schwarz be with you!!!!!

Michel.

By: Paul Cunningham

Paul Cunningham — Mon, 01 Feb 2010 23:09:51 +0000

Hi Dan, haven’t hit this problem with Server 2008 in the field yet so not sure how different it is, it at all. If you find anything out please let us know!

By: Dan

Dan — Mon, 01 Feb 2010 18:14:36 +0000

Have similar issue based on a dc snapshot restore on VMWare. See the key, however this is a Server 2008 Standard …anyone know if same applies…

By: Ryan

Ryan — Tue, 10 Feb 2009 18:56:57 +0000

Had this problem after restoring from snapshot an AD DC on VMWare.

Did all steps as stated and it worked. At first there was some replication errors but they got sorted out automatically.

Thanks!