(2014-08-02) Fixing AD/SYSVOL Replication And Reconnecting A Disconnected AD Domain (Part 7)
Posted by Jorge on 2014-08-02
PART 6 is here.
WARNING/DISCLAIMER: I provide this information on a FYI basis. Be very very very careful in actually doing these steps on your production systems as it may brake or destroy your AD domain or AD forest. You are fully responsible for any steps you use from this blog post. If you do not understand what you are doing, either hire someone who does, or call Microsoft for support!
According to the DFS Replication Event Log the Staging Area was inaccessible.
Figure 1: Event ID 4212 For The Missing Staging Area
Looking at the folder structure I was missing the folder "staging" and its subfolder "domain" and the "staging areas" with the junction point.
The complete folder structure for the SYSVOL is:
- <Drive>:\<Folder>\<SYSVOL or SYSVOL_DFSR>
- staging areas
- <FQDN AD domain> = JUNCTION POINT to <Drive>:\<Folder>\<SYSVOL or SYSVOL_DFSR>\staging\domain (see: Create the SYSVOL Root and Staging Areas Junction Point)
- <FQDN AD domain> = JUNCTION POINT to <Drive>:\<Folder>\<SYSVOL or SYSVOL_DFSR>\domain (see: Create the SYSVOL Root and Staging Areas Junction Point)
Stopping the DFSR service and then creating the yellow marked folders and junction points, and then restarting the DFSR service again solver all SYSVOL related problems! YES!
Executing DFSRDIAG DUMPADCFG on both RWDCs should show very similar output and the DFSR Service Event Log should show the following event ID:
Figure 2: Event ID 4604 For DFSR Service Having Initialized The SYSVOL And Having Performed Initial Replication
My test environment is running only W2K12R2 RWDCs. However, in the original scenario the ‘C1FSRWDC1.CHILD.ADCORP.LAB’ RWDC was running W2K8R2. Because of that, but also depending on what occurred with the RWDC (e.g. dirty shutdown) you might end up with the event 2213.
EVENT LOG: DFS Replication
EVENT ID: 2213
The DFS Replication service stopped replication on volume D:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="74D84752-A63E-11E0-8F2A-00155D006D28" call ResumeReplication
- Changes that are not replicated to a downstream server are lost on the upstream server after an automatic recovery process occurs in a DFS Replication environment in Windows Server 2008 R2
- DFSR event ID 2213 in Windows Server 2008 R2 or Windows Server 2012
I hope you enjoyed this ride. I did!
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: https://jorgequestforknowledge.wordpress.com/disclaimer/
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
This entry was posted on 2014-08-02 at 23:00 and is filed under Active Directory Domain Services (ADDS), KCC, Metadata Cleanup, Object Deletion/Restore, Promotion/Demotion, Replication, SYSVOL. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.