How to deploy applications by Scripting with K1000
Dear All,
Please advise me how to deploy applications by use Scripting with Software Packet on Distribution? I mean I already software packet for install on Distribution and I can deploy by use Distribution however I think it will good to be if I can use Scripting to deploy applications to client machine because it have status to show me it success or not. So please advise me how to do thanks.
Answers (3)
Hi manpang, a good start would be to check out this article:
http://www.kace.com/support/resources/kb/article/How-to-call-a-Visual-Basic-script
You could attach a MSInstaller file instead of the *.vbs file as a dependency + you change the command line parameters to i.e "msiexec.exe /qn file.msi /i" (no quotes) instead of the cscript.exe line.
The MSInstaller should install fine. From here it could be any other setup.
Please let us know your experience doing it this way.
Comments:
-
I like how this sounds good in theory and should work, but literally once a day I'm finding programs where this doesn't work. Right now I'm working with Adobe Air and it's orphan "sentinel" file that does nothing; I'm thinking about just removing it from every PC. - gcarpenter 11 years ago
-
This is why I recommend using Managed Installs (Distribution) for installing/removing applications. I thought the same thing as manpang about Scripts giving the ability to track things (and schedule!), but in practice they just weren't consistent enough. I've found MIs to be very consistent and easy to track.
John - jverbosk 11 years ago-
Yeah, that's all I've been using recently. I use scripts for stuff like registry updating, but as far as pushing out applications, MIs are the boss. - gcarpenter 11 years ago
-
Hi jverbosk,
As your recommend about using Managed Installs to insatll applications, however what should I do for track when I deploy applications to 50clients? - manpang 11 years ago
This is the way we do it.
I make the installer package. Attached it to a software inventory item (or create a new one if there is not one specifically for it). Then I go add a new online script, set the on success field to install a software package, then i select the software inventory I attached my package to. The install arguments you would put in the msi or batch file command. Then you can put your pre and post install messages.
The Scripting module can give you some extra flexibility for complex programs. You would essentially upload your Installer files as Dependencies. Then you can use the Launch A Command function and run the installers with the needed command lines.
I use this fairly often for more specifically targeted installations.
