🟠 High   ⏱ 5–30 min  Last verified: 29 May 2026
Affected versions: Windows Server 2019

📖 ~1 min read

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution — Primary Fix
  7. Solution — Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

After promoting a server to a domain controller, SYSVOL and NETLOGON shares are absent. Group Policy processing fails and client logons become inconsistent.

Environment & Reproduction

Windows Server 2019 DC promotion in environments with delayed AD replication or DFSR startup issues.

Get-SmbShare | Where-Object Name -in 'SYSVOL','NETLOGON'
dcdiag /test:sysvolcheck /test:advertising

Root Cause Analysis

DFSR initial sync is incomplete or blocked by replication failures, service dependency issues, or stale SYSVOL metadata.

Quick Triage

Check DFSR service state, AD replication status, and SYSVOL subscription objects.

Get-Service DFSR,Netlogon,NTDS
repadmin /replsummary

Step-by-Step Diagnosis

Inspect DFS Replication logs and verify the Domain System Volume subscription for the promoted DC.

Get-WinEvent -LogName 'DFS Replication' -MaxEvents 100
wmic /namespace:\rootmicrosoftdfs path dfsrreplicatedfolderinfo get replicatedfoldername,state
Illustrative mockup for windows-server-2019 — terminal_or_powershell
DFSR and SYSVOL validation commands — Illustrative mockup — Progressive Robot

Solution — Primary Fix

Restart DFSR and Netlogon, sync AD partitions, and trigger DFSR AD poll.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Restart-Service DFSR -Force
repadmin /syncall /AdeP
dfsrdiag pollad
Restart-Service Netlogon
Illustrative mockup for windows-server-2019 — event_or_log_viewer
DFSR events related to SYSVOL initialization — Illustrative mockup — Progressive Robot

Solution — Alternative Approaches

If SYSVOL data is corrupted, perform authoritative or non-authoritative SYSVOL restore during maintenance.

dfsrdiag backlog /rgname:'Domain System Volume' /rfname:'SYSVOL Share' /sendingmember:DC1 /receivingmember:DC2

Verification & Acceptance Criteria

SYSVOL and NETLOGON shares exist and gpupdate succeeds from a member server.

Get-SmbShare | Where-Object Name -in 'SYSVOL','NETLOGON'
gpupdate /force

Rollback Plan

Restore system state if remediation worsens replication consistency.

wbadmin get versions
# Recover from last known good backup if required

Prevention & Hardening

Promote DCs during low-change windows and validate replication health before adding production workloads.

dcdiag /q
repadmin /replsummary

Related to DFSR Event IDs 2213/4614 and AD replication failures between sites.

Related tutorial: View the step-by-step tutorial for Windows Server 2019.

View all Windows Server 2019 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn: SYSVOL DFSR troubleshooting and AD DS promotion checks for Windows Server 2019.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.