We have a small network of about 40 workstations mostly running win 7 pro. I have recently been asked to change our screensaver policy increasing the delay from 5 top 10 min. For some reason when i try to run gpupdate /force command on some workstations i get this error: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\administrator>gpupdate /force Updating Policy... User policy could not be updated successfully. The following errors were encount ered: The processing of Group Policy failed. Windows attempted to read the file \\DOAMIN\SysVol\DOMAIN\Policies\{7D3654B1-1401-424B-9AAE-EE3B29C83AB6}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be appli ed 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. 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\SysVol\DOMAIN\Policies\{7D3654B1-1401-424B-9AAE-EE3B29C83AB6}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be appli ed 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. To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f rom the command line to access information about Group Policy results. C:\Users\administrator>

OK, but where is the result of GPO modelling? If you have received a hint, follow recommendations. Regards Milos

I would assume the client is unable to resolve the network location. I would map a network drive to the client machine with the location of the required file. Then I would run the gpupdate again.

Yesterday I reloaded windows7 pro on one of the workstations that was giving the above gpupdate /force error and it fixed the problem. However when I tried to run this command on the same machine today, approx. 24 hours later, the same error re-appeared again. I ran the GPresult command and there is one error in the component status: Component Status Component Name Status Last Process Time Group Policy Infrastructure Failed 8/1/2012 12:24:55 PM Group Policy Infrastructure failed due to the error listed below. Logon Failure: The target account name is incorrect. Note: Due to the GP Core failure, none of the other Group Policy components processed their policy. Consequently, status information for the other components is not available. Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 8/1/2012 12:24:52 PM and 8/1/2012 12:24:55 PM. BUT WHEN I LOG-IN INTO THE WORKSTATION USING LOCAL ADMINISTRATOR ACCOUNT I GET ONLY THE ERROR REGARDING COMPUTER POLICY: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>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 \\dss. hq\SysVol\dss.hq\Policies\{7D3654B1-1401-424B-9AAE-EE3B29C83AB6}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be appli ed 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. To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f rom the command line to access information about Group Policy results. C:\Users\Administrator>