PDQdeploy + AutoIt Problem



  • Shawn Anderson

    AutoIT scripts are becoming more popular as of recent. They do pose some challenges when attempting to run via an remote solution. Are you using the same account to install via PDQ Deploy that you are using when running manually? Will you please email your autoit script to support@adminarsenal.com and we'll see what we can do. In the email to support please provide info on the application that you are running/configuring via your script so that we can try and replicate in our lab.


    Comment actions Permalink
  • Adam Ruth

    Software that is run remotely, like with PDQ Deploy, runs in the background and won't be visible on the screen.  This is a security limitation of Windows.  If the software displays a window and is expecting some user input (such as to click on a button) then the software will appear to hang as it won't be possible for a user to respond.  It's the most common cause of hanging installers with PDQ Deploy.

    The solution therefore is to determine the silent method of installing the software that you are deploying.

    Comment actions Permalink
  • Adam Ruth


    What's most likely happening is that the Divxinstaller is displaying differently when run in the background, so that the script is stuck waiting for a window to appear that never does.

    You can add some tracing lines to the script to see where it's failing, for example:

    ConsoleWrite("Start" & @CRLF) 
    Opt("WinTitleMatchMode", 2)
    ConsoleWrite("DivXInstaller.exe" & @CRLF)
    ConsoleWrite("Sleep" & @CRLF)
    WinWait("Sprachenauswahl", "Wählen Sie Ihre Sprache.") 
    ConsoleWrite("WinWait 1" & @CRLF)

    ... etc ...

    Then capture the output from the script:

    autoit3.exe DivX.au3 > c:\trace.txt

    This will tell you where the script is failing, which should help to pinpoint what change needs to be made.

    Comment actions Permalink

Please sign in to leave a comment.