asked on

SYSVOL replication issue

I have four DCs. One is running 2008 and is the primary. The other three are running 2003.

When I create a GPO on any one of the DCs, the policy listing in active directory replicates to each server, but the corresponding SYSVOL listing is only created on the 2008 server, and it does not replicate to the 2003 servers. It does not even create on the 2003 server if I create the policy on said server.

However, if I copy the corresponding SYSVOL GPO folder from the 2008 server and paste it in the SYSVOL directory of any one of the 2003 servers, replication instantly occurs across the other two 2003 servers.

Any ideas why?

Bassam Almasri

What is the result of command {repadmin \\<dc2008name> /options } ?

Sushil Sonawane

Run the command dcdiag /q, repadmin, gpotool check the working fine with any error.

Checked the file replication service error or warning event in event viewer -- file replication service.

Make sure your file replication service started state.

Your server NIC Card dns server setting IP Address point your dns server.

If you find the error event in file replication service then reinitialize File Replication Service replica sets Using the BurFlags registry key.

For more details refer below KB article:

http://support.microsoft.com/kb/315457
http://support.microsoft.com/kb/2218556
http://support.microsoft.com/default.aspx?scid=kb;en-us;290762&sd=tech

How sysvol FRS Works refer below link :

http://technet.microsoft.com/en-us/library/cc758169(v=ws.10).aspx

Satish Auti

Resolution
========
1. Examine the 13508 event in the File Replication
Service event log to determine which computer that FRS
has been unable to communicate with.
2. Determine whether the remote computer is working
properly, and verify that FRS service is running on it. A good
method to do this to execute the following command:
NTFRSUTL VERSION <FQDN_of_remote_DC_name> from the
computer logging the 13508 event.
3. If this fails, check network connectivity by pinging
the <FQDN_of_remote_DC_name> from the computer logging
the 13508 event. If this fails, then troubleshoot the
problem as a DNS or TCP/IP issue. If it succeeds, confirm
the FRS service is started on the remote domain
controller.
4. Determine whether FRS has ever been able to
communicate with the remote computer by looking for 13509
in the event log and reviewing recent change management
to networking, firewalls, DNS configuration, and Active
Directory infrastructure to see if there is a
correlation.
5. Determine whether there is anything between the two
computers that is capable of blocking RPC traffic, such
as a firewall or router.
6. Confirm that Active Directory replication is working.

Also make sure that you running all 2003 servers with latest service packs.

ASKER CERTIFIED SOLUTION

frapanthers

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Seth Simmons

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.