You are on page 1of 6

Sysvol replication: C:\>dcdiag Domain Controller Diagnosis Performing initial setup: Done gathering initial info.

Doing initial required tests Testing server: Default-First-Site-Name\DOMAIN CONTROLLER Starting test: Connectivity ......................... DOMAIN CONTROLLER passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\DOMAIN CONTROLLER Starting test: Replications ......................... DOMAIN CONTROLLER passed test Replications Starting test: NCSecDesc ......................... DOMAIN CONTROLLER passed test NCSecDesc Starting test: NetLogons ......................... DOMAIN CONTROLLER passed test NetLogons Starting test: Advertising ......................... DOMAIN CONTROLLER passed test Advertising Starting test: KnowsOfRoleHolders ......................... KnowsOfRoleHolders Starting test: RidManager ......................... DOMAIN CONTROLLER passed test RidManager Starting test: MachineAccount ......................... DOMAIN CONTROLLER passed test MachineAccount Starting test: Services DOMAIN CONTROLLER passed test

......................... DOMAIN CONTROLLER passed test Services Starting test: ObjectsReplicated ......................... ObjectsReplicated Starting test: frssysvol ......................... DOMAIN CONTROLLER passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Group Policy problems. ......................... DOMAIN CONTROLLER failed test frsevent Starting test: kccevent ......................... DOMAIN CONTROLLER passed test kccevent Starting test: systemlog An Error Event occured. EventID: 0x00000457 15:44:48 Failing SYSVOL replication problems may cause DOMAIN CONTROLLER passed test

Time Generated: 08/17/2012

(Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 15:44:50

Time Generated: 08/17/2012

(Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 15:44:51

Time Generated: 08/17/2012

(Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 15:44:52

Time Generated: 08/17/2012

(Event String could not be retrieved) An Error Event occured. EventID: 0x00000457

Time Generated: 08/17/2012

15:44:52

(Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 15:44:52

Time Generated: 08/17/2012

(Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 15:44:53

Time Generated: 08/17/2012

(Event String could not be retrieved) ......................... DOMAIN CONTROLLER failed test systemlog Starting test: VerifyReferences ......................... VerifyReferences DOMAIN CONTROLLER passed test

Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : nic Starting test: CrossRefValidation ......................... nic passed test CrossRefValidation Starting test: CheckSDRefDom ......................... nic passed test CheckSDRefDom Running enterprise tests on : nic.local Starting test: Intersite ......................... nic.local passed test Intersite Starting test: FsmoCheck ......................... nic.local passed test FsmoCheck

The failed tests above are due to past errors being in the event log from before the sysvol fix. If youre having sysvol replication errors, youll see the replication tests failing, along with systemlog and frsevent failures. To fix this, the intact sysvol folder needs to be forced to replicate across the domain. The process is as follows: Stop the FRS service on all domain controllers. Locate the Burflags entry under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Resto re\Process at Startup

And change the DWORD value to D4 on the source domain controller (this is to flag an authoritative restore, and D2 on the child domain controllers (non-authoritative). Before doing this, take a backup of the sysvol folder, but make sure you store it on the same partition, otherwise permissions may change, and this would impact group policy if you had to restore it. Then restart the FRS service on all domain controllers (the D4 one first) and wait for replication to occur. This can take up to a few hours, depending on the infrastructure, number of domain controllers, and size of the sysvol folder.

Afterwards, running
Net share

At a command prompt will also show you the shared folders on the domain controller so once this replication is complete, you should see the sysvol and netlogon shares present. Then you can also run DCDIAG tests on each domain controller to confirm. each domain controller in the domain, follow these steps: 1. Click Start, click Run, type cmd, and then click OK. 2. Type net start ntfrs to start the File Replication service. 3. Type ntfrsutl ds |findstr /i "root stage", and then press ENTER. The NTFRSUTIL command returns the current root directory for the SYSVOL replica set that is referred to as the replica set root and the staging folder. For example, this command returns: Root: C:\WINNT\SYSVOL\domain Stage: C:\WINNT\SYSVOL\staging\domain 4. Type Linkd %systemroot%\SYSVOL\SYSVOL\ DNS Domain name, and then press ENTER. The LINKD command returns the following: Source DNS Domain Name is linked to %systemroot%\SYSVOL\domain 5. Type linkd "%systemroot%\SYSVOL\staging areas\DNS Domain Name", and then press ENTER. This command returns the following: Source DNS Domain Name is linked to %systemroot%\SYSVOL\Staging\domain How do I force the Sysvol replication in an active directory Your can restart the FRS service to force the FRS replication To restart the FRS service, launch services.msc from the Run option on the Start Menu And restart the FRS service and you will get the Event ID 13516 on FRS event log this will ensure the FRS status is fine Forcing Sysvol replication through NTFRSUTL If you want to force sysvol replication between two domain controllers in an active directory then use the below procedure NTFRSUTL FORCEREPL Command-Line Option to Force Replication You can use the new ntfrsutl forcerepl command to enforce replication regardless of the predefined replication schedule. This is only implemented for the domain controller Sysvol replica set. ntfrsutl forcerepl [Computer] /r [SetName] /p [DnsName] This command forces FRS to start a replication cycle. You must specify the Computer, SetName and DnsName. Note In this command, the following placeholders are used:

[Computer] = Connect with the NtFrs service on this machine. [SetName] = The name of the replica set. [DnsName] = The DNS name of the inbound partner to force replication from. I have a GPO replication problem, I believe that the SYSVOL is corrupt. Why I think it is corrupt: GPO's wern't replicating, gpotool or userenv (can't remember which) told me when a local machine tried to connect to Hermes or Apollo DC the desktop machine was looking at sysvol/mydomain but looking at sysvol I noticed that it should of been looking at sysvol/sysvol/mydomain So I made the stupid mistake of copying the mydomain folder back one level, when that didn't work I deleted it, but it also deleted the original !!! Can I repair the sysvol? so I ran: dcdiag /a /q it reported the following error Testing server: Default-First-Site-Name\HERMES Starting test: frssysvol Error: No record of File Replication System, SYSVOL started. The Active Directory may be prevented from starting. There are errors after the SYSVOL has been shared. The SYSVOL can prevent the AD from starting. ......................... HERMES passed test frssysvol Then I tried the following: 1. ran ipconfig /registerdns 2. restarted the File Replication service on both machines 3. re-set the trust for deligation on both machines 4. Changed the Operations master to DC named Apollo Then when I ran dcdiag /a /q again it reported the following errors Testing server: Default-First-Site-Name\HERMES Starting test: frssysvol Error: No record of File Replication System, SYSVOL started. The Active Directory may be prevented from starting. ......................... HERMES passed test frssysvol Testing server: Default-First-Site-Name\APOLLO Starting test: frssysvol There are errors after the SYSVOL has been shared. The SYSVOL can prevent the AD from starting. ......................... APOLLO passed test frssysvol

You might also like