As suggested, I built a new server, promoted it to DC and then cleaned up the metadata. Fortunately, another DC had the roles so I didn't have to worry about that. It all went well- no problems. Thanks for the help!
On Fri, Aug 7, 2015 at 11:01 AM, Charles F Sullivan < [email protected]> wrote: > Here are the VMware versions that support Generation ID, which you will > need in order to restore from a snapshot, in order to avoid USN rollback: > http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2041872 > > > > I think a lot of people would suggest building a new box, promoting it, > seizing any roles that were on the failed DC, then cleaning up the metadata > (which now only involves using AD Sites and Services snapin). I would tend > to agree, but see what others say. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *CSSU NetAdmin > *Sent:* Friday, August 7, 2015 9:52 AM > *To:* [email protected] > *Subject:* [NTSysADM] Windows 2008 R2 recovery > > > > A Windows 2008 R2 server boots to the recovery screen. It is a VM on > Hyper-V and is a domain controller. The last image of it was taken last > night at about 5:00 pm- close to 17 hours ago. Is there a risk with > restoring the image? There is a second DC in the domain- a physical > machine. We tried running sfc but get a message about a repair pending. > We ran dism to clean up the repair and revert back but it didn't work. If > we can restore the image, what options do we have? >
