Recently added a Vista Business workstation to a company's Server 2000 AD Domain. This server acts only as a DC, file and print server. The joining to the domain went fine. No errors. Upon reboot though I noticed Event ID 1058 in the System Log: The processing of Group Policy failed. Windows attempted to read the file \\Domain.local\sysvol\Domain.local\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. Looking at the details tab of this error, the cause was 'Error 5: Access Denied' I have been through every article relating to this error that is currently available. DFS is currently running on the DC and the Vista Business workstation has DFS client set to manual. Active Directory shows the workstation in the Computers Group. DNS shows the correct entries for this workstation. I can access the DC and the path above if I do a 'Start -> Run' and enter the path above. I can also access any other resource(shares) in the domain without a problem. If I perform 'gpupdate' form a command prompt on the Vista machine It states the User Group Policy was successfully applied but then gives me the same exact error as what is seen in the event log (shown above).

Hi, Thank you for your post. I understand that the Event 1058 is logged in the event viewer on the Windows Vista machine after it restarts or tries to update policy. Before we go further, please collect the following information: 1. How many domain controllers are there in this domain? 2. Does the issue occur on every Windows Vista machine? 3. On the Windows Vista machine, please perform the following steps to collect GPSvc.log:==========a. Click Start, type regedit in the Start Search box, and press Enter.b. In the Registry Editor, expand HKLM\Software\Microsoft\Windows NT\CurrentVersionc. Under that, create a new Key called Diagnosticsd. Under that key, create a DWORD value GPSvcDebugLevel and set the value as 0x30002 (hexadecimal)e. In Command Prompt, type gpupdate /force to reproduce the issue.f. After that, please collect gpsvc.log which is located in %windir%\debug\usermode 4. On the Windows Vista machine, please collect the following information:==========System Information:-------------a. Click Start, type msinfo32 on the Start Search box.b. On the System Information window, click File, and click Save to export the system information to a .NFO file.Event Log:------------a. Click Start, type eventvwr on the Start Search box.b. Expand Windows Logs, right-click System, and click Save Event As to export the system event log to a .evtx file.c. Right-click Application, and click Save Event As to export the application event log to a .evtx file.d. Expand Applications and Services Logs\Microsoft\GroupPolicy, right-click Operational, and click Save Event As to export the GroupPolicy event log to a .evtx file.NOTE: please select Display information for these languages, and select English option on the Display Information dialog box.GPResult:------------a. Click Start, type cmd on the Start Search box.b. Right-click cmd icon and select Run as Administrator.c. In the Command Prompt window, type: gpresult > c:\gpresult.txt 5. On all Domain Controllers, please collect MPSReport:a. Download the executable file from the following URL specific to the support issue being experienced.http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_DirSvc.EXEb. Copy the file to the problematic computer.c. Double-click the executable to launch the report gathering tool.d. Accept the EULA.e. Then, the reporting tool begins to gather necessary information on your system.f. After the tool finishes gathering the information, a cab file is generated in the following folder: C:\WINDOWS\MPSReports\DirSvc\cab 6. Please upload above files to the following space:https://sftasia.one.microsoft.com/choosetransfer.aspx?key=02b07a2b-9726-4f91-92df-53cf3d0a6aaaPassword: !uoOG$KDwx9+tY[j Thanks. I look forward to your reply. Sincerely, Joson Zhou Microsoft Online Community Support

I have same problem. need logs?

I'm also seeing this issue. Has anyone found a resolution yet?-dweez