Completely agree. Delete the VM, clean up AD, and start over --brian
From: [email protected] [mailto:[email protected]] On Behalf Of Charles F Sullivan Sent: Friday, August 7, 2015 9:49 AM To: [email protected] Subject: RE: [NTSysADM] Windows 2008 R2 recovery Ooh, good that you mentioned this, because I missed something the first time…. Regardless of the hypervisor itself, I was thinking that support for this sort of thing started with 2008 R2 DCs, but it started with 2012 DCs. Because your DC is 2008 R2, you don’t want to do anything like restore from a snapshot or save the state. You had better go with Plan B that I had mentioned. Again, see what others on the list say, but I really would avoid restoring from the snapshot. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Aakash Shah Sent: Friday, August 7, 2015 12:36 PM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Windows 2008 R2 recovery I believe that this only applies to 2012+? If so, since this server is 2008r2, unless the hypervisor is 2012+, it appears this will not work: https://msdn.microsoft.com/en-us/library/JJ643357(v=VS.85).aspx -Aakash Shah From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Charles F Sullivan Sent: Friday, August 7, 2015 8:02 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Windows 2008 R2 recovery 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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of CSSU NetAdmin Sent: Friday, August 7, 2015 9:52 AM To: [email protected]<mailto:[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?
