Forum Discussion
Decommissioning Essentials 2012 server, replacing with 2022 - final steps before remove old AD role?
Ok.. DC is demoted.. saw a few errors in logs.. went and removed references to old DC in DNS (switching to new DC where only a single value, removing old DC where two options listing both).. re-ran DCDIAG..
It seems only remaining potential issues:
- DCOM errors in dcdiag output about trying to reach old DC (what would these be about?)
- Potential issues around DFSR on SYSVOL and NETLOGON (do I need to do anything there?)
To be clear, I demoted the DC through removing the role in the Server Manager (rather than forcing it as if it were no longer available).
- L_Youtell_974Apr 28, 2024Iron Contributor
hello ADFHogan, i saw your post and i think, i may be able to save your day. When you migrate your AD to a new version, sometime the migration doesn't work perfectly but you don't have any warning. Everything work except for the netlogon, sysvol, GPO ....
You have to finish everything by hand.
For the netlogon and sysvol follow the link below
https://thesysadminchannel.com/solved-sysvol-and-netlogon-shares-missing-2016-2019-domain-controller/
For DFSR you have to follow the link below
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-authoritative-recovery-sysvol
I hope the link help.- ADFHoganMay 13, 2024Copper ContributorThanks, L_Youtell_974..
I think I'm going to need to look at the DFSR stuff as it's popped up. Hopefully if I fix it before it tombstones,, I won't have problems with netlogon and sysvol again.- L_Youtell_974May 13, 2024Iron ContributorYou should be ok. As the old DC remain, everything should work fine. You just go through the guide and the new DC should be OK without any lost. The OLD DC should be online because it will retrieve the data from the old DC.