Solved

Active Directory FRS errors

Posted on 2015-02-16
4
76 Views
Last Modified: 2015-07-01
Hey there,

I have 3 DCs between 2 offices:

- oldDC (SBS 2011)
- newDC (2012 R2)
- remoteDC (2012)

newDC was just promoted as a domain controller. We will eventually get rid of oldDC and rely only on newDC in the main office. For now though, oldDC still has all FSMO roles as required by SBS.

I noticed that newDC had SYSVOL/NETLOGON replication errors. Right now it isn't even sharing either folder. I looked into Event Viewer on oldDC and found that it is in journal wrap state. I thought an easy fix would be set BurFlags to D2 on oldDC and newDC and set D4 on remoteDC. However, remoteDC is also not replicating because of oldDC's journal wrap state.

From what I understand, D4 should only be set on a known, good working copy of SYSVOL. Since oldDC has the journal wrap error, I'm worried about setting D4 on it. I also don't have a good, working copy of SYSVOL from a backup.

What do I need to do to resolve this? Additionally, information about backing up all data before I start trying to resolve this would be much appreciated since I don't have a known good backup.

Thanks!
0
Comment
Question by:mjm11
4 Comments
 
LVL 21

Expert Comment

by:RK
ID: 40613747
Hi,

Yes, you need to set D4 On the server which has a good copy of Sysvol, mark the Sysvol structure as the Source. Unfortunately you are not confident about which server has got good copy of Sysvol? So i would suggest to run this MS tool http://www.microsoft.com/en-in/download/details.aspx?id=30005 and identify the replication status.

Once you identified the server then go for the normal Burflag process.
0
 
LVL 24

Accepted Solution

by:
VB ITS earned 500 total points
ID: 40614027
Ran into this exact issue myself last week. Promoted a new 2012 R2 machine to a DC in a SBS 2011 environment and found out that the SYSVOL and NETLOGON shares weren't replicating to the new 2012 R2 DC.

Here's what I did to fix the issue:
- Stop the File Replication Service service on all of your DCs
- On the SBS 2011 server, browse to C:\Windows\SYSVOL\sysvol\yourdomain.local
- Back up the existing Scripts and Policies folders in here to another location for safe keeping or rename them to Scripts.old and Policies.old
- Browse to C:\Windows\SYSVOL\sysvol\yourdomain.local\NtFrs_PreExisting___See_EventLog
- Copy the Scripts and Policies folders in here to C:\Windows\SYSVOL\sysvol\yourdomain.local

Now we need to do an authoritative restore for DFS:
- Still on your SBS 2011 machine, open the Registry Editor
- Browse to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup

Open in new window

- Double click BurFlags and change the value to D4
- Start the File Replication Service service on your SBS 2011 server
- Monitor your event logs to verify that the Journal Wrap error has been resolved and that AD is healthy again (Event ViewerApplications and Services LogsDFS Replication, Directory Service, etc.)
- Once you have verified that Journal Wrap error has been addressed, set BurFlags to D2 on your other DCs and start the FRS service
- Review the logs again and verify that the SYSVOL and NETLOGON shares have been created and are replicating on your new 2012 DCs
- Providing everything goes to plan, you should be able to see the SYSVOL and NETLOGON shares get created on your 2012 DCs and the Policies and Scripts folder have been replicated from your SBS 2011 server

Let me know how you go with the above.
0
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 40861240
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

820 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