Metadata Cleanup Using NTDSUTIL in Windows Server 2019

[@ovidiojoseperez4207]

You are my Angel just save my 😊 with this video

[@howardberesford4025]

Great work, thank you for your help here very valuable information helping out big organizations.

[@PKArfeen]

YOU are expert man

[@jasoncummings7052]

Thanks for the presentation.

[@vishalnavgire7614]

Thanks for this Video on How to perform Metadata cleanup for a Fault DC. Won't NS record be removed by the Metadata cleanup [NtdsUtil] ? I saw you doing it manually for each Zone.

[@elangoramalingam667]

Please help, can not add adc and asking raised forast and domain level raised 2008, my current functional level is 2003, And my old adc pc HD not working, then I try to add another pc to adc error message

[@h.bragad.oliveira1441]

Thanks

[@rogerbennett9598]

You sir are awesome 👏

[@deepanns8460]

Really helpful thank you souch

[@MSFTWebCast]

Glad it was helpful!

[@mtayyabasghar1448]

Good Effort

[@pg4694]

have you performed this on the new fsmo owner

[@sarefeen]

LOVELY MATE PRECISE ..TAHNKS KEEP DOING MORE

[@pg4694]

and second thing when you are select server sites and domain why have u not followed the hirerarchy

[@muhamedbasic8458]

Thanks a lot mate!

[@MSFTWebCast]

You're welcome!

[@mahmoudsami7965]

Good work mate, very clear steps really helpful. I have got a question though, after performing this cleanup can I promote server later on to be a domain controller once more.

[@MSFTWebCast]

Yes.

[@faresist6510]

I have one note, when i do gpupdate / force it show error: the processing of group policy failed.... long message, what I can do with this ?

[@MSFTWebCast]

The issue is with SYSVOL group policy path. Try to access the sysvol folder using the UNC path and check whether you can access the domain policy folder or not? 1) Run the command to find more information dcdiag /e /c /v >c:\filename.log I am not 100% sure but I remember once I solved this kind of issue by editing ADSI to point correct path of the SYSVOL.

[@khackney86]

Great video

[@Ms.Robot.]

That was nice ❤️💋

[@nicholasspanos1804]

Can this be done in the GUI

[@MSFTWebCast]

Yes, you can use Active Directory users and computers snap-in to do so. Right click no computer account of domain controller, select delete. You will see one dialog box. Select This Domain Controller is permanently offline and can no longer be demoted using the Active Directory Domain Services Installation Wizard (DCPROMO), and then click Delete. Note: I still recommend you to use NTDSUTIL for metadata cleanup.

[@elangoramalingam667]

the functional level could not be raised, the error is. the fsmo role ownership could not be verified because its directory partition has not replicated successfully with last one replication partner

[@MSFTWebCast]

Verify the which DC currently holds the all FSMO roles. DC with all FSMO roles must be online otherwise you are not able to raise the functional level. In case if your DC with FSMO role is down then you need to seize FSMO roles and assign to DC which is currently up and running. If you even have little confusion do not proceed. Again ask for help.

[@elangoramalingam667]

@@MSFTWebCast Window 2008R2 is my current DC

[@elangoramalingam667]

All FSMO Rules is held window 2008R2

[@MSFTWebCast]

Run netdom query fsmo command for confirmation. Make sure all DC's are able to replicate with each other. Once DC's are replicating successfully. First raise the domain functional level and then raise forest functional level.

[@elangoramalingam667]

@@MSFTWebCast Do u have whatsup No

[@ThatoneSwifty13]

Followed these steps and I have one DC. I do see issues with meta data randomly popping up to old DC's. I want to clean those up - how? For example in forward and reverse lookups I still see the old DC. Can I just delete those and should solve the issue?

[@MSFTWebCast]

First check the SOA and NS entries in DNS zone properties. If old servers name is there just remove it.

[@faresist6510]

very nice, can I contact you by email, please? I have some questions you may help me with.