Active Directory SYSVOL recovery

Missing SYSVOL and NETLOGON shares require a known-good directory and DFSR source before authoritative recovery.

Modern Active Directory domains replicate SYSVOL with DFS Replication. After a dirty shutdown, storage failure or database recovery, DFSR can pause replication or leave SYSVOL unshared even while the domain controller still answers directory requests.

Understand the symptom

SYSVOL recovery must align directory objects, DFSR membership and the file tree used for Group Policy and logon scripts.

WHY

What is happening

Recovery determines whether the issue is DFSR event 2213-style suspension, initial sync, database damage, USN or invocation history, or missing file content. An authoritative or non-authoritative sync changes which copy becomes the source for others, so source selection must precede configuration changes.

What you may see

Symptoms that change the recovery path.

01

SYSVOL and NETLOGON are not shared

The domain controller has not completed a valid SYSVOL initialization.

02

DFSR paused after unexpected shutdown

Replication awaits recovery or the database cannot resume cleanly.

03

Group Policy is inconsistent

Controllers hold different GPT files or cannot replicate updates.

04

Only one domain controller remains

There may be no second verified source for directory or SYSVOL state.

Protect the source

Actions that can make the situation worse.

01

Wrong authoritative source propagates stale policy

Older scripts and GPO files can replace newer valid content across the domain.

02

Deleting the DFSR database removes history

A rebuild can obscure the exact divergence and pending changes.

03

Restoring only SYSVOL creates mismatch

AD GPC objects and SYSVOL GPT content must correspond.

Do this now

Safe steps before evaluation.

01

Stop broad replication changes

Pause demotion, metadata cleanup, DFSR database deletion and authoritative flags.

02

Inventory every controller

Record shares, DFSR events, AD replication, GPO versions, roles, backups and last known good times.

03

Preserve system state

Protect NTDS, registry, SYSVOL, DFSR data, logs and backups for each controller.

04

Identify a trusted source

Compare directory and SYSVOL content before selecting any authoritative copy.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Domain-state comparison

NEPFOSYS maps controller histories, AD replication and SYSVOL file versions.

02

Protected source validation

Candidate system-state backups and controller copies are evaluated away from production.

03

Controlled recovery planning

Authoritative or non-authoritative steps are based on the verified source and then validated for shares and policy consistency.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can I just resume DFSR after a dirty shutdown?

Only after confirming storage health and that the local database and SYSVOL are the copy you want to retain.

Which domain controller should be authoritative?

The one with the most complete, verified and appropriate AD and SYSVOL state—not automatically the FSMO-role holder or newest server.

Does a system-state backup include SYSVOL?

For a domain controller it is designed to capture directory and system components, but the backup must be validated and matched to the recovery objective.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case