Group Policy Replication Failure
- Environment:
Server 2003 Forest Level
Server 2003 Domain Level
Single Domain/Forest
3 Server 2008 Domain controllers in Corporate HQ
5 Server 2003 Domain controllers in branch offices
Issue:
Months ago we began updating our HQ domain controllers from Server 2003 to Server 2008. All has gone well, except for we have recently discovered that Group Policy isn't being replicated out from the PDC (which is one of the Server 2008 Domain Controllers). When looking at GPMC, the AD version for a particular GPO is 165, whereas the SYSVOL version is 138. It does not seem that FRS is replicating the files correctly, as I can place a file in the SYSVOL directory and is does not get replicated.
I'm not sure why replication isn't working. DCDIAG looks clean for all the servers. The event logs have no errors stating that FRS cannot connect to the destination servers, so I know the problem lies within FRS itself.
Where do I go from here?
Trevor
Answers
- Sorry for the late reply. This issue manifested itself as a direct result of moving the SYSVOL and Active Directory database files on the NTFS partition on the server. Luckily, I had one working Domain Controller here at our home office so I was able to simply demote and re-promote the affected DCs, choose the correct NTFS location, and all is well!
Trevor- Marked As Answer byrovert506 Friday, November 06, 2009 4:58 PM
All Replies
- Hi Trevor,
To better understand the current problem, please help to collect the following information for research:
1. Could you create new GPO on all DCs? Please try on all DCs and let us know if there is the GPOs appear in the SYSVOL folder.
2. Please run the command below on every DC:
repadmin /showrepl >>c:\\repadmin.txt
repadmin /showrepl SERVERNAME >>c:\\repadmin.txt
Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give me the download address.
3. Run "dcdiag /v >>c:\dcdiag.txt" on every DC and upload the files.
4. There are some general guides to troubleshoot replication problems, please try to follow the guides:
Troubleshooting Active Directory Replication Problems
http://technet.microsoft.com/en-us/library/bb727057.aspx
Troubleshooting replication
http://technet.microsoft.com/en-us/library/cc755349(WS.10).aspx
Using Ultrasound for troubleshooting FRS
http://blogs.technet.com/instan/archive/2009/08/17/using-ultrasound-for-troubleshooting.aspx
Mervyn
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byMervyn ZhangMSFT, ModeratorFriday, October 30, 2009 11:13 AM
- Unmarked As Answer byrovert506 Friday, November 06, 2009 4:57 PM
- Hi,
Do you need any other assistance? If there is anything we can do for you, please let us know.
Thanks.
This posting is provided "AS IS" with no warranties, and confers no rights. - Sorry for the late reply. This issue manifested itself as a direct result of moving the SYSVOL and Active Directory database files on the NTFS partition on the server. Luckily, I had one working Domain Controller here at our home office so I was able to simply demote and re-promote the affected DCs, choose the correct NTFS location, and all is well!
Trevor- Marked As Answer byrovert506 Friday, November 06, 2009 4:58 PM
- Hi Trevor,
Glad to hear you have resolved the problem. If you have more questions in the future, you’re welcomed to this forum.
Thanks.
This posting is provided "AS IS" with no warranties, and confers no rights.
