L
LUE42
I hope I can describe my problem sufficiently.
SCENARIO: I am using SMS to push a winbatch job which sets the
autoadminlogon information, reboots and proceeds to install some
software. This code was working properly before Active Directory with
NT4WS clients, but is giving strange results now. All the clients are
XP Pro.
The registry values I am changing are:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
DefaultUserName=Administrator
DefaultPassword=*******
DefaultDomainName=<Localcomputername>
AutoAdminLogon=1
DontDisplayLastUserName=0
ForceAutoLogon=1 (probably not required, as I am only autologing in
once)
PROBLEM: However... the code is pretty much randomly not working. In
some cases it auto logs in and goes ahead with the install, and in
others it comes back up to a login prompt as if the auto login
registry keys were not set (or, as I am suspecting, getting blanked
out/reset by something else). The cases in which it autologin's or
not does not seem to be based on which AD container the computer is in
- some in a specific container work, others don't.
There are no shutdown scripts running, and the startup script doesn't
do anything that would effect it.
I am confident that the code is setting the registry parameters
correctly. The code is bulletproof. Anyway, why would it work in
some cases?
Can anyone give me any ideas what would be stopping the autologin
between the code setting the registry values and the computer starting
up again.
I have narrowed down the problem to something outside SMS or
Winbatch... something in XP itself, or AD, etc, etc.
Any guesses for me to follow up on would be appreciated. Any ideas
may help. I am not neccessarily looking for answers... just a
suggestions for things to explore.
Thank you very much!
Cory
SCENARIO: I am using SMS to push a winbatch job which sets the
autoadminlogon information, reboots and proceeds to install some
software. This code was working properly before Active Directory with
NT4WS clients, but is giving strange results now. All the clients are
XP Pro.
The registry values I am changing are:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
DefaultUserName=Administrator
DefaultPassword=*******
DefaultDomainName=<Localcomputername>
AutoAdminLogon=1
DontDisplayLastUserName=0
ForceAutoLogon=1 (probably not required, as I am only autologing in
once)
PROBLEM: However... the code is pretty much randomly not working. In
some cases it auto logs in and goes ahead with the install, and in
others it comes back up to a login prompt as if the auto login
registry keys were not set (or, as I am suspecting, getting blanked
out/reset by something else). The cases in which it autologin's or
not does not seem to be based on which AD container the computer is in
- some in a specific container work, others don't.
There are no shutdown scripts running, and the startup script doesn't
do anything that would effect it.
I am confident that the code is setting the registry parameters
correctly. The code is bulletproof. Anyway, why would it work in
some cases?
Can anyone give me any ideas what would be stopping the autologin
between the code setting the registry values and the computer starting
up again.
I have narrowed down the problem to something outside SMS or
Winbatch... something in XP itself, or AD, etc, etc.
Any guesses for me to follow up on would be appreciated. Any ideas
may help. I am not neccessarily looking for answers... just a
suggestions for things to explore.
Thank you very much!
Cory