/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Silent install and deployment of Adobe acrobat pro DC NOT WORKING!

03/07/2017 4983 views

Hi guys.

I am having trouble deploying "Adobe acrobat pro DC" from the k1000 via a script.

Created the MST file with the Configuration Wizard. As you can see the "Acropro.mst" below...

Zipped up the Package and uploaded as a dependency....

Then ran "launch a program" see below.

Not working...

What am I doing wrong guys ??




1 Comment   [ + ] Show comment

Comments

  • When you created the zip file did you select all of the files in the folder and compress them, or did you right click on the folder containing them? If you right clicked on the folder then that structure is part of your zip file and your MSI will be inside of that folder.

    Also, you can't just launch AcroPro.msi, as a program. Your program is msiexec.exe.

All Answers

0
Looks you you made a MST file using "Acrobat Customization Wizard DC".  When creating that make sure you set the "Run Installation" to "Silently (no interface)" under the "Installation Options" section as well as "Suppress reboot".  Then put that file in the folder and modify the setup.ini file add to the Line that says "CmdLine=TRANSFORMS=" the name of your .MST to it. (E.G. "CmdLine=TRANSFORMS=acropro.mst"). Then zip up the folder (make sure it is just the contents in the zip and not the folder).

For you Kace commands you would have the following:
Directory: $(KACE_DEPENDENCY_DIR)
File: setup.exe
Answered 08/10/2017 by: danflynn
Orange Belt

-1
>Also, you can't just launch AcroPro.msi, as a program. Your program is msiexec.exe.
To be blunt, I know NOTHING about Kace (I'm a dinosaur from when this was AppDeploy.com, not a Dell product forum)  but I can tell immediately that you have that set up wrongly. To me, it's screamingly obvious that the 'File' text-box is where yo specify the program you want to run (and doesn't Kace have an option to prepend msiexec.exe, anyway?) and the 'Parameters' is where the command line arguments go.

Also, you should always add verbose logging to MSI installs or you'll never know why an installation failed.
Answered 03/08/2017 by: VBScab
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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