Silent install and deployment of Adobe acrobat pro DC NOT WORKING!
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
Answers (2)
Please log in to answer
Posted by:
danflynn
6 years ago
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
Posted by:
anonymous_9363
7 years ago
>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.
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.
Also, you can't just launch AcroPro.msi, as a program. Your program is msiexec.exe. - chucksteel 7 years ago