OK, let me start off by saying i would appreciate any help anyone could give me, because I have no clue really what i am doing. We got KBOX about 2 months ago and my boss wants us to really start using it for everything. So i am trying to install 2 .msi files and 2 .msp files. So i wrote a batch file:

Msiexec /I "ENTRUST_90.msi" /norestart
Msiexec /I "entrust_90patch.mst" /norestart
Msiexec /i "Entrust_80.msi" /norestart
Msiexec /I "entrust_80patch.mst" /norestart

It works if i run it from my local computer, however i am unable to load it into KBOX and get it to work. What i did was Zip the 4 files along with the batch and upload those into a KBOX script. I told KBOX to unzip the files in to the KBOX dependency directory (which it does) and run the batch file (which it doesnt)

Any clue on what i could do?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


It works if i run it from my local computerI'd like to see that work, since you have errors in those command lines.

MST = a transform file
MSP = a patch file

Either way, you must specify the correct command line switches when using either. For example, it's either:

Msiexec /I "ENTRUST_90.msi" /norestart
Msiexec /I "ENTRUST_90.msi" TRANSFORMS="entrust_90patch.mst" /norestart
Msiexec /I "Entrust_80.msi" /norestart
Msiexec /I "ENTRUST_80.msi" TRANSFORMS="entrust_80patch.mst" /norestart

or it's:

Msiexec /I "ENTRUST_90.msi" /norestart
Msiexec /I "ENTRUST_90.msi" /p "entrust_90patch.msp" /norestart
Msiexec /I "Entrust_80.msi" /norestart
Msiexec /I "ENTRUST_80.msi" /p "entrust_80patch.msp" /norestart

If the latter - i.e. you're dealing with patch files, not transforms - I would strongly recommend against patching individual clients. Rather, create an Administrative Installation point on a globally-accessible network share, using the '/A' switch. Once you've done that, then patch the AIP. When that's done, use the patched MSI which will be in the root of the AIP to install to your client machines.
Answered 05/26/2010 by: VBScab
Red Belt

Please log in to comment