Replication sysvol problem in a windows 2008 2003 environment

Dear Experts,

I am in a messy situation right now with our active directory replications. We recently place 2 windows 2008 server with the idea of replacing 2 windows 2003 servers. We already took one server offline. In one of the server I am getting this error:

The processing of Group Policy failed. Windows attempted to read the file \\is.ad\sysvol\is.ad\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
 
Event ID: 1058


This is from one of the new windows server 2008. Does anyone know how to resolve this issue?

Kindly, thank you so much, M
marceloNYCMiddle-Tier AdministratorAsked:
Who is Participating?
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
You need to run command-line in elevated mode :) Click right mouse button on it and choose "Run as administrator" Then type in command-line

net stop ntfrs

Open in new window


change registry, to set up D2 burflag

and start FRS service by typing

net start ntfrs

Open in new window


in event log search for event id 13565 which means non-authoritative restore has been stared and wait until you will see event id 13516 that SYSVOL is fully operative

From now, everything should work fine. DC reboot is not required

Krzysztof
0
 
Hypercat (Deb)Commented:
Take a look at this article:

http://social.technet.microsoft.com/wiki/contents/articles/1456.event-id-1058-group-policy-preprocessing-networking.aspx

Also, have you tried just restarting the server? I'd advise trying that first. It could be that a service or services are not running for some reason and a restart would ensure that all required services are running.  Also, if you do a restart and some important service doesn't start properly for some reason, you'll see errors in the event viewer that could help in troubleshooting this problem.
0
 
Life1430Sr EngineerCommented:
Check if that server is in Journal Wrap State search for event ID 13568 in FRS logs if you find this event then perform non authorative restore of sysvol using below link

http://support.microsoft.com/default.aspx?scid=kb;en-us;290762&a mp;sd=tech
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Krzysztof PytkoSenior Active Directory EngineerCommented:
Please try to perform non-authoritative SYSVOL restoration using D2 burflag
This should resolve the issue
http://support.microsoft.com/kb/315457

Regards,
Krzysztof
0
 
marceloNYCMiddle-Tier AdministratorAuthor Commented:
I restarted the server and the error message still the same....
0
 
Life1430Sr EngineerCommented:
Ok let me make Non-authorative restore simple

Navigate to regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup in right side u will see BurFlags set the value to "D2" and run
net stop ntfrs & net start ntfrs

Open in new window

0
 
marceloNYCMiddle-Tier AdministratorAuthor Commented:
C:\Users\mzamorano>net stop ntfrs & net start ntfrs
System error 5 has occurred.

Access is denied.

System error 5 has occurred.

Access is denied.

Sarang I got that message....
0
 
marceloNYCMiddle-Tier AdministratorAuthor Commented:
Still the same thing , sorry guys...
0
 
SandeshdubeySenior Server EngineerCommented:
If d2/d4 does not helps check below parameters are set correctly on DC.
1.Ensure correct dns setting on the server.Each DC / DNS server points to its private IP address as primary DNS server and other remote/local DNS servers as secondary in TCP/IP properties
2.Check the permission on problematic gpt.ini file see below link for more details
3.Check that File and print sharing is enabled on the NIC on client and DC.
4.Disable the windows firewall on the DC/client.
5.Ensure that the TCP/IP NetBIOS Helper Service" is started.
6.Run DFSUtil /purgemupcache
7.Run gpupdate /force and check the apllication log.
8.If still the issue persist run the Group Policy Diagnostic Best Practice Analyzer for more details

Reference link:http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/e35e3fb0-7664-4323-9f42-b5315a4b2ca7

Hope this helps
0
 
marceloNYCMiddle-Tier AdministratorAuthor Commented:
Thank you guys the error is gone!!!!
0
 
SandeshdubeySenior Server EngineerCommented:
Nice to hear that the issue is fixed...
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
You're welcome :)

Krzysztof
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.