Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 961
  • Last Modified:

Errors userenv 1058 and 1030

Hello experts,
 
I had two domain controllers withe Windows Server 2003 SP2. Some days ago, I had to remove (forced remove) one of them, and the other one had to take all the roles. We had a bunch of issues regarding active directory replication, but at the end we made everything work correctly.
 
The domain control functionality seems to work fine. We can create users, modify them, log in computers to the domain, users can log in and so on.
The only issue is that each 5 minutes we get a a pair of errors UserEnv 1030 and 1058 in the event log:

1030 is Windows cannot query for the list of Group Policy objects.
1058 is Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=MyDomain,DC=org. The file must be present at the location <\\MyDomain.org\sysvol\MyDomain.org\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. ). Group Policy processing aborted.
 
 
Error 1058 tell us that the file gpt.ini in Policies folder can't be accessed. It's no surprise, as that folder and files structure does not exist in SYSVOL.
 
Taking a look to a backup, when the two DC still existed, all those files and folders existed.
 
How should us fix these errors?  Should we just copy back the files from the backup or is it somehow dangerous? Should we do anything else?
 
Thanks in advance,
     Gregorio
0
McGregor09
Asked:
McGregor09
1 Solution
 
Matt VCommented:
You can safely copy back the policies and scripts folder from a backup.  We often do this when doing a disaster recovery restore of the main DC.

You will probably need to reboot for this to take effect.
0
 
Darius GhassemCommented:
Make sure you run a metadata cleanup to remove any objects from the failed DC.

http://www.petri.co.il/delete_failed_dcs_from_ad.htm
0
 
McGregor09Author Commented:
Thanks!

We copied the policies back and everything worked fine after rebooting :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now