Project Case Analysis IV: SYSVOL STOP replication after DC upgrade, log 13508

Recently, during the 240-site AD upgrade project, the contents of the Sysvol were not moved in half after the individual DC upgrade, and there was no movement for one weeks in a row, so I would like to share with you today how to deal with this problem.

1. Introduction to the Environment

650) this.width=650; "title=" 1.PNG "alt=" wkiom1uvfgmyr3vxaaepbspa2zu865.jpg "src=" http://s3.51cto.com/wyfs02/M01/ 6b/7c/wkiom1uvfgmyr3vxaaepbspa2zu865.jpg "/>

• Among them, DC01 and DC02 are the DC of China Headquarter, and the other more than 200 sites in China are replicated by KCC-generated links and DC01 or DC02;

• DC01 and DC02 are bridgehead servers;

2. Problem phenomena

2.1 View the policies content under SYSVOL, the last replication time is 20150215, has not moved for more than one weeks, and the number of GPOs is only 138 (the number of fully replicated GPOs is 428)

650) this.width=650; "title=" 2.png "alt=" wkiol1uvf7zxbnyhaarykqvfj4w630.jpg "src=" http://s3.51cto.com/wyfs02/M01/ 6b/78/wkiol1uvf7zxbnyhaarykqvfj4w630.jpg "/>

2.2 View FRS does not have any error only 13508 warning, the log shows a problem with FRS replication for this DC with DC03

650) this.width=650; "title=" 3.png "alt=" wkiol1uvf-2bzpf-aatg_fvhcpq785.jpg "src=" http://s3.51cto.com/wyfs02/M00/ 6b/78/wkiol1uvf-2bzpf-aatg_fvhcpq785.jpg "/>

2.3 The KCC link seen in Adsite is replicated with DC04

650) this.width=650; "title=" 4.png "alt=" wkiol1uvgajth0f7aajvtuwzek8900.jpg "src=" http://s3.51cto.com/wyfs02/M00/ 6b/78/wkiol1uvgajth0f7aajvtuwzek8900.jpg "/>

Preliminary judging from the above information is currently out of sync due to the previous replication with DC03, but after the KCC link changes, the FRS service still retains the replication with DC03, so it needs to be re-forced to replicate

3. Solution

3.1 Open adsite, remove KCC link established with DC04

650) this.width=650; "title=" 5.png "alt=" wkiol1uvggxtmgueaakaw0tctio116.jpg "src=" http://s3.51cto.com/wyfs02/M01/ 6b/78/wkiol1uvggxtmgueaakaw0tctio116.jpg "/>

3.2 Open the command-line administration tool and run the following command

Repadmin/replicate DC04 DC01 cn=configuration,dc=Contoso, dc=Corp / Force

3.3 Restart the FRS service and Netlogon, wait for the new KCC link to be generated and re-replicate (the above command and restart service actions need to be repeated several times)

650) this.width=650; "title=" 6.png "alt=" wkiom1uvf0sbvfwkaaft9rwiq8s445.jpg "src=" http://s3.51cto.com/wyfs02/M01/ 6b/7d/wkiom1uvf0sbvfwkaaft9rwiq8s445.jpg "/>

3.4 After a period of waiting, SYSVOL has been synchronized and automatically shared, such as:650) this.width=650; "title=" 7.png "alt=" wkiom1uvf5irvkukaashi1yx_ Mq676.jpg "src=" Http://s3.51cto.com/wyfs02/M01/6B/7D/wKiom1UvF5iRVkUkAAShI1Yx_MQ676.jpg "/>

The above is a solution to the ad synchronization problem, welcome to exchange more people.

This article from "Bright Future" blog, declined reprint!

Project Case Analysis IV: SYSVOL STOP replication after DC upgrade, log 13508