Upgrading 2008R2 domain controllers to 2012R2 DCs with mismatched USN's

I've read through other people's Q&A about upgrading from Windows Server 2008R2 to 2012R2 and seem to have the basic upgrade process down.  My unique situation deals with Update Sequence Numbers not matching on our two domain controllers.  I made the mistake of creating a vSphere snapshot on a DC and restoring it a while back.  I found out later that is a no-no but, it was too late.

My question is - do I have to fix the USN mismatch problem before attempting to do an across the wire DC upgrade on two new server VMs?
volleyguyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
the problem is domain controllers suffered with USN rollback (2095 event id  - directory service) cannot replicate with any DC and hence must be demoted

So the question is, do you have only these two DCs which are problematic or you have other DCs as well?

If you have other working DCs, demote these DCs and then promote new version DCs

If these are only two DCs and both in issues, you must restore AD authoritatively / natively  on one of those DC if you have good AD system state backup before this issue occurs, ensure its working fine and then go for new AD version promotion
But obvious, you need to demote other faulty DC
0
volleyguyAuthor Commented:
Moderator - I replied to Mahesh but, it's not posted.  Did I reply incorrectly?
0
MaheshArchitectCommented:
In the same window you need to post comments so that it will be reachable to everybody part of thread
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

volleyguyAuthor Commented:
Sorry for the delay Mahesh.

I actually have three domain controllers and they all don't match each other.  Before I demote, how do I tell which one is the good one and which two are faulty?

I don't know when this happened so, I don't have a good backup of the good DC's system state.
0
Shaun VermaakTechnical Specialist/DeveloperCommented:
Keep the one that is running the PDCe role
0
volleyguyAuthor Commented:
I ended up contacting Microsoft and they checked the registry entry for USN rollback.  The primary DC was the only one that had the registry key marked so, they demoted the primary and re-promotoed it.  It took some time since other areas needed to be checked, such as AD Sites and Services.  Took about 1-1/2 hours to fix.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
volleyguyAuthor Commented:
Suggested solutions did not solve my problem.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.