TwistedHelixis Posted January 2, 2025 Posted January 2, 2025 Hi, This is something I only do every 4 or 5 years. Current DC = Server 2019 Just installed a new 2022 server. Installed updates joined it to domain installed Active Directory Domain Services role Promote the new server to a domain controller In my really old notes, my next step is to check C:\Windows\SYSVOL\Domain C:\Windows\SYSVOL\sysvol\Domain.lan All those folders are shown on my new 2022 DC, but both the Domain & Domain.lan folders are empty. Is this still the correct location to look for these folders / files? Should I wait a bit to see if the files appear inside these folder? BTW on the new 2022 DC server, if I open Group Policy Management, all the group policies are displayed. I suppose I can just demote the new DC and try again
Olliedawg Posted January 2, 2025 Posted January 2, 2025 How long have you waited? Worth running repadmin commands to check replication status if you haven't already, any errors etc.. 1
TwistedHelixis Posted January 2, 2025 Author Posted January 2, 2025 How long have you waited? About 30 minutes Worth running repadmin commands Do I run these on the old or new DC?
Olliedawg Posted January 2, 2025 Posted January 2, 2025 How long have you waited? About 30 minutes Worth running repadmin commands Do I run these on the old or new DC? Hmm ok Run "repadmin /showrepl" & "repadmin /replsummary" on the new DC to see last connection attempt to the other DC's Can also try "repadmin /syncall" to force a sync, and then check the local sysvol folder 1
Roberto Posted January 2, 2025 Posted January 2, 2025 Does Windows Server 2022 only support DFS-R by any chance and your old DCs haven't been migrated yet? 1
TwistedHelixis Posted January 2, 2025 Author Posted January 2, 2025 Does Windows Server 2022 only support DFS-R by any chance and your old DCs haven't been migrated yet? I thought server 2019 only supported DFS-R, so didn't check. Ill check that now. Run "repadmin /showrepl" & "repadmin /replsummary" on the new DC to see last connection attempt to the other DC'sCan also try "repadmin /syncall" to force a sync, and then check the local sysvol folder Just logging in now to test
TwistedHelixis Posted January 2, 2025 Author Posted January 2, 2025 repadmin /showrepl Everything successful repadmin /replsummary lists both the new and old DC 0 fails repadmin /syncall Completed with no errors
TwistedHelixis Posted January 2, 2025 Author Posted January 2, 2025 BTW both servers are using the newer DFS-R
TwistedHelixis Posted January 2, 2025 Author Posted January 2, 2025 Just to update - I have demoted the new DC and will start over.
Olliedawg Posted January 3, 2025 Posted January 3, 2025 Sounds like a good method, fingers crossed. We created new DC's in summer of 2023 & went from Server 2012 R2 > Server 2022. For me, Those local folders on the C:\ drive of the DC contain the same as \\domain.local\sysvol. I can't recall doing anything out of the ordinary when creating the new DC's. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now