"Domain System Volume" replication group schedule

Enrico Giacomin 1 Reputation point
2021-08-23T11:22:46.623+00:00

Hello,

I recap this thread to ask you to clarify some aspects of the DFSR Replication of the SYSVOL:

Hello,

I recap this thread to ask you to clarify some aspects of the DFSR Replication of the SYSVOL:

  1. Does the replication schedule follow the ADDS Replication (the replication time configure in IP Site Link) as @Alvwan wrote in the mentioned thread?
    I had a similar issue by a client. In my troubleshooting steps I demoted the Domain Controller in site B and promoted back. The Sysvol was replicated successfully, but, after the first replication, new changes to the sysvol contents in site A were not replicated to domain controller in site B. Additionally, no errors appeared in Event viewer.
    So I tried to change the ADDS IP site link replication time. Then, I replicated AD and launched the command Update-DfsrConfigurationFromAD.
    Were my actions correct to solve an issue that the sysvol replication between site occurs only if I force it? Effectively, after I made these configurations, a new folder created inside the sysvol folder of a domain controller in Site A, immediately replicated in the domain controller in SiteB.
  2. What is the default schedule of the Domain System Volume replication group?
  3. Is there any way to check and alter the Domain System Volume replication group schedule?

So, I ask your help to understand why the issue seems to be solved with these two actions and give me some docs articles that help me to clarify.

Thanks and kind regards.

Enrico Giacomin

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,133 questions
0 comments No comments
{count} votes

9 answers

Sort by: Most helpful
  1. Dave Patrick 426.4K Reputation points MVP
    2021-08-23T14:09:07.13+00:00

    Should be 180 minutes between sites by default. You can right click then click Edit Replication Group Schedule to change it.
    https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/determining-the-interval

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Dave Patrick 426.4K Reputation points MVP
    2021-08-24T01:41:45.817+00:00

    Just checking if there's any progress or updates?

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  3. Dave Patrick 426.4K Reputation points MVP
    2021-08-24T09:40:05.73+00:00

    your indication is correct for other DFS replication group, not for the Domain System Volume Replication group

    Not sure what is meant, you can define it here.

    126008-image.png

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  4. Dave Patrick 426.4K Reputation points MVP
    2021-08-24T15:45:15.43+00:00

    Just checking if there's any progress or updates?

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  5. Limitless Technology 39,491 Reputation points
    2021-08-26T09:47:22.133+00:00

    Hello Enrico G,

    Thank you for your question.

    Please follow these steps, it will help you:

    Syntax

    Get-DfsReplicationGroup
    [[-GroupName] <String[]>]
    [-IncludeSysvol]
    [[-DomainName] <String>]
    [<CommonParameters>]

    The Get-DfsReplicationGroup cmdlet retrieves existing replication groups.

    A replication group is a set of servers, or members, that participate in the replication of one or more folders. A replicated folder is kept synchronized among the members of a replication group. The Distributed File System (DFS) Replication Get-* cmdlets are useful for pipeline operations or inventory.

    For more information please go through this link:
    https://learn.microsoft.com/en-us/powershell/module/dfsr/get-dfsreplicationgroup?view=windowsserver2019-ps

    If the reply was helpful, please don't forget to upvote or accept as answer.

    Thanks,

    Bharti B

    0 comments No comments