Userenv 1030/1058 on Workstations

[mpapier]

All workstations (XP Pro SP2) are reporting these errors:

Windows cannot access the file gpt.ini for GPO CN={B51CA1C0-3683-41CB-8590-9B89F553549A},CN=Policies,CN=System,DC=xxx-domain,DC=com. The file must be present at the location <\\xxx-domain.com\SysVol\xxx-domain.com\Policies\{B51CA1C0-3683-41CB-8590-9B89F553549A}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.

However, Group Policy is being applied and is working as we'd like. I am wondering if the workstations might all be looking towards an old DC server that is no longer in the environment. And once they fail to read from that server, they look to another and get what they need.

I ran set l on two seperate workstations. They were using different logon servers, but both were reporting thee errors in the application log.

My servers dfo not report any errors with GPO. DFS is enabled, File replication is working properly, etc.

 

[mpapier]

I just noted the following on one of my domain controllers. All the rest are fine:

Windows cannot access the file gpt.ini for GPO CN={79D8A913-3EA5-4D8A-8504-B1CA27C4949A},CN=Policies,CN=System,DC=xxx-domain,DC=com. The file must be present at the location <\\xxx-domain.com\SysVol\xxx-domain.com\Policies\{79D8A913-3EA5-4D8A-8504-B1CA27C4949A}\gpt.ini>. (Logon Failure: The target account name is incorrect. ). Group Policy processing aborted.

 

[porkchopexpress]

If you clear the event log and then reboot the station is the error there?

If so clear the log again and run gpupdate, do you see the error now?

Is this a recent setup or has this just started happening?

 

[mpapier]

After rebooting, the error I had in my application log was Userenv 1054:

Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

After running gpupdate /force, I got my 1030 and 1058 errors again:

1058: Windows cannot access the file gpt.ini for GPO CN={B51CA1C0-3683-41CB-8590-9B89F553549A},CN=Policies,CN=System,DC=xxx-domain,DC=com. The file must be present at the location <\\xxx-domain.com\SysVol\xxx-domain.com\Policies\{B51CA1C0-3683-41CB-8590-9B89F553549A}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.

1030: Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

I've had these errors for some time. I thought it was DFS related because we had DFS disabled on servers until one month ago. After DFS was enabled, similar errors on the DCs discontinued and Group Policies were enforced properly. However, these errors remain on workstations.

 

[porkchopexpress]

Ok i've seen this caused by switches that use spanning tree and don't have pirtfast enabled but if you're still getting it after boot up it's unlikely to be that.


Are you certain that the policy is applying correctly it could be reapplying cached copies, if you make a change on the DC is this applied to the client?


Also are your clients all configured to look for your DNS server for name resolution not your ISP?

 

[mpapier]

All clients are configured to look at two of our internal servers for DNS.

Now that you mention it, I am wondering if only the Default Domain Security Policy is being applied. Do workstations look for this information in a different manner than individual GPOs?

 

[mpapier]

One additional note: If I make a change to a GPO on one DC it is properly replicated to the other DCs.

 

[porkchopexpress]

I'd create a new GPO to test and add some settings to that.

 

[mpapier]

I have created a new GPO and it has applied to workstations successfully. However the 1030/1058 Userenv errors still get logged on these workstations.