RE: Group policy gets "stuck" on workstation
- From: Taimour Al Neimat <TaimourAlNeimat@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 13 Mar 2007 05:41:03 -0700
Hello Jesse,
I think I used my common sense when I said it is not possible. I was wrong,
sorry for that.
I’m sure you tried the resolution on that support article and it did not
work for you.
I will suggest another approach. Why do you want to use a screen saver while
waiting for someone to log on locally? Just tell the system that when no
one’s logged in (e.g., when the .DEFAULT profile’s being used) that you don’t
want a screen saver to run.
This can be done by performing these steps:
1. Start Registry Editor
2. Select the following key: HKEY_USERS\.Default\Control Panel\Desktop
3. Locate the ScreenSaveActive value
4. Modify it to zero
5. Restart the computer
Please keep me updated.
--
Eng. Taimour Al Neimat
Amman - Jordan
Infrastructure Specialist
MCT, MCSE, MCDBA, MCSA, CCNA, CWNA
"Jesse" wrote:
.
If you read the article below, you will see that it is indeed possible for a
computer to be locked with no user logged in:
http://support.microsoft.com/kb/242917
I've done the steps you describe, AutoAdminLogon is already set to 0.
I will try to describe the symptom more clearly:
When the computer is rebooted, it displays "Press Ctrl-Alt-Del to begin" as
it normally should. After 7 minutes of doing nothing, it suddenly locks. It
then says "This computer is in use and has been locked. Only or an
administrator can unlock this computer."
Note that it does not say "Only USERNAME or an administrator can unlock this
computer" as it normally should! The user is missing from where it normally
would be, the reason is that no one is logged on.
Thanks, any help is appreciated.
"Taimour Al Neimat" wrote:
It is not possible for a computer to be locked when no user is logged in.
Make sure that automatic logon options are not enabled.
Verify this by performing these steps:
1. Open regedt32.
2. Select the following key: HKLM\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon
3. Double click the AutoAdminLogon key.
4. Modify it to a zero or ensure that it does not exist.
5. Close regedt32.
--
Eng. Taimour Al Neimat
Amman - Jordan
Infrastructure Specialist
MCT, MCSE, MCDBA, MCSA, CCNA, CWNA
- Follow-Ups:
- RE: Group policy gets "stuck" on workstation
- From: Jesse
- RE: Group policy gets "stuck" on workstation
- Prev by Date: Re: How do you set a WINS server?
- Next by Date: Re: AD Sites and Services wrong replication server
- Previous by thread: AD Sites and Services wrong replication server
- Next by thread: RE: Group policy gets "stuck" on workstation
- Index(es):
Relevant Pages
|