We recently upgraded to v3.6.  I did not realize the impact this upgrade would have to our Post Install Tasks.  I have 4 Images (System Deployments) created using WAIK, SYSPREP, etc.  (Windows 7 SP1).  Before the upgrade all our post install tasks would run/install, etc.

Now the image is stopping at the "Disable UAC" task (which I guess is new) - the PC will reboot, and then sit at the Windows Login Page.  We have to manually login as Administrator - at which point we see the Post Install Tasks take off again - until the next reboot (we 3 happening now, where we had none before).

So - is there a way to get the Admin Account to login automatically?  I guess I can add it as a post install task.  I was hoping there would be a built in one that came with the 3.6 update - but so far no joy.

Any help would be appreciated. 

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0

you need to add autologin to your answer file.  make the count 3 also.

 <AutoLogon>
                <Password>
                    <Value>VwBpAG4AZABvAHcAcwA3ACEAUABhAHMAcwB3AG8AcgBkAA==</Value>
                    <PlainText>false</PlainText>
                </Password>
                <Enabled>true</Enabled>
                <LogonCount>3</LogonCount>
                <Username>installer</Username>
            </AutoLogon>

Answered 05/23/2014 by: SMal.tmcc
Red Belt

  • I also add auto login to my first post task
    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoAdminLogon /d 1 /f
    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoLogonCount /t REG_DWORD /d 3 /f
    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultUserName /d Installer /f
    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultPassWord /d password /f
    start /wait reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultDomainName /f
    • Ok. So if I understand correctly - I copy all of the commands above into a Post Install task (modified for my environment of course). If I add this as my first item, it should take care of everything?
      • this will take care of the reboots that occur during the post phase after the disable UAC task. the reboot that occurs at the disable uac point will not be included since this task would not have run yet.
      • Ok. So another question.

        On this line -> start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultUserName /d Installer /f - is "installer" the user account name (ie. is this what I would change to match the account we use?).

        If so then I would guess -> start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultPassWord /d password /f - I replace "password" with our password.
      • that is a local user, that is why you see the reg delete to remove the domain. and yes put the real passsword there
      • Ok. Is it a local user named "installer"? (I should have been more clear). We use the local Administrator account. Just want to make sure.
      • yea you would want what I use on the admin images

        start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoAdminLogon /d 1 /f
        start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoLogonCount /t REG_DWORD /d 3 /f
        start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultUserName /d Administrator /f
        start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultPassWord /d X0x0x0x! /f
        start /wait reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultDomainName /f
  • Which action would I select to create this post install task? I'm assuming that I open Notepad, copy the commands to it, save the file and attach it within the task....sorry, still a newbie here.
    • I created a post install task - called it auto login. I have it as my first post install task.

      Go to Library - view all Post Install Tasks. Create New - I selected Batch File - copied and pasted the above in (modified to my envionment). Added it to a deployment and tested.
      • Thanks! I'll try this.
      • perfect :)
    • If you need to, you can modify the unattend.xml with a vbs file. read answer on this link
      http://www.itninja.com/question/number-of-autologins-required-has-changed-from-1-to-3-since-3-6-upgrade
      • Thanks again, SMal.tmcc. You've really got some great ideas!
  • So I added this to my Sysprep, and created a new image. The PC still does not login on the initial KBOX restart (after it has done everything, but before the post install tasks are run).

    However the other post install task suggestion - does work. I just need to figure out the 1st one, so it can get to the Post install task and run seamlessly.
Please log in to comment
0

So that means I have to rebuild my image?  I am not using an Answer file (other than the one used during the original Sysprep).

Answered 05/23/2014 by: hutcha4113
Second Degree Blue Belt

  • If you do not want to rebuild your image. You can deploy the image but do not reboot. Then go to c:\windows\panther and get the unattend.xml file and put that on a usb drive. Modify that file to add the new lines for autologon and save it. Create a new mid level task that copies that file back to your images right after it casts, before it reboots.
    • I should be able to pull that file out of the image by using the K2000 File Browser. Modify the XML - and then copy it back to all images.
      • yea, I had 52 old images as wims stored externally so editing was not an option for me
      • Ok. I have the images in the KBOX. I have used the file browser before to replace some files. So will give that try.
  • If you use Kimages you can browse your image and update your unattend.xml file in c:\windows\panther to include your autologons and save the changes.
Please log in to comment
Answer this question or Comment on this question for clarity

Share