Managing Multiple User Boot Setups

[David]

I have a PC with XP/Home SP3

I am using the PC in a daycare setting where staff & kids have access
to the same pc. Here is what I would like to do. I would appreciate
knowing if it can be done and how to do it.

User 1: Administrator account with password
User 2: User Account (Limited Access) with password for staff access
User 3: User Account (Limited Access) NO PASSWORD for kids access

I have noticed that XP/HOME will allow multiple users to be logged on
at one time. I want to prevent this. That is, only one user at a
time logged in. When a different user logs in, the previous user is
automatically logged off.

I want the pc (from a cold boot) or a reset to boot up in the kids
user account (NO PASSWORD) bypassing the login screen completely.

These last two desires were easily implemented in Win/2000. I have
been unable to figure out how to implement them in XP/HOME.

Any help would be appreciated.

David

 

[Anteaus]

I have noticed that XP/HOME will allow multiple users to be logged on
at one time. I want to prevent this.

Disable the Fast User Switching service in services.msc

I want the pc (from a cold boot) or a reset to boot up in the kids
user account (NO PASSWORD) bypassing the login screen completely.

Run 'control userpasswords2' select the required user and untick 'Users must
enter a password...'

To access other accounts you then need to log-off holding down the shift key.

 

[David]

Disable the Fast User Switching service in services.msc


Run 'control userpasswords2' select the required user and untick 'Users must
enter a password...'

To access other accounts you then need to log-off holding down the shift key.

Anteaus:

Thanks so much for the advice. It all worked very well.

The one item you mentioned: control userpasswords2, are there a list
of items that could give the control program other uses (other than
userpasswords2)? Could you provide a reference that I could access in
the future?

David

 

[Anteaus]

This is not clearly documented.

Control {appletname} will work with any .CPL file in the windows\system32
folder. But, it also works with several which aren't .CPL files as such, and
which don't appear as Control Panel icons.

I suppose any arrangement with a 100%-logical behaviour would be too
simplistic for Microsoft programmers. <g>