Pop,
1. IF, when there are multiple accounts present (as in my own case), and a
method other than the one I described were previously used to configure
auto-logon, that going in thru Control Panel can NOT be used to make the
changes?
Yes. This is because the automatic logon credentials still remain in the
registry, and automatic logon continues to happen.
2. If it were a third party app I could see it; the app has been put in
charge of the settings and even if you did change it, the app would just put
it back; right?
May be, but it depends upon the application. TweakUI and AutoLogon (from
www.sysinternals.com) don't automaticlly put the credentials back.
3. Are you saying that Case #2 is the same as if it were a 3rd party app and
negates the Control Panel ability to use User Accounts for changing it?
Would it be similar using Group Policies?
Nope. Not similar to GPO. My point is that assigning password to an user
account (via User Accounts applet) does not remove the credentials already
stored (using userpasswords2 method / TweakUI / other tool). The
username/pwd still remain in the registry, in a protected area of course, in
an encrypted form.
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting
http://www.winhelponline.com
Ramesh said:
Automatic logon occurs due to two different reasons:
1. There is a single user account in the system, and is not password
protected.
2. There are multiple accounts present, but the user had configured
automatic logon earlier (using the userpasswords2 method, TweakUI or
any other third-party tool)
Your tip addressed case #1, and Nepatsfan addressed case #2. Both are
correct, BTW.
Yes, I didn't mean to imply that the preceding case wasn't correct.
Hmm, I'm learning something new I think. To clarify, you are saying that
IF, when there are multiple accounts present (as in my own case), and a
method other than the one I described were previously used to configure
auto-logon, that going in thru Control Panel can NOT be used to make the
changes?
If it were a third party app I could see it; the app has been put in
charge of the settings and even if you did change it, the app would just put
it back; right?
Are you saying that Case #2 is the same as if it were a 3rd party app and
negates the Control Panel ability to use User Accounts for changing it?
Would it be similar using Group Policies?
Normally I'd just go test it, but since I feel there are some details I'm
not aware of, I'd rather ask for more info first. I do have Norton's Sysem
Optimizer, but I avoid using it simply because it does take control away
from where XP indicates it is available, and without notice. I'd rather
learn the policies etc.; then I know where things came from months down the
line when I've forgotten<g>. So far I haven't found anything Norton ca set
that isn't natively available in XP, though it's useful for discovering what
IS available to change.
TIA,
Pop`