Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
TS not doing auto admin login

Answered TS not doing auto admin login

  • Tuesday, September 11, 2012 1:49 AM
     
     
    Sign In to Vote
    0

    Hoping someone can help.  I have a task sequence that for some reason is not doing the usual auto admin login to run LTIBootstrap.vbs after deploying the image.  I have verified the unattend.xml is configured to enable autoadminlogon and the command to run LTIBootstrap.vbs is there.  I have recreated the TS, but I'm not sure where to go from here.

     

All Replies

  • Tuesday, September 11, 2012 8:25 AM
     
     
    Sign In to Vote
    0

    I have a task sequence 

    What kind of Task Sequence, please?

    is not doing the usual auto admin login

    What exactly is it doing? Where does it stop?


    Blog: http://scriptimus.wordpress.com

     
  • Tuesday, September 11, 2012 1:09 PM
     
     
    Sign In to Vote
    0

    Sorry, it's a standard client ts, after imaging it does the postinstall group, reboots and ends up sitting at the login screen where I cannot login as any user, even local administrator.  Normally it would login, run some custom post install vbs scripts, name and add itself to the domain.

    Here's a screenshot of the ts, the Imgscripts-InsertPause step I added so I could tell if it started the State Restore group, it's just a vbs with a msgbox:

     
  • Tuesday, September 11, 2012 2:23 PM
     
     
    Sign In to Vote
    0

    check and make sure you have the autologon set in the unattend.xml for this task sequence

    Phase 7 oobeSystem

    Microsoft-Windows-shell-Setup\AutoLogon

     
  • Tuesday, September 11, 2012 5:58 PM
     
     
    Sign In to Vote
    0

    Yes, autoadmin login is enabled in unattend.xml.  It looks like the issue is with my image because I replaced the image being deployed in the ts with another image and it deploys and the ts runs fine.  I am re-uploading now.

    OK I have reuploaded my image, the issue still exists and it's baffling me.  Here's the sysprep and capture ts I'm using to capture:

    I must be missing something real simple here somewhere...  Maybe there's a setting somewhere that I've inadvertently changed...


    To be clear, I can see sysprep is being applied on the master image, then it reboots and uploads.  When I deploy this image to a second machine it ends up at the login screen where I cannot login as any user.  The State Restore group in the standard client ts used to deploy the image is not running, but I know the ts is not the issue because if I select another (older) image to be deployed with the ts it works fine.
    • Edited by J. Wall Tuesday, September 11, 2012 8:49 PM
    • Edited by J. Wall Tuesday, September 11, 2012 9:07 PM
    • Edited by J. Wall Wednesday, September 12, 2012 12:17 AM
    •  
     
  • Wednesday, September 12, 2012 9:16 PM
     
     Answered
    Sign In to Vote
    0

    I am not sure why, but capturing the image (which had already been configured exactly the same way) using the same capture sequence seems to have worked.  When I deploy the image to the second client sysprep runs as I'd expect.

    Unless someone has any knowledge as to what may have caused this, I'll consider this issue resolved.

    • Marked As Answer by J. Wall Monday, September 24, 2012 6:40 PM
    •