Not sure why this is failing. I'm installing the KACE Agent as a post install task.

The file is in the correct location.  I can install it from the location marked in the Edit Tasks.xml view cmd in the Task engine.  But K2000 will not install the task automatically.


ANy ideas?

7 Comments   [ - ] Hide Comments


  • Same here, my agent it is not installing as post install. no errors whatsoever. Manual installation of the agent works fine. this only happens to OS X clients. I did re-upload the agent with the cert fixed, no luck.
  • jharrell - Can you post your task?
  • I was having issues with a bunch of my post tasks after my 3.6 upgrade. Talking with support, there are apparently a number of slightly less than documented changes that happened. Here's the response I got:

    PO tasks have changed 3.6. Here is something on this subject -
    Although not specified (we are working on getting the documentation expanded), this affects several other things.
    VBS scripts now need at the begining of the cmd - cscript.
    Dos commands would need this - cmd.exe /c followed_by_the_command.

    In my instances, my application tasks were failing with file not found errors, I needed to add the cmd.exe /c, or (my long winded solution) package the installer and a batch file with install commands inside of a zip, upload that to the K2 and call the batch file as the application task.
  • msiexec.exe /qn /i install_flash_player_12_active_x.msi

    Its a Flash Player install as a Windows Application with the associated .msi listed in the command line above.

    Should it be cmd.exe msiexec.exe............ ?
    • I have some flash installers in my post tasks as well, and those actually worked fine after 3.6, so I went in and took a look at them. I'm launching mine with:

      msiexec /i install_flash_player_12_plugin.msi /qn

      maybe re-arrange your syntax a bit and see if that helps?
  • That did help. the /i and /qn need to be right up front: msiexec.exe /qn /i install.....
  • Also i'm having some trouble with this one:

    C:\WINDOWS\system32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /inpkey:M
    • without having a task to reference, I would maybe drop the C:\windows\system32\ and the file extension, leaving your task with

      cscript "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /inpkey:M

      I've noticed that alot of my issues come from treating the 3.6 task engine like it's the old "dumb" engine. Try that out and let the engine sort out the file locations for you.
  • Perfect. That did it. Thanks
Please log in to comment

Answer this question or Comment on this question for clarity



One solution I heard works is to recreated the Application task as a Windows Script task. Another solution can be found at the following link:


Answered 02/17/2014 by: stevech
Purple Belt

Please log in to comment