Techdw Posted February 13, 2013 Posted February 13, 2013 Hi, Am still having a problem on my printerserver, when I run gpupdate /force is says users policy was updated but Computer couldn't b updated. Its saying it cant read the Default Domain Policy GPO Microsoft Windows [Version 6.0.6001] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Users\administrator.DOMAIN>gpupdate /force Updating Policy... User Policy update has completed successfully. Computer policy could not be updated successfully. The following errors were enc ountered: The processing of Group Policy failed. Windows attempted to read the file \\DOMAIN.local\sysvol\DOMAIN.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\g pt.ini from a domain controller and was not successful. Group Policy settings ma y not be applied until this event is resolved. This issue may be transient and c ould 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. So I built another sever using Server 2008 and once it was built ran it again and same error! Would moving the functional level on the DC to Server 2008 r2 cause this?
Jawloms Posted February 13, 2013 Posted February 13, 2013 Can you get to \\DOMAIN.local\sysvol\DOMAIN.local\Policies\{31B2F 340-016D-11D2-945F-00C04FB984F9} from Start -> Run?
slugshead Posted February 13, 2013 Posted February 13, 2013 I had this exact issue earlier on and this is how i bodged it. Two servers in school. One brand new and one old one. AD and GPO's were replicating exactly as I expected. Sysvol wasn't. Manually copied the missing folder and its sub contents to the new server. In your case \\DOMAIN.local\sysvol\DOMAIN.local\Policies\{31B2F 340-016D-11D2-945F-00C04FB984F9}\
slugshead Posted February 13, 2013 Posted February 13, 2013 Also, check the DNS order. I think this had something to do with what happened to me earlier too.
Techdw Posted February 14, 2013 Author Posted February 14, 2013 When i look at Sysvol on the two DC's it is the same! and \\DOMAIN.local\sysvol\DOMAIN.local\Policies\{31B2F 340-016D-11D2-945F-00C04FB984F9}\ exist on both
Techdw Posted February 14, 2013 Author Posted February 14, 2013 We have moved the functional level to Windows 2008 R2 as well and the server is 32bit 2008!
Ric_ Posted February 14, 2013 Posted February 14, 2013 Can you edit the GPO on each DC? (Just right click the top level node to select which DC you are editing on) It could be that one has become corrupt. If you cannot, I would recreate the object and ditch the old one. Also use dcdiag to make sure that your replication is working properly... this could be a symptom of a much bigger problem.
Duke5A Posted February 14, 2013 Posted February 14, 2013 Are other machines having issues reading this policy? If you go into RSOP.msc, right click computer configuration, select properties, and go to the error information it should give verbose error messages. Before getting midevil with it though, if no other machines in the OU exhibit any issues, I would leave the domain and rejoin it.
mehrdadi Posted March 14, 2013 Posted March 14, 2013 Also you can try this: 1. Delete or rename the HOSTS file in c:\windows\system32\drivers\etc\ 2. Go to each GPO and bring up it's Security settings. Uncheck and recheck all the boxes in there that had their switches ON. Do the save for the one's that were OFF. Click apply. This should force a re-write of the ACLs on the GPOs. 3. Move the computer object out of the OU it is currently in and move it back. 4. Restart the netlogon service on the Domain Controller that the user is authenticating with. 5. Restart the File Replication service on DC. 6. Run these commands in order: Dfsutil /purgemupcache Dfsutil /pktflush Dfsutil /spcflush IPCONFIG /FlushDNS IPCONFIG /RegisterDNS GPUpdate /force 6. Like Duke said, leave the domain and rejoin.
mehrdadi Posted March 14, 2013 Posted March 14, 2013 Group Policy settings are not applied on member computers that are running Windows Server 2008 or Windows Vista SP1 when certain SMB signing policies are enabled
mehrdadi Posted March 14, 2013 Posted March 14, 2013 SOLVED: Group Policy gpt.ini Event ID 1058 & 1030 - Daryl Hunter - Network Cowboy
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now