Software Deployment Question

Correct "Additional Parameters" for Snagit 12

06/09/2015 3641 views
I'm attempting my first Kace Software Deployment since we've installed the K1000.  Generally I would just create .bat/cmd files and run them at logon for these software installs and updates.  So while I have a very good handle on scripting flags, I'm not entirely sure what Kace is looking for from me.  I've already added Snagit(.msi) 12 to our Software Assets, and am now trying to configure the Distribution "package".  Do I simply add "/I /quiet /norestart" to additional parameters?  I'm not sure what kind of formatting it's looking for.  I also need to add the license key into it... 

Side note: obviously I could use TechSmith's Deployment Tool or a simple .bat, but if I don't start forcing myself to use this for installations I'm never going to.
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author


Use the tool for SnagIt as it gives you a lot more choices for install and more importantly uninstall. eg. when uninstall it makes it true silent and not prompt for do you want to keep the screen caps or delete them...

Answered 06/09/2015 by: Rob_Cliffeild
Senior White Belt

  • This is what I ended up doing, but Ben pointing out that little blue ? was helpful in general, it should get me somewhere in the future.

    I tried sticking the whole line that the Distribution Tool(Snagit) created in the Override Default Installation, but I'm imagining that Kace is having issues seeing the network location where the files are saved. Just ran out of time to deal with it. To the login scripts it went.

    Anywho...next time I guess.

All Answers

Probably the easiest way to answer your question is just to show you where Kace is putting the contents of "Additional Parameters". If you click on the blue "?" you actually can see exactly what command Kace will be using to install the program. You can also see that, in this situation the "/qn /i" command is being inserted before the name of the program but after the "msiexec.exe". That necessitates placing the /i at the end of the command. Hopefully this helps!

Answered 06/09/2015 by: Ben M
9th Degree Black Belt

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