TroubleShooting Domain Controller Issues
Articles on: Virtual Machine
Understood the issue and found that SYSVOL and NETLOGON Folders weren't shared on both DC's
Both DC's were hosted on Azure VM.
There was a Failover after which the SYSVOL Replication stopped.
SYSVOL was replicating on FRS.
AD replication was stopped and both DC's weren't advertising as well.
None of the Snap-IN's were opening and were giving error like, ADSIEDIT and DSA.msc
Found that SYSVOL Folder was missing from "C:\Windows\" location
Created the Folders under the above-mentioned Path.
Ran MKLink Command to create Junction points.
Did AUTH and Non-Auth Restore for FRS on DC02 and DC01 and respectively.
Sysvol Issue was fixed.
Deleted Meta Data of old Stale DC's from AD and fixed AD replication as well.
Later copied all the policy GUID's under the Policies Folder and initiate AD replication.
Updated on: 31/01/2023
Understood the issue and found that SYSVOL and NETLOGON Folders weren't shared on both DC's
Both DC's were hosted on Azure VM.
There was a Failover after which the SYSVOL Replication stopped.
SYSVOL was replicating on FRS.
AD replication was stopped and both DC's weren't advertising as well.
None of the Snap-IN's were opening and were giving error like, ADSIEDIT and DSA.msc
Found that SYSVOL Folder was missing from "C:\Windows\" location
Created the Folders under the above-mentioned Path.
Ran MKLink Command to create Junction points.
Did AUTH and Non-Auth Restore for FRS on DC02 and DC01 and respectively.
Sysvol Issue was fixed.
Deleted Meta Data of old Stale DC's from AD and fixed AD replication as well.
Later copied all the policy GUID's under the Policies Folder and initiate AD replication.
Updated on: 31/01/2023
Updated on: 01/07/2024
Thank you!