G
Guest
Hi,
I've got an unusual problem. Some Windows 2000 workstations in my
environment will lock themselves when no user is logged in. They display the
message "Only or an administrator can unlock this computer". It is exactly
the issue described here:
http://support.microsoft.com/kb/242917
However, the default screensaver is just fine! After hours of investigating
I discovered that some user policies are being applied before anyone logs in!
The user policies associated with the usual user of the machine got "stuck"
and are applied as soon as the machine starts. Of course, the user policy
enforces a mandatory screensaver that locks the computer, causing this issue.
I found that if I remove the user from her OUs, it does not change the
"stuck" policies that get applied. Also, I can see that the user policies
that are in place before logon have not refreshed for many months, using
gpresult. Somehow it got "locked in" and it's just in there, forever. When a
user actually logs in to the machine, they disappear and the user gets their
usual policies. Once they log out, these months-old policies come back into
effect.
We're on a Windows 2000 domain, and this has happened to about a dozen of
our 250 Win2k workstations.
So the big question, does anyone know how to fix this?
I've got an unusual problem. Some Windows 2000 workstations in my
environment will lock themselves when no user is logged in. They display the
message "Only or an administrator can unlock this computer". It is exactly
the issue described here:
http://support.microsoft.com/kb/242917
However, the default screensaver is just fine! After hours of investigating
I discovered that some user policies are being applied before anyone logs in!
The user policies associated with the usual user of the machine got "stuck"
and are applied as soon as the machine starts. Of course, the user policy
enforces a mandatory screensaver that locks the computer, causing this issue.
I found that if I remove the user from her OUs, it does not change the
"stuck" policies that get applied. Also, I can see that the user policies
that are in place before logon have not refreshed for many months, using
gpresult. Somehow it got "locked in" and it's just in there, forever. When a
user actually logs in to the machine, they disappear and the user gets their
usual policies. Once they log out, these months-old policies come back into
effect.
We're on a Windows 2000 domain, and this has happened to about a dozen of
our 250 Win2k workstations.
So the big question, does anyone know how to fix this?