NetLogon paused after restart

I have a 2008R2 server that pauses NetLogon after a reboot.

I have found the following in the event logs:

Event 2103 - Directory Service
The Active Directory Domain Services database has been restored using an unsupported restoration procedure.
Active Directory Domain Services will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.

My Scenario is one server 2008R2 PDC

History is:
2003 PDC plus 2008R2 BDC
2003 PDC removed from LAN and 2008R2 promoted to PDC

I have read a number posts on this topic and most refer to a USN rollback. Where the AD database is out of sync with another DC however I only have one DC on the LAN.
Ethan DarwinAsked:
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.

Yeah, that does sound like a USN rollback. Was the 2008 R2 DC recently restored from a backup made using a non-AD-aware backup application?

Also, you're right in saying that it shouldn't matter when there's only one DC in the domain. Are you certain that the 2003 DC was demoted properly before being taken offline?
Ethan DarwinAuthor Commented:
Yes 2003 was demoted correctly.

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
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

I've never run into this situation myself with a single DC, so I've never tried that procedure, but the comments show that it has worked for a number of people. I say go for it, but only after you're sure you've got a good backup of the DC.
Ethan DarwinAuthor Commented:
Interestingly the following post says "Don't do it". Having said this it also states this will never happen in a single domain forest.

I wonder if there are some remaining ghosts and AD still thinks there are other DCs in the forest.

Is there a simple way to check if AD is still trying to contact the ghosts of DCs?
I agree that it shouldn't be done if there's more than one DC in the domain, but since that article makes the assumption that it'll never happen if there's only one DC, I don't think it really applies here.

You can go through the initial steps of an old-school metadata cleanup to see if the DC believes there are other DCs in AD. If step 12, list servers in site, shows only the one DC, stop the process there, as there aren't any other DCs to remove.
Ethan DarwinAuthor Commented:
This issue was discussed previously in the linked post and resolved the problem perfectly.
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
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.