Software Deployment Question

Managed installs of Autodesk viewers - Finish prompt shows before install completed

06/21/2018 525 views

We are installing the various viewers from Autodesk:

  • DWG TrueView
  • Inventor View
  • Design Review

We want to silently install the software and use the prompting feature during the managed install script, but the Completion prompt shows long before the Autodesk install actually completes.  When most setup programs are run from the command prompt you can see the command line does not return to the prompt until the install completes, however Autodesk product setups immediately return to the command prompt as though they were completed even though they are spooling off processes for the install.

For example, if you silently install DWG Trueview with the silent switches:

setup.exe /S /Q /I setup.ini
or even
start /wait setup.exe /S /Q /I setup.ini

Setup will spool off a few msiexec.exe processes and Kace will think that the command was run successfully almost immediately and then pop up the Completed message to the end user.

Does anyone know how to set Autodesk setup to wait for completion before continuing?

0 Comments   [ + ] Show comments


  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

All Answers

Either use the MSI natively, or add the '/W' argument to SETUP.EXE.
Answered 06/25/2018 by: VBScab
Red Belt

  • The /W does not work. It still spawns off the different processes.
Instead of a managed install, you could create a script with custom notifications. Breaking the steps into "tasks" may give you what you're looking for. If nothing else, you can make the script wait a few minutes before displaying a complete message to allow the install time to finish.
Answered 06/27/2018 by: JasonEgg
Red Belt

  • Looks like we have to go this route. We found the KSLEEP,EXE and have been using that to put in a 10 minute pause to be sure the application has enough time to install. It only takes about 2-3, but just want to be sure we do not reboot early.

    Even though it is working fine, it does add about 20 minutes to a deployment for al the unnecessary waiting.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ