Solved

AutoAdminLogon info removed after XP restarts

Posted on 2002-06-25
6
421 Views
Last Modified: 2012-08-14
The first time XP restarts after the unattended install, the AutoAdminLogon=1 value in registry gets set to 0, and DefaultPassword also gets removed.

Under NT 4, after our automated install of NT, we run a script that installs all our common applications.
Under Win XP I'm trying to do the same thing, but here's what happens:
In Unattend.txt, under the [GUIRUNONCE] I call my script (stage.exe) - it launches fine, and since I have 3 steps in it, I have it log off, reboot and call itself again with a parameter of 2 (for step 2) via the runonce key.

Here's the crux of the matter.  Before the script logs off and reboots, I set the AutoAdminLogon to 1 and put the settings in for Administrator to log on.  However, it seems that after XP runs the script called by GuiRunOnce, it sets the AutoAdminLogon back to 0 !!!!!  Thus, to carry on my script, I have to manually log in - this only happens after the first step (From XP's viewpoint, after it runs the script it calls from GuiRunOnce, 'cause it doesn't know about the multiple steps).

Thus my questions - do you know how to remove this 'feature'?  Is there perhaps a 'shutdown' script that is run after the XP setup which is removing these settings?
Any advice would really help

Thanks
0
Comment
Question by:lz7y4l
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 1

Accepted Solution

by:
schristie11 earned 200 total points
ID: 7108867
Have you reviewed the documentation and option for a Sysprep install and how they may relate to your issue here?

Just a suggestion. I'm pretty new at Unattended and deployment-type installs.
0
 

Expert Comment

by:R_OCONNOR
ID: 11231102
I have exactly the same problem but no resolution.
The sysprep option is not viable because I am working with different types of machines with various hardware.
0
 

Author Comment

by:lz7y4l
ID: 11231232
I actually found the solution years ago - here's why it was rebooting...
A new feature with XP's uninstalls is a line in the unattend.txt called     AutoLogonCount.

In our case we set     AutoLogonCount=4, and then after XP's automated install it will set autoadminlogon to 1 in the registry for the next 4 reboots.  What was causing my problem was that this AutoLogonCount was set to 0 or 1 (I can't remember), so after the 1st reboot it would set the Autoadminlogon in the registry to 1.  THus, the solution is to set this number to the number of reboots you require.
0
The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

 

Expert Comment

by:R_OCONNOR
ID: 11231364
I have experimented with the AutoLogonCount and it does work, however...
1) I need to AutoLogon as a Domain User.
2) On the 2nd reboot it needs to continue running a script (obviously the runonce only works once)
3) Both registry changes and copy commands do not seem to work in the runonce batch file but they work fine when the batch file is ran any other time.... strange.
Any ideas?
0
 

Author Comment

by:lz7y4l
ID: 11232194
We call a script from the runonce and that script takes care of the rest...
Eg. Runonce calls  stage.bat - at the end of step 1 in stage.bat, it goes to a subroutine that calls itself again with a parameter of 2 (ie. it puts in the runonce of the registry "stage.bat 2" and it the subroutine sets the autologon.
Next, after the reboot it autologs on, calls Stage.bat and it starts step 2.  When step 2 is complete, the subroutine is called and it sets the autologon again and puts in the runonce "stage.bat 3", etc. until you're done
0
 

Expert Comment

by:R_OCONNOR
ID: 11232686
Thanks for the input.
I have finally resolved this by using cmdlines.txt
I was able to change the registry from within cmdlines.txt and it has worked out well. :-)
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you build your web application in Visual Studio you'll get at least a few binaries, or .DLL, files in your bin folder. However, there is more compiling to be done. Normally this would happen when an ASP.NET resource within the web site is request…
cPanel is a Unix based web hosting control panel that provides a graphical interface and automation tools designed to simplify the process of hosting a web site. cPanel utilizes a 3 tier structure that provides functionality for administrators, rese…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question