Hello,
I was also gone through the same kind of issue couple of weeks back:
I had single forest, single domain & 3 domain controllers all were running Windows Server 2K8R2.
DC Names: DC1 (Primary), DC2, DC3
As part of OS up-gradation to windows server 2k12R2 - have demoted DC2 , installed windows server 2k12R2 & re-promoted it as DC with same name; however after promotion of DC2, I have found that
SYSVOL & NETLOGON was not shared on my DC2 & in event viewer i was getting event 13565 i.e. "File Replication Service is initializing the system volume with data from another domain controller. ..."
If you are also facing the same issue then you must check below things.
I highly recommend you to test this solution first in test
environment.
1) Check if FRS Subscription objects are present - if objects are not present - you can manually create those object - refer this link https://support.microsoft.com/en-in/help/312862/recovering-missing-frs-objects-and-frs-attributes-in-active-directory
2) restart NTFRS & NETLOGON Service on Problem DC & see if it resolves the issue.
3) Try D2 D4 FRS Restore :https://support.microsoft.com/en-in/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi
4)
If all above steps does not help then you need to check if Replica Set & Cumulative replica set registry keys present on each domain controller, In my case registry entries was not present on newly promoted DC2.
Note: Each domain controller have only one replica set & cumulative replica set value on registry
- the value of Object GUID of DC & value present in registry on the same DC should match.
Before making any registry changes stop
NTFRS & Netlogon on all domain controllers | you can use cmd :
net stop ntfrs && net stop netlogon
Before moving forward, Take registry
backup of all domain controllers.
To create registry keys, we required object GUID of domain controller which can be found in ADSI edit:
Go to Adsiedit > connect to Default Naming context > CN=System>CN=File Replication Service> CN=Domain System volume (SYSVOL Share)
Here you will see nTFRS objects for all domain controllers , Right click on domain controller object on which you are having SYSVOL replication issue > go to properties > here you will find
ObjectGuid > copy the GUID Value.
Now go to Regedit Navigate
to : HKEY_LOCAL_MACHINE\SYSTEM\Currentcontrolset\Services\NtFRS\Paramaters> Cumulative replica sets > right click & select new key > paste GUID (Value copied from ADSI edit)
Create below registry entries in Cumulative replica sets\****GUID****
|
Name
|
Type
|
Data
|
|
BurFlag
|
REG_DWORD
|
0 (Hexadecimal)
|
|
Number of Partners
|
REG_DWORD
|
For this value refer
the value present on healthy DC
|
Now go to Regedit Navigate
to : HKEY_LOCAL_MACHINE\SYSTEM\Currentcontrolset\Services\NtFRS\Paramaters> replica sets > right click & select new key > paste GUID (Value copied from ADSI edit)
Create below registry entries replica sets\****GUID****
|
Name
|
Type
|
Data
|
|
Replica Set Name
|
REG_SZ
|
Domain System Volume (SYSVOL SHARE)
|
|
Replica Set Root
|
REG_SZ
|
Path of SYSVOL folder (ex: C:\windows\sysvol\domain)
|
|
Replica Set Stage
|
REG_SZ
|
Path of SYSVOL staging folder (ex: C:\windows\sysvol\domain\staging)
|
|
Replica Set Tombstoned
|
REG_DWORD
|
0 (hexadecimal)
|
|
Replica Set Type
|
REG_SZ
|
Domain
|
Follow the same step on all DCs & ensure on all domain controllers the GUID value on & value in registry matches.
5) Transfer FSMO Roles to Healthy Domain controller.
6) Take SYSVOL & NETLOGON folder Backup.
7) Login to PDC where SYSVOL & NETLOGON folders are up to date.
8) Start Regedit > Navigate to :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
Change BurFlags Registry value to D4
You can refer to understand D2 & D4 Restore
https://support.microsoft.com/en-in/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi
9) No login to Problem DC (where SYSVOL & NETLOGON not working )
10) Start Regedit > Navigate to :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
Change BurFlags Registry value to D2
11) Run below commands on all DCs:
Ipconfig /flushdns
Ipconfig /registerdns
12) Start NTFRS & NETLOGON service on all domain controllers - first start on PDC (where BurFlags value set to D4)
net stop ntfrs
&& net stop netlogon
13) run below command on all DCs:
Repadmin /syncall /AdeP
Once replication gets complete issue should get resolved.
_________________________________________________________________
Regards,
Shahrukh Shaikh
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
