KACE Product Support

Our K1100 is running v5.2.38773 and we're pushing out v5.1.38724 of the Agent.

Using the advice from above I tried using $KACE_DEPENDENCY_DIR in the Configure Manually part of the Run Command. I found that this didn't seem to run the MSI.
The KBOT_LOG on the machine looks like it did everything correctly, however nothing actually installs. There are no errors reported in the Windows Event Log either.

I have tried: msiexec.exe /i "$(KACE_DEPENDENCY_DIR)\Smart Notebook.msi" /qn
and also: msiexec.exe /i "$(KACE_DEPENDENCY_DIR)\Smart Notebook.msi" /qn TRANSFORMS="$(KACE_DEPENDENCY_DIR)\smartnotebook10_7admin.mst"

Which is taken direct from the SMART Notebook deployment instructions.

To install SMART Notebook software
Run the following command if you created an MST file to customize the installation package:
msiexec /i "[Path]\SMART Notebook.msi" TRANSFORMS="[MST File]"
[Parameter]


If I use: msiexec.exe /i "Smart Notebook.msi" /qn /T:"smartnotebook10_7admin.mst"

It will install if I change it to: msiexec.exe /i "Smart Notebook.msi" /qn /T:"smartnotebook10_7admin.mst"
BUT my transform isn't applied.


I don't think there is anything wrong with our setup as such because so far I have always found a way to install what I need.
It's more trying to understand how it "should" work so I can follow the same process each time.

does this work:
msiexec.exe /i "Smart Notebook.msi" /qn TRANSFORMS="smartnotebook10_7admin.mst"
either from KBOX or regular command line? I'd also turn on logging and see if the log indicates a problem with the MST.

Yes, that works.

Embarrsing confession time.....I really need to check my typing.

I could have sworn the MST was called "smartnotebook10_7.mst"....it was actually "smartnotebook10-7.mst".

I'm an idiot :P

Arcolite,

Just remember, they don't pay us to spell or do math!

If they did most of us wouldn't have jobs, i know i wouldn't.

Would it be possible to have to send across or post a screenshot, since your post references msi files as well as exe files...

I have seen this before on older versions of the agent.

Have you tried upgrading to server version 5.2 and the latest client?

You could always try and add

$(KACE_DEPENDENCY_DIR)\

In front of your msi path. I use this for Scripted installs when I need to call a file and delete it.

Also remember you dont need to encase the second set of quotes. The run paramater for you (I believe) would be:
msiexec /i "$(KACE_DEPENDENCY_DIR)\Your MSI Name.msi" /qn
and you would set it to 'Configure Manually'

Let us know how you go.

Cheers,
Col

Unless they added some new functionality, i don't think $(kace_dependecy_dir) will work for a managed install. :)

Its kinda a pain, but i would stick with using a bat in the mean time and open up a ticket with support long term.

I Second this:
ORIGINAL: dchristian

I have seen this before on older versions of the agent.

Have you tried upgrading to server version 5.2 and the latest client?