Jump to content

Recommended Posts

Posted

Hi all,

I've been having more problems with Group Policy. This time with errors in the event log. The event ID's are 1030 and 1058. Supposedly to do with access problems with the gp.ini file in SYSVOL. This server is one of two on our network, fresh rebuilds, with no fiddling with permissions on my part. Has anyone else come accross this when building new servers and setting up GP for the first time?

 

I'd be greatful for any info.

 

Regards

Maximus.

Posted

For event 1030:

 

The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.

 

If you runs Vista here is a hotfix Error results when you run the "gpupdate /force" command on a computer that is running Windows Vista: "User policy could not be updated successfully"

 

for event 1058:

 

The processing of Group Policy failed. Windows attempted to read the file %9 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

 

Try doing this in run and see what happens.

 

\\domaincontroller\netlogon

 

&

 

\\domaincontroller.domainname.whatever\netlogon

 

&

 

\\domainname.whatever

Posted

Hi,

 

The first two givs me the netlogon share (empty) in windows explorer.

 

The third one brings up exploerer populated with shares and shared printers.

Posted

It looks as though I may have found the problem. I rebooted the server and when it restarted it came up with a windows scripting error pointing to a start up script i was using to attach printers based on users OU. I removed the script from Group Policy, reboooted and no more errors have been logged since then.

 

Maximus

:)

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...