For managed installs, what's your preferred method, VBS or batch file?
I love me some VBS but for whatever reason, kace seems to play nicer with batch files for managed installs. Which ones do you run for managed installs?
Answers (4)
I prefer batch file when the task at hand is simple and could be easily accomplished. And vbs when something I find it difficult to get done in batch file. But I enjoy writing powershell code these days than vbs.
Comments:
-
I am teaching myself powershell slowly but surely. Can you do power shell through k1000 scripting? - areiner 10 years ago
Everything which fits best.
I prefer batch files, but if needed then I use scripts (vbs only if really needed)
Comments:
-
I used to do pure vbs but i was having some issues, i have since turned to batch files, they are fun and simple. - areiner 10 years ago
-
I prefer batch scripts for managed installs and it is easy to do customizations with batch files. - Visalakshi 10 years ago
SCCM is far more manageable, works with almost any software using it directly with MSI's or using your own batch files and VBS's. You can create packages to install lots of programs, or link packages to install one after another, even integrate WSUS updates (which is easier/quicker this way imo). You can set conditions eg. install if particular operating systems are selected.
I know it's not free, but on a network of 100+ PCS it does the job. Before you ask, I do not work for Micro$oft :)
I use both, what ever accomplishes the task with the least amount of work. Remember the old adage KISS
Comments:
-
that was one of my MIS professors main saying..just KISS it. He couldn't be more right. - areiner 10 years ago
-
I have worked on computers/electronics since 1979 when I went into the USAF and still believe in that rule - SMal.tmcc 10 years ago
-
A cool scripting method for MI's is to create a kbot and then call it from the MI command line.
For Example: I deploy cctk.exe and the HAPI drivers to my Dell PCs. The installer from Dell.com installs the GUI as well as the command tool, and I don't need the GUI.
I created Software Item "Dell CCTK 2.1.1" with Custom Inventory rule FileVersionEquals(c:\program files\dell\cctk\cctk.exe, 2.1.1.0) and no associated file.
I created a offline kbot (ID 341) with the following:
CCTK.zip as a dependency.
Verification = Unzip CCTK.zip to $(KACE_DEPENDENCY_DIR)
On Success = Batch File to install HAPI driver and copy cctk.exe to %programfiles%\Dell\CCTK
Don't run on a schedule.
I created MI for Dell CCTK 2.1.1 with the following:
Check box: Also show software without an Associated File.
Installation Command: "$(KACE_APP_DIR)\runkbot.exe 341 0"
Check box: Run Command Only (do not download file):
This is a simple example, but with this method you can create a sequence of vbs, batch and the built-in kbot features. - jessefrase 10 years ago
