General discussion


Strange errors after moving office

By toreador ·
I moved a company?s servers to a new location over the weekend and now many of the servers are getting these errors in the system logs;

Event Type: Error
Event Source: Userenv
Event Category: None
Event I 1000
Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.
Access is denied

On others I am getting a similar error:

Windows cannot access the registry information at \\\sysvol\\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (53).

There are no roaming profiles enabled. This doesn't appear to be causing any issues but the locals want to know what the errors mean or what is causing them. I did some limited googling but did not find anything helpful and I do not have a lot of time to spend on this issue. Any ideas?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to Strange errors after movi ...

Could be any number of things.

Check your DNS settings.

Check that AD sites and services matches the subnet information for where you are.

Also can try this:

This happens if a user right in a policy is being applied to a user or group that no longer exists. The policy is refreshed every 5 minutes on a DC and when it looks for the account, it generates this error. You can enable group policy process logging to find out which account or group is doing this. A registry value creates a log file during policy propagation. The log file is located in "systemroot\Security\Logs\Winlogon.log". You can examine this log file to identify specific errors that occur during policy propagation to the computer. The registry key is:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{827D319E-6EAC-11D2-A4EA-00C04F79F83A}"
For the new registry value, type: "ExtensionDebugLevel"
For the registry data type, put: "REG_DWORD"
For the registry data, type: 2.
After changing this value, go to a command prompt and type "secedit /refreshpolicy machine_policy /enforce" Check the "winlogon.log" file for errors to determine the account that is causing the problem.

Collapse -

by sgt_shultz In reply to Strange errors after movi ...

something tells me a whole lot more than just moving the machines went on...but whatever. we are up for taking a swing at it on your feeble data...
my guess: somebody ditched the sysvol folder on the server. you maybe?
you cn restore from backup or recreate it. since you were scant with info, that is all the clues i'm gonna give...(tease)

Collapse -

by toreador In reply to

This answer wasn't worth reading! All DC's were shut down and came back up cleanly. The ONLY indication that it wasn't a flawless move are these errors; which are causing no issues, the office just wants to know what they are. I installed UPHClean and the errors are gone but I am still curious what caused them in the first place.

Related Discussions

Related Forums