Environment: Three domain controllers, ad1/ad2 (win2008), AD4 (win2012), functional level win2008
Problem: Client gpupate behaves as follows:
650) this.width=650; "height=" 301 "title=" clip_image002 "style=" border:0px; "alt=" clip_image002 "src=" http:/ S3.51cto.com/wyfs02/m02/54/33/wkiol1r8avxqij1qaaih5l6jcf4185.jpg "border=" 0 "/>
The underlying scenario is that the Group Policy object on AD4 is not synchronized with ad1/ad2. When the client accesses the AD4 policy, an error is taken.
Workaround: First look at the replication related DFSR logs, such as the following, reported a single 4004 error, and did not report other errors, there is a "system cannot find the specified file" bug.
650) this.width=650; "height=" 345 "title=" clip_image003 "style=" border:0px; "alt=" clip_image003 "src=" http:/ S3.51cto.com/wyfs02/m00/54/33/wkiol1r8avjwcrjnaagnn6salvs228.jpg "border=" 0 "/>
See AD4 really did not C:\windows\sysvol_dfsr\ this directory, and looked at the other two, there is this directory, so from AD1 copied this directory to AD4 the same location, restart the DFSR service, found that the replication succeeded, but the content is not synchronized, so check the share, Discover \\AD4 below There is no Netlogon share, while the SYSVOL share exists, but the point is C:\Windows\Sysvol\Domain, not the latest C:\windows\sysvol_dfsr\domain, So the first thing to do is to change the direction of the SYSVOL to a new location: edit:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
In the Edit menu, click Add, and then add the following key values:
Value Name:sysvolready
Data Type:reg_dword
value:0
The original SYSVOL share disappears.
Change the value above to 1, and the new SYSVOL share will appear.
But then you don't see the Netlogon share,
You need to create a link manually.
mklink/j c:windows\sysvol\sysvol\cqwater.gov.cn C:\Windows\Sysvol\Domain
When the DFSR and Netlogon services are restarted after completion, the Netlogon appears and the DFSR replication is fully functional.
This article is from "Lao Zhu's IT Infrastructure blog" blog, please be sure to keep this source http://12937895.blog.51cto.com/9437529/1584998
DFSR replication is not synchronized with rebuilding Sysvol and Netlogon shares