Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Autologon is still on after Sysprep (MDT 2012 Update 1)

Unanswered Autologon is still on after Sysprep (MDT 2012 Update 1)

  • Sunday, September 23, 2012 10:54 PM
     
     
    Sign In to Vote
    0

    I have a standard task sequence for deploying Windows 7 SP1. I select "Sysprep this computer" in the Deployment Wizard and the task sequence finishes successfully. When I reboot such syspreped installation (same as if I manually captured it and then applied it), everything works fine but it is automatically loging on as an Administrator and giving an error launching C:\LTIBootstrap.vbs (which is understandable when there is an unattended.xml file in the %WINDIR%\Panther folder that has Autologon configured). The question is why?

    I understand that in most "legitimate" deployment scenarios (WDS, MDT, SCCM, etc.) another unattended.xml can/will be supplied and applied during deployment, making this a non-issue, but if one's intention is to have an image that could be deployed by simply applying it to the hard drive, than the "Sysprep this computer" option doesn't really do the job. And excluding the \Windows\Panther from capture (like MDT does) is also not a very good solution in this scenario because with it all the other settings (that may be important, like CopyProfile) in unattended.xml are lost.

    I could accept that MDT wasn't meant to produce an installation that could be captured and then deployed by simply applying it to a hard drive, if I didn't realize that the "Capture an image of this reference computer" option produces exactly that. When the full capture is run, what remains on the hard drive after capture is a syspreped installation and an unattended.xml file without Autologon and MDT entries (perfect for "dumb" capturing and deployment).

    So the question is: Why do these 2 different options ("Sysprep only" and "Capture") produce a different end result in terms of unattended.xml file that remains on the drive and if "Sysprep this computer" is meant to leave the machine ready for manual capturing (into WIM or VHD), therefore ready for deployment and delivery to end user, shouldn't it behave the same as "Capture" option ie. have Autologon and MDT entries removed from unattend.xml?


    • Edited by pdavidyu Sunday, September 23, 2012 10:56 PM
    •  
     

All Replies

  • Sunday, September 23, 2012 11:28 PM
     
     
    Sign In to Vote
    0

    Hi there,

    I agree that C:\LTIBootstrap.vbs error is an annoyance. I get it when I use the Sysprep this computer option also. I set the FinishAction option in my customsettings.ini and it does not autologon. 

    FinishAction=SHUTDOWN

    I suggest you try the above or the REBOOT option and see if that fixes it for you.

    Blog: http://scriptimus.wordpress.com

     
  • Thursday, January 10, 2013 4:51 PM
     
     
    Sign In to Vote
    0

    Hi,

    i am facing this problem by installing a VM Windows 7 x64 . Everthing works great boot / install OS but then i got this ugly message : C:\LTIBootstrap.vbs...

    Why does it appear and how can i fix it ? if i understand your advice correct i should shutdown the machine (customsettings.ini FinishAction=SHUTDOWN) but if i want to start some scripts ?