How to run a VBScript as a K2000 post-install task?

Oh my god!!!!!!!!!!!!!!! KACE documentation is so frustrating!!!!!!! 

I hate it so much!!!!

All I want to do is to run a VBScript as a post install task, I look in the KB articles and can't find a simple guide on the process.  I see 1 document showing an people in questions talking about it, but nothing that goes through the process (or variety of processes). 

I called support, they said I needed to put cscript in front of my parameter calling the vbs file (post install type is a windows script, no idea if that is correct as there seems to be no documentation).  I uploaded the vbs file and have "cscript file.vbs" (no quotes) in the parameters field.  I synced the change to the local RSA, kicked the deployment off to test and get the error message "Windows cannot find 'csript file.vbs'. Make sure you typed the name correctly, and then try again.

3 Comments   [ + ] Show comments
  • Hello Vivalo,

    It looks like you might have a typ0. you need to have "cscript" the a space then the path and name of your vbs file.

    An example would be: "cscript C:\temp\install.vbs" - jboling 4 years ago
    • I have a space. But there isn't a path to the file, just the file name of the uploaded file.

      Quest Support said it looked fine but it fails as I said.

      Was finally able to speak to another support rep who said I should package in a zip file along with a bat file to call the vb script file in a similar manner to how I do for powershell scripts. I will test and reply back. - Vivalo 4 years ago
  • We do this for joining PCs by attaching the VBS Script to the task, then in the parameter we have cscript join_domain.vbs [domain] [adusername] [aduserpassword]

    However the adusername/aduserpassword is not needed if it is a local only script and does not need access to the domain. - DaveMT 4 years ago
  • I see the same issues with Kace Documentation. It is as simple as can be except there is no how to on what to do. Then you get into the threads like this that explain the exact problem you have and users comment but never explain the final solution. very frustrating support system they have with the ITninja stuff.... - j.catlin@nmscolo.org 3 years ago

Answers (1)

Posted by: cserrins 4 years ago
Red Belt

Sorry you are having issues.  There are several ways a vbs can be run as a post install task.

The easiest is to do a Windows Script postinstall task.  You just upload your vbs file, that is it.  This works great if your script does not require parameters.   The other suggestions you mention should work as an application post install task.  If you do it this way, check out the example join domain windows task that comes on the box.

  • Hi Corey, sorry, just frustrated that I couldn't find this info in any admin guides.

    I will try that method too (seems deceptively simple). - Vivalo 4 years ago
  • Turns out in the end that method isn't working too. The only way I can make it run is to make a batch file that runs "cscript file.vbs" and zip the batch and vbs files together uploading as an application post install task and in the parameter call the batch file. - Vivalo 4 years ago
    • If it isn't a sensitive script file, can you email it to me? My email is in my profile. Thanks. - cserrins 4 years ago

Don't be a Stranger!

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

Sign up! or login


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