A one way FRS sysvol replication

Posted on 2012-08-24
Last Modified: 2012-08-26
- Main Office: 2x Domain server Windows 2008 (DC1 and DC2)
- Branche Office:  1x Rodc Domain server Windows 2008 (Rodc1)
- Domain functional level: Windows server 2008
- Sysvol replication: FRS
- Several computer and user log files are written to the sysvol directory, for instance to: \\domainname\sysvol\domainname\sys\log\%computername%.log
- DC1 and DC2 (Main Office Site) have an "automatically generated" replication configuration in the Sites and Services snap in. Rodc1 (Branche Office Site) has a (possibly manually) added replication context to DC1.

The logfiles written to the sysvol folders in the Main Office are perfectly replicated from the Main office sysvol directory to the Branche office sysvol directory. But the logfiles written to the sysvol folders in the Brache Office aren't replicated to sysvol directory in the Main Office. A one way replication from the Main Office to the Branche Office. So the main office only has the log files in sysvol from the computers in the Main Office, while the Branche office has the complete both computer logfiles of the Main Office computers as well as the Branche Office.

The domain controler in the Branche Office is a Rodc server. Is this normal behaviour for a Rodc server? Or is there a possible Sites and Services configuration error?

How can I correct this creating a complete 2 way sysvol replication?
Question by:NicoNL
    LVL 33

    Accepted Solution

    The behaviour is normal, RODC will never replicate anything that is on its own box to other RWDC.

    Here, is the link that'll help you understand in detail with examples.

    Bottom-line, what you are seeing is considered normal.

    How can I correct this creating a complete 2 way sysvol replication?

    Add a RWDC in your local site and remove RODC.


    Author Comment

    That's the link I was looking for. Thanks!
    LVL 41

    Expert Comment

    A better solution than using a RWDC is to use a domain based DFS namespace and then replicate the shares to servers at the appropriate sites.

    Write to \\domainname\dfsroot\log\%computername%.log . You can have as many DCs (full or RO) host the DFS namepsace, and then you can have any DC or member server participate in DFS-R replication to host the files you want store.

    FWIW, I map EVERYTHING to a single domain based DFS namespace. That way I can change file servers, domain controllers, etc. without needed to worry about fixing links, drive mappings, or paths on the clients.

    Author Comment

    Thanks for your tip, I'm going to look into that.

    Featured Post

    PRTG Network Monitor: Intuitive Network Monitoring

    Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

    Join & Write a Comment

    Citrix XenApp, Internet Explorer 11 set to Enterprise Mode and using central hosted sites.xml file.
    My experience with Windows 10 over a one year period and suggestions for smooth operation
    Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
    Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

    733 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    20 Experts available now in Live!

    Get 1:1 Help Now