Run an Interactive Installation in SCCM with AutoIt and the “Run a Command Line” TS Step.

By | November 8, 2011
Share

By Default, All programs called by an SCCM task Sequence are silent and HIDDEN.  They are not in view, so any non .MSI, old .EXE,  or improperly packaged install packages without fully silent arguments are NOT SUPPORTED without re-packaging.  This process is very time consuming and also troublesome when resources and settings are missed during re-packaging.  The best method I’ve found is to use AutoIt’s “ControlClick” function to click through installation prompts and similate a manual installation of the package exactly how the customer wants.  In SCCM, you MUST run the AutoIt install script as a “Command Line”.  This is due to “Programs” being hidden and therefore out of sight, so AutoIt can not target boxes and buttons.  I’ve used this methodology successfully with the Slysoft VirtualCD Application as a test.  This is the “Run Command Line” line step in my “Task Sequence”.

RunCommandLinStepInSCCMTS

And here is my package contents:

Package Contents

I also add a block of code on the top of my AutoIt scripts to close the Progress UI, which may interfere with the script targeting buttons and boxes.  This UI reappears after the installation is complete.

CloseProgressUIinAutoIt

Link to AutoIt source and images above: https://panaconsulting.egnyte.com/h-s/20111108/c74a6ee76c0243e5

– Brian G

2 thoughts on “Run an Interactive Installation in SCCM with AutoIt and the “Run a Command Line” TS Step.

  1. Vicky

    Hello Brian,
    I have been struggling with trying to create a MDT task sequence wizard UI prompts for user input at the time pre-image installation(data to enter is only available at the time of deployment),I have three .ini files which needs to be used to create UI input wizard from and save the entered data to, once the data is entered it can boot to applying image. Can you please advise with any solution?
    I have a per-captured WIM with hyper-v2016 with a VM on it, i was able to copy directories with .ini files and PS scripts which will inject this updated .ini files (which will be updated by the UI user input) to the VM after OS installation and boot of VM.

    Thank you and I appreciate your help!

    Reply
    1. Brian Gonzalez Post author

      Task Sequence Variables seem like a better fit to store this data, they are retained throughout the entire task sequence. So you can prompt for the values in your wizard to populate the variables and then use them later. https://archive.codeplex.com/?p=mdtwizardstudio simplifies the process of collecting the values. It is fairly easy to work with, but you’ll need to know some basic HTML.

      Reply

Leave a Reply

Your email address will not be published.

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.