I'm trying to configure a Windows 2000 Pro deployment image (deployed via a
Windows 2003 RIS server) so that it will autologon with an account OTHER
than the administrator account.

I created a batch file that modifies the relevant registry entries, and put
it in the GuiRunOnce section of the riprep.sif file.
It works, but then it breaks.

After deployment, the system boots up and auto logs on with the
administrator account, then runs the batch file and modifies the registry
(verified with regedit). However, after I reboot (in order to log on with
the non-admin account), it appears that Windows removes the DefaultPassword
entry completely, and sets AutoAdminLogon back to zero, which effectively
removes the modifications made by the batch file. This is probably part of
the image deployment cleanup phase, but how do I work around it?

Thanks,
Mike

Setting Passwords
http://www.microsoft.com/resources/d...c_cai_rdii.asp

Change administrator account login to another user
http://www.msfn.org/board/index.php?act=ST&f=70&t=30375

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/secu...t/default.aspx

----------------------------------------------------------------------------

"Mike Koch" wrote:

| I'm trying to configure a Windows 2000 Pro deployment image (deployed via a
| Windows 2003 RIS server) so that it will autologon with an account OTHER
| than the administrator account.
|
| I created a batch file that modifies the relevant registry entries, and put
| it in the GuiRunOnce section of the riprep.sif file.
| It works, but then it breaks.
|
| After deployment, the system boots up and auto logs on with the
| administrator account, then runs the batch file and modifies the registry
| (verified with regedit). However, after I reboot (in order to log on with
| the non-admin account), it appears that Windows removes the DefaultPassword
| entry completely, and sets AutoAdminLogon back to zero, which effectively
| removes the modifications made by the batch file. This is probably part of
| the image deployment cleanup phase, but how do I work around it?
|
| Thanks,
| Mike