Please read original post carefully before bothering...
The local admin password is the same as the one specified in sysprep.inf.
The password has complexity and is not encrypted.
AutoLogonCount is set to 1.
Will now change the AutoLogonCount to 10 or whatever. When desktop image
installers have completed the "first boot script", I'll have the script
delete the AutoLogonCount key and other keys involved in the entire AutoLogon
procedure.
This does not guarantee a fix for the scenario described in the oroginal
post, but I'll test carefully and then post findings here...
Thanks for participating!
"Michael Niehaus [MS]" wrote:
> You should configure Sysprep.inf to tell it to configure this:
>
> [GuiUnattended]
> AdminPassword=local
> AutoLogon="Yes"
> AutoLogonCount=1
>
> If you use an encrypted admin password in Sysprep.inf, Autologon isn't
> possible. In this example, it will only auto-logon once; if you want more
> than that, increase the AutoLogonCount.
>
> How is your Sysprep.inf configured? When running Sysprep, was the local
> admin password blank or the same as what's in Sysprep.inf?
>
> -Michael Niehaus
> Systems Design Engineer
> (E-Mail Removed)
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Bjorn" <(E-Mail Removed)> wrote in message
> news:60652B97-84AA-4BA8-93E1-(E-Mail Removed)...
> >I run sysprep on Windows XP with SP2. I configure sysprep.inf to do the
> > autologon stuff. I also set the registry to do autologon at:
> >>>>"HKLM\SOFTWARE\Microsoft\Windows
> > NT\CurrentVersion\WinLogon\AutoAdminLogon", "1", "REG_SZ"<<< and >>>
> > "HKLM\SOFTWARE\Microsoft\Windows
> > NT\CurrentVersion\WinLogon\DefaultPassword",
> > "XXXX", "REG_SZ"<<<
> > Here's the problem - Sysprep simply deletes these keys...
> > Result: If a user reboots the machine, they'll be asked to authenticate.
> >
> > Background & requirements: I have a boot script forcing a desktop image
> > installer to change the computer name according to internal naming
> > standards
> > and to set a new password for the local admin account.
> > To make this happen in a "somewhat" secure manner, I want to have the
> > machine loop autologon until they have changed computer name and password.
> >
> > Again the problem is: Sysprep deletes autologon keys from registry
> > FYI - I have already tried implementing scripts to re-enter the keys above
> > on the first boot after sysprep. Didn't do it...
> > I've been thinking of implementing a startup script enforcing autologon by
> > using local group policy, but couldn't figure out a scripted way to
> > disable
> > the startup script once the installer has changed the computer name and
> > set a
> > new password...
>
>
>
Similar Threads
