E
ewitz
Client with horrible backup management got hit with crypto, and I am in the midst of trying to get something back operational.
They have a single Server Standard 2012 R2 box (physical) which functions as domain controller. I was forced to restore from an old Windows Server Backup drive, which makes this restore-from-backup more than a year old.
I'm used to sometimes seeing the 0xc00002e2 blue screen when first booting a server from restore, but the normal steps I take to resolve have had no effect. Booted into Directory Services Restore Mode and cleared all log files from C:\Windows\NTDS, and that had no effect. Additionally ran esentutl /p "c:\windows\ntds\ntds.dit" and that, too, had no effect.
I am unsure where to proceed from here. There are no other machines I can grab AD settings from. I am wondering whether to attempt a restore from a different date on that restore drive...?
Continue reading...
They have a single Server Standard 2012 R2 box (physical) which functions as domain controller. I was forced to restore from an old Windows Server Backup drive, which makes this restore-from-backup more than a year old.
I'm used to sometimes seeing the 0xc00002e2 blue screen when first booting a server from restore, but the normal steps I take to resolve have had no effect. Booted into Directory Services Restore Mode and cleared all log files from C:\Windows\NTDS, and that had no effect. Additionally ran esentutl /p "c:\windows\ntds\ntds.dit" and that, too, had no effect.
I am unsure where to proceed from here. There are no other machines I can grab AD settings from. I am wondering whether to attempt a restore from a different date on that restore drive...?
Continue reading...