Hey guys, I've been running the script I found on the support site for years that would auto logon after imaging, run a WSName, reboot and auto logon again to join my domain.  I had set the auto logon in sysprep.  Now on 3.6 my guys need to logon to the computer and it will kick off the script, then reboot and they have to log back on to finish the job.

Is there a better way to accomplish this in 3.6?  The new task engine looks like I may be able to do it a better way, if someone out there has a little direction I would greatly appreciate it!

1 Comment   [ + ] Show Comment

Comments

  • When we updated to 3.6 there was an extra reboot in the process and it would require a log-in before the post tasks kicked off. Adding 1 more auto logon to the unattend.xml file in all of our images resolved the problem for us. Shouldn't need to turn it off if you find the correct # of log-ins for your images/environment.
Please log in to comment

Answers

1

This might be related: http://www.itninja.com/question/windows-8-1-and-k2000-scripted-install-cannot-rename-system-with-service-tag

Sounds like this might be a common issue.

Answered 01/29/2014 by: nheyne
Red Belt

  • I checked that one out, mine is working but I have to login 2x manually. We have 6000+ machines and image a lot, I want the guys in the field to start an image and basically walk away knowing it will be done in one shot (most the time). I'm thinking in the new task engine I need to do a task for each process and have it reboot by clicking the reboot check instead of my bat w/ the old style scripts.
    • I don't have any experience with the new task engine, but you should be able to have reboot tasks.
      • I ended up resyspreping a base image with 9 auto logins then turning it off with the last task - good enough until I can figure out something later.
Please log in to comment
Answer this question or Comment on this question for clarity