Unable to bring 2012 R2 DC up in Hyper-V replica test failover scenario

We've just setup Hyper-V replica for most of our servers over to a DR site.  First server I tried to bring up was our domain controller (FSMO master, 2012 R2.)  We DO have other domain controllers, but wanted to make sure this solution also worked (As it should and has tested fine in other scenarios.)

We did a test failover, created a private NIC for the DC on the DR site's Hyper-V box, and booted the domain controller.  Sat at the "please wait" forever, as if it's waiting for DNS.  Once we get into the box, we're unable to open AD users and computers.  Unable to do anything DC related.  We adjusted the DNS on the NIC to only point to itself, rebooted again, and same results.  All services are running.  Can get into the DNS console and all looks good.  

Opening AD users and computers gives us, "Naming information cannot be located because: The specified domain either does not exist or could not be contacted.  Contact your system administrator to verify that your domain is properly configured and is currently online."

Nothing in the event logs jumps out at us - plenty of errors because it's looking for the other domain controllers.  It does appear to be having an issue in that it can't contact DNS though, but not sure why as DNS is running and we see it fine.  DNS server is listening on all IP addresses.

Appears the netlogon and sysvol shares are also gone.

Does this have something to do with the ability for server 2012 to properly virtualize and rollback DCs, and it won't advertise itself as a DC until it successfully ________?

Suggestions?
LVL 9
diperspAsked:
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.

gheistCommented:
Easiest is to place DC or two in DR site and let their brothers in primary site die and DR site to take over the roles.
0
diperspAuthor Commented:
Yes, we already have that in place.  Looking for multiple recovery methods.
0
diperspAuthor Commented:
Good information for anyone else that runs into this.  We were finally able to get domain services back up after running an authoritative restore of NTFRS on the domain controller we were bringing up in our test environment.  

http://support2.microsoft.com/kb/290762
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
diperspAuthor Commented:
With the help of a Microsoft tech, suggestion was to do an authoritative restore which indeed worked.
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
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.