asked on
SYSVOL Replication Fails
introducing a 2016 DC into an existing 2012 domain.
Single 2012 (not r2) server and DCDIAG ran clean before the new DC was added.
The domain function level was 2012, but I didn't realize the Forest function level was 2003.
(didn't seem to matter for the promotion, but I did upgrade it afterwards to 2012 hoping that would help my sysvol replication trouble)
The new 2016 DC added normally, and transferred the FSMO roles
(This may or may not matter, before the promotion the domain function level was 2012, but I didn't realize the Forest function level was 2003.
it didn't seem to matter for the promotion, however after the new DC was added, i did upgrade the Forest to 2012 as well)
Now DCDIAG has error: C:\Users\Admin>dcdiag -q
Warning: DsGetDcName returned information for \\Server2012.wert.local, when we were trying to reach Server2016.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... Srever2016 failed test Advertising
Unable to connect to the NETLOGON share! (\\Server2016\netlogon)
[Server2016] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
......................... Server2016 failed test NetLogons
The new server has a SYSVOL folder, and subfolders... but everything is empty. From all that I've read... I'm suppose to force the non-authoritative synchronization of SYSVOL.
However using the tool ADSIEDIT.MSC, and following the path to make the changes (CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettin
It does not have the CN=DFSR-LocalSettings on either server.
Cannot make the edits recommended.
Maybe the original 2012 server never had DFS installed? (doesn't seem to be installed now, but it's been running the domain fine for several years)
Single 2012 (not r2) server and DCDIAG ran clean before the new DC was added.
The domain function level was 2012, but I didn't realize the Forest function level was 2003.
(didn't seem to matter for the promotion, but I did upgrade it afterwards to 2012 hoping that would help my sysvol replication trouble)
The new 2016 DC added normally, and transferred the FSMO roles
(This may or may not matter, before the promotion the domain function level was 2012, but I didn't realize the Forest function level was 2003.
it didn't seem to matter for the promotion, however after the new DC was added, i did upgrade the Forest to 2012 as well)
Now DCDIAG has error: C:\Users\Admin>dcdiag -q
Warning: DsGetDcName returned information for \\Server2012.wert.local, when we were trying to reach Server2016.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... Srever2016 failed test Advertising
Unable to connect to the NETLOGON share! (\\Server2016\netlogon)
[Server2016] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
......................... Server2016 failed test NetLogons
The new server has a SYSVOL folder, and subfolders... but everything is empty. From all that I've read... I'm suppose to force the non-authoritative synchronization of SYSVOL.
However using the tool ADSIEDIT.MSC, and following the path to make the changes (CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettin
It does not have the CN=DFSR-LocalSettings on either server.
Cannot make the edits recommended.
Maybe the original 2012 server never had DFS installed? (doesn't seem to be installed now, but it's been running the domain fine for several years)
Active DirectoryWindows 10AzureWindows Server 2012Windows Server 2016
Last Comment
Mahesh