Link to home
Start Free TrialLog in
Avatar of Muahammad
Muahammad

asked on

SysVolum is Not replicating belween Domain Controller

Hi All,

Recently I am facing issue with Group policy Replication and While am checking on SYSVOL folder on PDC its showing all the policies, But in ADC newly  created policies are missing and inaccessible showingwhile am trying to detect now on the group policy objects . and also i can't acces netlogon/sysvol its is showing acces denied (Prompting user name password)by IP, but can acces by FQDN
I chechecked syvol folder security its included authenticated user and Administrator and everyone.
User generated imageUser generated imageUser generated image################################################################################################

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
 
 Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 Replica root path is   : "c:\windows\sysvol\domain"
 Replica root volume is : "\\.\C:"
 A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.
 
 [1] Volume "\\.\C:" has been formatted.
#################################################################################################
The File Replication Service is having trouble enabling replication from Server-DC01 to Server-DC02 for c:\windows\sysvol\domain using the DNS name server-dc01.demo.localL. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name server-dc01.demo.localL from this computer.
 [2] FRS is not running on server-dc01.demo.localL.
 [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
 
 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
###########################################################################################################

dfsdiag /testdcs

Validating site associations...

Validating the site associations on every domain controller of the following: Server-DC01
Success: The site associated with the following host name is consistent on all accessible domain controllers: Server-DC01

Validating the site associations on every domain controller of the following: Server-DC02
Success: The site associated with the following host name is consistent on all accessible domain controllers: Server-DC02
Finished TestDcs.

#####################################################################################
dcdiag(Only geting below erorr)

 Starting test: FrsEvent
         There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL
         replication problems may cause Group Policy problems.
         ......................... Server-DC02 passed test FrsEvent
  ......................... Server-DC02 passed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 03/31/2020   14:41:59
            Event String:
            DCOM was unable to communicate with the computer JBIZU-DC02.JBIZU.LOCAL using any of the configured protocols; requested by PID     1cf4 (C:\Windows\system32\taskhostw.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 03/31/2020   14:41:59
            Event String:
            DCOM was unable to communicate with the computer JBIZU-DC02.JBIZU.LOCAL using any of the configured protocols; requested by PID     1cf4 (C:\Windows\system32\taskhostw.exe).
         A warning event occurred.  EventID: 0x000003FC
            Time Generated: 03/31/2020   14:44:12
            Event String: Scope, 10.10.10.0, is 92 percent full with only 3 IP addresses remaining.
         A warning event occurred.  EventID: 0x00000560
            Time Generated: 03/31/2020   14:44:12
            Event String: IP address range of scope 10.10.10.0 is 92 percent full with only 3 IP addresses available.
         ......................... Server-DC02 failed test SystemLog
      Starting test: VerifyReferences
         ......................... Server-DC02 passed test VerifyReferences
######################################################################################
C:\Windows\system32>repadmin /replsummary
Replication Summary Start Time: 2020-03-31 15:01:12

Beginning data collection for replication summary, this may take awhile:
  .....


Source DSA          largest delta    fails/total %%   error
 Server-DC01             03m:51s    0 /   5    0
 Server-DC02             10m:08s    0 /   5    0


Destination DSA     largest delta    fails/total %%   error
 Server-DC01             10m:08s    0 /   5    0
 Server-DC02             03m:51s    0 /   5    0
####################################################
ASKER CERTIFIED SOLUTION
Avatar of Hello There
Hello There

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Hello There
Hello There

And after you fix the issue, I recommend you to migrate to DFSR.
1. Perform on all DCs: Server Manager -> Manage -> Add Roles and Features -> select the DFS Replication role -> Install
2. Then run from the PDC:
Dfsrmig /setglobalstate 1
Dfsrmig /getmigrationstate
Dfsrmig /setglobalstate 2
Dfsrmig /getmigrationstate
Dfsrmig /setglobalstate 3
Dfsrmig /getmigrationstate

Open in new window

https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405
Yes, please migrate from FRS to DFSR after replication is fixed.
Avatar of Muahammad

ASKER

Hi Hello There,

thank you for explained reply

I have one more question. my primary domain controller giving the 13568 event id on PDC and When I create group policy object it s creating sysvol.
please tell me I will proceed same step or D2 value on PDc and D4 on secondary.
Yes. The same rule applies.
Healthy DC - set the D4 option
Bad DC - set the D2 option
ok Thanks
I will try tomorrow and update you
and I have noticed one I can access sysvol with fqdn but unable to access with DC ip address
Thank You All, It is working perfectly
You are welcome!