This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 94%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Oi turma, um belo dia, após queda de energia, uma vm não sobe, justamente nosso AD.
Before the vm would not boot because it lost the reference in hyperv, the .vhdx, and the snap...But I booted a new vm and attached the .vhdx but it boots in Directory Services Repair Mode
From the blue Stop Code screen: 0xc00002e2
[
I Tried to
Acessar o modo Directory Services Repair Mode
ntdsutil.exe
activate instance ntds
files
e esentutl /p "c:\windows\ntds\ntds.dit" | ntdsutil.exe activate instance ntds files recover
But blue screen
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 80%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
My answer will be in English because we are in anEnglish forum.
How many domain controller you have in same domain of failed AD?
If you have another DC , you can install new machine , perform metadacleanup to delete the failed DC and promote new on properly.
Please don't forget to mark helpful answer as accepted
Just checking if there is any update ?
Please don't forget to mark helpful answer as accepted
Hi, sorry to response late. I've tried all the steps mentioned. I decided to create a new virtual machine, unfortunately.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The simplest / safest solution is to seize roles to another healthy one
seize FSMO roles in Active Directory Domain Services
then perform cleanup to remove remnants of failed one from active directory
Clean up Active Directory Domain Controller server metadata
Step-By-Step: Manually Removing A Domain Controller Server
then stand up a new one for replacement, I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
--please don't forget to upvote and Accept as answer if the reply is helpful--
