In previous years we would perform a DR test consisting of bringing up a handful of our Windows Server VMs (On VMWare) at our Disaster recovery location. The DR location has it's own SAN array that is replicated to regularly throughout the day. And when we do the test we connect the VMs to a standalone "sandbox" network that has no connectivity to the other 6 sites with domain controllers at each.
Previously we've had no problems spinning up the Windows 2008 DC (FSMO role holder) first, then exchange, then the file and sql servers. Earlier this year we installed a new 2012 DC as the FSMO role holder and demoted and removed the old 2008 DC (role
holder). So I go to do kick off the test, start up the new 2012 DC and find that AD is not functioning on it. DNS appears to be running and not giving any errors. Running a "netdom query fsmo" returns a "the specified domain
either does not exist or could not be contacted". I'm also getting eventID 2092 "This server is the owner of the following FSMO role but does not consider it valid...." Which appears to give a course of action in option 3.
3. In the rare event that all replication partners being down is an expected occurance,
perhaps because of maintenance or a disaster recovery, you can force the role to be validated.
This can be done by using NTDSUTIL.EXE to seize the role to the same server.
This may be done using the steps provided in KB articles 255504 and 324801
on http://support.microsoft.com.
However when I try to seize the roles, following that process with a reboot. I'm still in the same position I was in earlier. So I'm left to wonder what I should try next. The production version of this VM appears healthy and runs like a top. Any suggestions?