Managed Install - Command Line

I've been trying to execute a cmd file in a Managed Install - just won't run.
Have a command called "StartInstall-Attended.cmd" from a vendor. Set the MI Installation Command to "Configure Manually"
entered just "StartInstall-Attended.cmd" does not execute. Tried a full command line to the file in the Kace directory, nothing executes the cmd.
I remote to the machine, I can see the bits are downloading, I have a PreInstall message that runs, so I know the files are ther and the MI is stating, but it just won't execute the cmd
Any recommendations?

Answers

This is a bit of a kludge but try a batch file with the fallowing code.START /WAIT "TEST" "%~DP0StartInstall-Attended.cmd"
EXITIt should pop StartInstall-Attended.cmd into a visible window so you can see what's going on.

Your problem could be related to something in the .cmd file itself, or you could have issues associated with user rights. Keep in mind that everything is run as the local SYSTEM account by the KBOX agent.

This is unrelated to my previous comments, but I'm just curious... have you tried changing the extension from .cmd to .bat?

Im trying to install two different McAfee packages but both are same version with different configuration, one frame pkg for Region1 and another for Region 2, how i can do this MI ?

when I create new managed install im able to associate only one file at a time, any idea how can i perform this ? as i need to perform the two installation with different configuration at a time..I have zipped both the frame pkgs, and trying to call as below

I'd recommend using a KScript instead. If you attempt to split this up with 2 MIs then they'll run completely independent of one another, and you'll have to control which machines perform which install by using Smart Labels. With a KScript, you can attach both dependencies to one script and control the checks/installs, etc with that single script.

If you prefer the MI method, you can still do that. As I mentioned before, the 2 MIs will run independent of one another so you'll have to do all of your targeting by using Smart Labels. The accuracy of your Smart Labels will determine the accuracy of your deployment.

As for the specific command line parameters for FramePkg.exe, I can't remember off the top of my head. McAfee should be able to confirm this for you.

Managed Installs are for software items that will show up in the Installed Programs of a computer inventory record. If the software hasn't been inventoried yet then a manual install and check-in is required first to have the KBOX know about the software. Then you can associate the install script to the software record. What software is associated with this managed install?

It sounds more like you want to use the Scripting section to set up the batch file and then it can be associated with a label to apply to desired computers.

Rich, managed installs will deploy regardless of the inventory. The problem with managed installs is they can't confirm that they've been installed unless the inventory item is configured properly. I would agree that the scripting module is better for this type of deployment.

Mlathrop, you may want to try using a KScript with the .cmd file as a dependency. The only reason you should use a managed install instead is if you want to inventory based on something the .cmd file is doing (i.e. a custom inventory item). If the program being installed is in Add/Remove Programs, then the KBOX will still inventory it if you deploy using a KScript.

To create a Managed Install requires a software item be picked from the pull-down menu. It can be one with an associated file already or by checking the box to "Also show software without an Associated File" you can pick from any of the software titles in the inventory. That's what I meant that it has to be in the software inventory first.

Rich, you are correct. I was just pointing out that the software inventory item doesn't have to be configured properly for an MI to deploy - you simply have to choose one (whether it has an associated file or not).

I tried BAT and that does not execute either from an MI. I have pinged KACE on this.
FYI, RichB, the managed install uses a custom inventory rule to validate the app is installed. Due to version issues with most software, which can change with patches or updates, I've found that custom inventory rules are almost always neccessary and more reliable for managed install validation. Scripting a bat file it would be my second choice.