Windows 2003 replication sysvol

Improve this question. Add a comment. Active Oldest Votes. Before you try any of that, though, I'd at least make a current System State backup to disk. Improve this answer.

Evan Anderson Evan Anderson k 18 18 gold badges silver badges bronze badges. Spot on Evan! I had half-read that MS KB, and didn't seem clear that it would rebuild the journal. Everything is peachy now, thanks! Sign up or log in Sign up using Google.

Sign up using Facebook. Once done you can promote the Server back as ADC. Saturday, December 3, AM. Saturday, December 3, PM. Monday, December 5, AM. Hi all,. I will be at the client site in a few days and will dig more into your responses and post appropriate logs, etc.

Also, I do realize Windows is a risk, and actually that's our main project out there: to decommission this box and take it out of the environment. One thing I didn't mention in the last post as I feared it might add confusion is that I tried to introduce a new DC called DC02 into the environment, but it is behaving like DC1 in that it has never replicated the sysvol share.

Essentially, I'd like to get DC02 and DC1 to have the sysvol folder replicating successfully, then I can yank S01 out of the environment. So I guess what I'm looking for is recommendations for best plan of attack - should I try to get the new DC02 replicating the sysvol folder, or do I need to address the possibly tombstoned situation first? Wednesday, December 7, PM. Thursday, December 8, AM. Sandesh, Thanks so much for your response.

Just so I'm absolutely clear on the steps can you verify that this summary is correct: 1. Sound good? Thanks, Brian. Wednesday, December 14, PM. Hi, Is it possible to still get some help with this?

However, it may also be manually enabled on Windows Server R2 servers. For each domain controller enabled for content freshness, evaluate if DFS Replication has logged an event ID that indicates replication of the folder has stopped because replication has failed for longer than the MaxOfflineTimeInDays parameter. For any domain controllers running Windows Server R2, first install DFS Replication updates to prevent data loss and to fix known issues.

It's a best practice to use the latest version of DFS Replication. Backups may be a file copy of the SYSVOL contents to a safe location or, it may be a backup that uses backup software. Depending on the situation, policy files could be moved to PreExisting or Conflict and Deleted. PreExisting and Conflict and Deleted contents will be purged if initial synchronization is done multiple times on a server. Back up data in these locations to avoid data loss.

Based on the number of domain controllers in the domain, select the appropriate method to recover the DFS Replication service. Determine whether a dirty shutdown was detected event ID on either domain controller. The reason is, after promotion, it will log a event that indicates that DFS Replication is waiting to do initial replication. You don't have to configure the second domain controller as nonauthoritative, because it's already waiting to do initial synchronization.

Otherwise, any existing data present on first domain controller not present on the second will go into the PreExisting and Conflict and Deleted folders. Confirm that an event ID is logged to indicate the membership is disabled. Enable the first domain controller's membership, and wait for the and events that report completion of the initial synchronization. If necessary, restore any updated files from PreExisting to the original location. If the first domain controller is in the event ID state, and the second domain controller has never completed initialization after it was promoted, and content freshness hasn't been triggered.

To complete this step, examine Active Directory to determine the group policies that are still used and that contain orphaned data. Policy information is located in the Group Policies container. To view this container, follow these steps:. On the View menu, select Advanced Features if it is not already selected. Expand the domain container, expand the System container, and then expand the Policies container. If any domain controller that is participating in the domain has a newer version of a Group Policy in its local SYSVOL tree, make sure that it is copied to a temporary location on the reference domain controller.

On the reference domain controller, delete any files or folders that are in the FRS replica set root or in the replica set stage folders.

On the reference domain controller, move the policies and scripts folders and the folder contents from the temporary location that you used in step c to the FRS replica set root folder. On all domain controllers except the reference domain controller, configure the FRS to be non-authoritative. This approach helps avoid overloading a single domain controller or causing the FRS to source its contents from a domain controller that has not completed its own re-sourcing of the system volume.

This process involves setting the Burflags registry entry to D2 on all hub site domain controllers before proceeding to branch office or to satellite sites. Use the Replica Set Parent registry entry to specify a source domain controller for the D2 setting:. We don't recommend that a single domain controller becomes the source for more than 10 to 15 domain controllers at the same time.

If you must source more than 15 domain controllers off a single source, start the FRS on only 15 downstream partners of any particular source domain controller, and then wait for them to complete sourcing the SYSVOL tree before the FRS service is started on the next group of 15 computers. On all domain controllers in the domain except the reference domain controller, delete any files or folders under the FRS replica set root and the replica set stage directories. This step eliminates the need for the FRS server to move the existing contents before replicating the new data.

This step is not required but it is recommended. Stop FRS on all domain controllers in the domain and set the service to Disabled. You may have to copy additional policies depending on Group Policy requirements for the environment.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback?