SYSVOL at branch site not same as HQ site

Our AD comprises of 2 Sites and 3DCS (All Windows Server 2008 R2, forest and domain functional levels also 2008 R2)

Our Head Office has 2 DCs and our branch office (4k miles away) has 1 DC.

The branch office DC has a SYSVOL folder that is different to the Head office SYSVOL folder.

I have attached DCDIAG output, be grateful for any help/advice on resolving this issue.
Who is Participating?
antoniokingConnect With a Mentor Author Commented:
Yes, I demoted and re-promoted the DC and everything is replicating fine now.
Is your Group policies working fine on both sites ?
Check below few command and update us the output.

¿      Repadmin /showrepl & Repadmin /Syncall DCName

¿      Dcdiag /s:Serverdc01 /test:replications

¿      Dcdiag /s:Serverdc01 /test:netlogons

So if u have not ran below command pls get it and update us the output.

C:\>Dcdiag /s:DCName --> Enter
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

antoniokingAuthor Commented:
Repadmin /showrepl displayed errors (see attached)
Repadmin /Syncall HQDC01 terminated with no errors.

Dcdiag /s:HQDC01 /test:replications passed all tests without any failures
Dcdiag /s:HQDC01 /test:netlogons passed all tests without any failures

I have also attached results from DCdiag /s:BRANCHDC

Thanks for your help!
Will SzymkowskiSenior Solution ArchitectCommented:
Take a look at the below link which illustrates common replication issues and ways to resolve them. Make sure that the DC in the remote site has the proper time.

Troubleshooting Steps for AD Replication

If you cannot get Sysvol to replicate properly, you may need to demote that DC in the branch office and promote it again and allow replication to happen.

Have u checked your Group Policy, is it working fine ?

gpupdate /force --> Enter

Also check your DNS Server settings IP address and all IP on Dcs as well

Also ensure the following on DC:
1. Each DC / DNS server points to its private IP address as primary DNS server and other remote/local DNS servers as secondary in TCP/IP properties.
2. Each DC has just one IP address and single network adapter is enabled.
3. Contact your ISP and get valid DNS IPs from them and add it in to the forwarders, Do not set public DNS server in TCP/IP setting of DC.
4. Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.
5.Also, disable local windows firewall service, by default it is enabled in vista/windows 2008 and above
You may go through below microsoft article as well to resolve ur mentioned related errors.
Is your issue resolved ?
antoniokingAuthor Commented:
Thanks for your help, sorry I didn't go through the MS article. I needed a quick resolution.
Appreciate it doesn't help me or anyone else find the root cause but demoting and re-promoting certainly fixed the problem.!
antoniokingAuthor Commented:
Demoting/Promoting resolved the issue
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.