Agreed. Good point Charles, thanks for the clarification. My, rather general, answers were simply to Daniel's request for elucidation.
- WJR 🙈🙉🙊 On Mon, Feb 10, 2014 at 12:05 PM, Charles Sullivan < [email protected]> wrote: > This is sure to add to the confusion, but I think it’s important to > note…… > > > > Even though FRS has been replaced in newer versions of Windows/AD, after > you migrate a domain to Windows 2008, 2008R2, 2012, or 2012R2, even after > getting rid of the Windows 2003 DCs and even after raising the domain > functional level, you still will need to use the following procedure to > switch from FRS to DFS for replicating sysvol: > > http://technet.microsoft.com/en-us/library/dd640019%28WS.10%29.aspx > > (There is a link to that from the first link that William provided.) > > > > FRS can remain as the method for doing the replication, but you will read > all kinds of reasons for switching to the newer, better DFS. > > > > I wanted to add that because it says “FRS has been replaced…..”, which can > be misleading. > > > > Charlie Sullivan > > Sr. Windows Systems Administrator > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *William Robbins > *Sent:* Monday, February 10, 2014 10:28 AM > *To:* [email protected] > > *Subject:* Re: [NTSysADM] Recovering From Dirty Shutdown On DCs Using > DFS-R For Sysvol Replication > > > > Define "AD Replication." I suspect you are thinking of FRS from the > 2000/2003 era of ADDS: > http://technet.microsoft.com/en-us/library/6405fa66-e47b-4e17-b602-7015d6052c00 > > "File Replication Service (FRS) is a technology that was originally > introduced on Windows 2000 Server to replicate Distributed File System > (DFS) folders and the SYSVOL folder on domain controllers." > > > "FRS has been replaced in Windows Server 2012 R2, Windows Server 2012, and > Windows Server 2008 R2 by DFS Replication for replicating DFS folders and > for replicating the SYSVOL folder." > http://technet.microsoft.com/en-us/library/cc771058.aspx > > Now if indeed you did mean AD Replication, then the answer is no, it did > not, does not, will not. This is what AD replication is about: > http://technet.microsoft.com/en-us/library/cc755994%28v=WS.10%29.aspx > > > > - WJR > 🙈🙉🙊 > > > > On Mon, Feb 10, 2014 at 9:06 AM, Daniel Chenault <[email protected]> > wrote: > > Someone correct me if I'm wrong but isn't replication of SYSVOL handled > by AD replication already? > > > On Feb 10, 2014, at 1:22, "Aakash Shah" <[email protected]> wrote: > > I had some questions and need some advice regarding recovering from a > “dirty shutdown” on both/all of DCs in a domain that are using DFS-R for > both the SysVol folder as well as a file share. > > > > *Background* > > I am helping a new environment that is experiencing problems where Group > Policies are not applying correctly. Upon closer inspection, I learned > that DFS-R is not correctly replicating the contents of Sysvol. > > > > *Setup* > > · 2 Windows Server 2012 Standard (not R2) Domain Controllers at > 2008 R2 domain and forest functional levels. > > · Sysvol replication is being done by DFSR (both server’s DFSR > migration state is at “eliminated”) > > · Both DCs are also file servers and use DFSR to replicate the > “My Documents” file share between the two servers. > > > > *Error Messages and Symptoms* > > · Event ID 2213 started to appear on 5/4/2013 on DC1, and on > 4/30/2013 on DC2 about once a month in pairs for both the C: and D: > indicating: > “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.” > > > > · GPMC reports that the GPO versions are not in sync. > > > > · The Sysvol folders do not have the same number of GPO folders. > > > > *Potential Resolution* > > From the event log as well as some reading I’ve done, it appears that I > need to back up the Sysvol files and run the following for each of the 2 > volumes: > wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where > volumeGuid="GUID" call ResumeReplication > > And since it’s been more than 60 days, it appears that I will need to > change MaxOfflineTimeInDays to allow this server to perform the recovery > process. > > *Questions* > > 1. Am I on the right track to solve this problem (with what I > mentioned in the “Potential Resolution” area, or are there different steps > that I should be taking? If there is any other information that I need to > be aware of, please let me know. > > 2. Since both/all of the DCs have this problem, will running these > commands pose any problems? I assume that I will need to run these > commands on both DCs? I plan to run them about a day apart. > > 3. Since this server is also a file server that has a file share > being replicated with DFS-R, will I need to take any special precautions > during this recovery? > > > > Any help/advice would be appreciated. Thanks! > > > > -Aakash Shah > > > > >
