Server 2012 SYSVOL Non-Authoritative restore on an RODC


hi,

so have 4 normal dc's, 2 in each datacenter. 1 dc in each datacenter pushes out rodc 

writeable:

dc01

dc02 --> rodc dc05

dc03 --> rodc dc06

dc04

the dfsr database stopped working on rodc dc05 resolved, database had been offline on 60 days means replication no longer working on rodc:

log name:      dfs replication
source:        dfsr
date:          30/01/2017 11:40:24
event id:      4012
task category: none
level:         error
keywords:      classic
user:          n/a
computer:      dc05
description:
dfs replication service stopped replication on folder following local path: g:\windows\sysvol\domain. server has been disconnected other partners 61 days, longer time allowed maxofflinetimeindays parameter (60). dfs replication considers data in folder stale, , server not replicate folder until error corrected. 
 
resume replication of folder, use dfs management snap-in remove server replication group, , add group. causes server perform initial synchronization task, replaces stale data fresh data other members of replication group. 
 
additional information: 
error: 9061 (the replicated folder has been offline long.) 
replicated folder name: sysvol share 
replicated folder id: 2ded4fc4-48b3-4da4-b2ce-96d2db6a3e6b 
replication group name: domain system volume 
replication group id: f6325288-9b34-4d3e-ac54-8c0d44a69f44 
member id: acb17d86-9727-4d95-959a-9b120b6c9f4d

i know non-authoritative restore process, doesn't seem work correctly in terms of fixing rodc.

https://www.experts-exchange.com/articles/17360/active-directory-dfsr-sysvol-authoritative-and-non-authoritative-restore-sequence.html 

the adsiedit part connect default naming context connects me writeable dc - dc02, not dc05.

does have correct process fix dfsr replication on rodc??


mcsa server 2012/2008 mcitp exchange 2010

fixed.

as content 1 day on 60 day limit changed maxofflinetimeindays=62 on broken rodc:

wmic.exe /namespace:\\root\microsoftdfs path dfsrmachineconfig set maxofflinetimeindays=62

restarted dfsr service , writable domain controller pushed out updates.

i ran status check button in gpmc , confirmed dc's upto date , in sync.

tomorrow, revert 60 days maxofflinetimeindays once know had 24 hours update. 

i still know if theres official documented process rodc's regards broken dfsr sysvol, or whether can modify maxofflinetimeindays value , read-only copy, writabledc update rodc correctly?


mcsa server 2012/2008 mcitp exchange 2010




Windows Server  >  Directory Services



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client