KACE Product Support

Is it an MI or a script? MIs run as SYSTEM account. Scripts run as SYSTEM unless you specify otherwise.

You can test running it as SYSTEM outside the agent by launching a command prompt with psexec then run your batch file from that:
c:\pstools\psexec.exe -i -s "%windir%\system32\cmd.exe"

http://www.kace.com/support/kb/index.php?action=artikel&cat=5&id=731&artlang=en

1. the logs are in C:\program data\dell\kace
If you turn on debugging that may help. Simply sort the logs by time. Likely good info in the kdeploy or klaunch logs but any might yield the cause

Are you certain that it is not getting installed? Sometimes when a managed install is not mapped to the write software item (e.g. if you manually created the software item) it will not detect it is installed and keep trying. Make sure that you are looking at machine for evidence of it installing and not just based on the MI attempts.

Also the agent will try to install it as SYSTEM user and it MUST be quiet.

This also might help: http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=821&artlang=en

What version of the agent are you using?

Hey,


I think you need to look at that the smmp log file for that info. By chance did you zip the folder, because if you don't leave the exe or msi at the root of the zip, kace won't install it.

Cheers,

Mike

i just zipped the files so they are all in root. If i run the batch from the folder it works fine. So I'm just sorta confused what is happening.

the kace agent is Agent Version: 5.3.47657

The links are exactly what I needed. It seems to be a windows 7 problem it works when its silent if I run the batch but not when kace runs the batch file. Also the installer works fine on xp machines even through kace. So its just something with kace and windows 7 64 bit.

Is it putting the program in the programs files (x86) directory? It probably a problem where kace expects it to be in the program files folder and it ends up in the programs files (x86) directory. I think you'll need to do a custom inventory rule for that software package just to get it for 64bit version.

Guys thanks for all the great feedback I'm going to dig through all this and I'll post my results back later this evening either way.