AD Experts, Thanks all for your input regarding the FRS issue listed below. We were able to get a safer solution out from MS to fix SysVol inconsistencies.
Here it is: 1)Fix policies and scripts on the PDC, make sure everything is clean on the PDC 2)Stop FRS service on all other DCs 3)Start with the direct replicating partner of the PDC 4)Open up the registry and go to Hkey local machine, system, current control set, services, ntfrs, parameters, replica sets 5)Locate the guid which corresponds to the sysvol , click on the guid which corresponds to sysvol under cumulative replica sets ( which is just above replica sets) 6)Do a D2 on the burflags , restart FRS 7)Wait for some time as there are a lot of policies and scripts and it will take some time before everything gets replicated over 8)Once you have a 13516 in your FRS logs you can proceed to the next DC and go through step4 to step7 9)You might notice some warnings in FRS from other DCs but that's normal since FRS service is stopped on them This is a safer solution since only one server is replication FRS with PDC at a time. I applied this fix and it seems to have stablized SysVol. -Adeel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Cliffe Sent: Wednesday, February 01, 2006 4:39 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] NTFRS Problems I can tell you that I used this KB as my guide to restore the SYSVOL state on one of our domains about 4 months ago and it worked just fine. http://support.microsoft.com/kb/315457/en-us If the journals on your DCs are inconsistent with each other, this may be the best way to correct it. Best advice is to ensure that there are no underlying replication issues first, otherwise you might just be wasting your time! -DaveC -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adeel Ansari Sent: Wednesday, February 01, 2006 5:10 PM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] NTFRS Problems Hello AD Experts, Recently, I noticed in-consistencies in Sysvol among my domain controllers and PDC while promoting a new replica DC in the domain and it stucked on sysvol after 145 out of 250 policies. To test further, I created a .txt file in the sysvol on PDC and it also didnt replicate to other DCs either. To make things even worse, the number of policies on PDC are not the same as in other DCs. After hours of troubleshooting and a phone call to M$, I was told by Microsoft to perform burflag authoritative (D4) restore on one Domain controller with good policy contents in Sysvol and non-authoritative (D2) restore on all the others. Having a luxury of a AD replica lab, I performed the operation in the lab environment but lost both the policies, scripts folders and now the servers dont even have Sysvols. I am not comfortable doing this operation in the production environment. Can anyone please share their experience with burflag restores? Any best practices? Is there another way that I can resolve this issue without perform burflag restore? Any ideas / suggestions are welcomed. Regards, Adeel _______________________________________ Adeel Ansari - Active Directory Admin. SLB Enterprise Services Houston, TX USA List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ To find out more about Reuters visit www.about.reuters.com Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd. List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
<<attachment: winmail.dat>>
