F
forgiven
Hyper-V VM of Server 2016. This server boots to a BSoD and stop error 0x00002e2. A quick search shows running ntdsutil and so i did and on the subsequent reboot, now the server just boots in a loop, no BSoD. I tried last known good config = same boot loop. I disabled auto reboot on failure = same boot loop. Chkdsk reports no errors found and sfc /scannow reports windows resource protection could not perform the operation. Anyone have any ideas on how i can get this DC back up and running (no known good backup). The Server 2012 R2 secondary DC is up and running
So i rebooted into DS repair mode and the interesting thing now is, the server name is now win-ah5xxxx instead of the 'real' name of the server! I made sure i am actually on the correct server which i am. I logged with local admin and it appears all the directory services are there so i went into the c:\windows\ntds directory and another interesting thing: the log files i had renamed just earlier were no longer there!? Ntds.dit WAS there so i reran the ntdsutil commands to compact the DB and moved that file into the C:\windows\ntds folder renaming the existing ntds.dit file. Reboot the server and still the same boot loop
Continue reading...
So i rebooted into DS repair mode and the interesting thing now is, the server name is now win-ah5xxxx instead of the 'real' name of the server! I made sure i am actually on the correct server which i am. I logged with local admin and it appears all the directory services are there so i went into the c:\windows\ntds directory and another interesting thing: the log files i had renamed just earlier were no longer there!? Ntds.dit WAS there so i reran the ntdsutil commands to compact the DB and moved that file into the C:\windows\ntds folder renaming the existing ntds.dit file. Reboot the server and still the same boot loop
Continue reading...