Systems Management Question

Command line not working in SMS

01/14/2007 4196 views
Hi I'm using SMS2003 and Wise Package Studio 7.0

Here is scenario...
there are MyApp.msi, MyApp.mst, MyApp.wse and MyApp.exe

MyApp.mst is for adding some settings in the MyApp.msi. MyApp.wse is compiled into MyApp.exe. So, it ,means, once I clicked MyApp.exe, it will intalls the MyApp.msi and MyApp.mst.

Inside the MyApp.wse(using WiseScript Editor), here is the command:
Execute %inst%\MyApp.msi TRANSFORMS=MyApp.mst /qb /l*v C:\Logs\MyApp.log (Wait)
Display Message "Extra Information"

If I just double click the MyApp.exe, everything works fine.
However, after I advertised it in the SMS2003 and I installed the MyApp from Run Advertised Programs. The wierd thing is that, it didn't apply the transforms. It only installed the MyApp.msi and and create the MyApp.log file. I noticed SMS2003 downloaded all 3 files; MyApp.msi, MyApp.mst, and MyApp.exe to the target machine(C:\windows\system32\CCM\Cache) correctly. No error message in the event viewer.
But, if I double click the MyApp.exe on the target machine(C:\windows\system32\CCM\Cache), it works fine and the transforms were applied correctly. I'm confuse here...

*fyi, I need to to add a .wse because I need to add msg box with extra information after the apps has finished with installation

Please help me..I'm new to SMS 2003 and WiseScript Editor...
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers


Don't know if it's Monday morning... but it seems a slightly difficult way to perform your task.

You could add a custom action to your .MST file that displays your "Extra Information" from the Execute Deferred section of the MSI script.

That way your are still using the MSI/MST combination. I suspect that for some reason it's not finding the transforms file and therefore not installing as wished.

Check the installation log it creates for mention of the MST file ( Use the SMSTrace utility from the SMS ToolKit, it will break all of the lines up into a readable format and even highlight errors in red - plus it has an error code lookup!)

SMS is a fickle mistress that sometimes just doesn't do what you'd expect.

I've found the best method of adding a package to SMS is to add a "new package from definition", then point it to your .MSI file. This will create various installation methods (per user attended, per machine unattended), modify the command line of the installation type you require to include your .MST and log settings.
This way also creates .MIF files for reporting back on installations.

Hope this in someway helps... it is Monday morning and this post is my first task of the day.
If I decide I'm talking rubbish or have any other brainwaves I'll update this posting.


Answered 01/15/2007 by: dunnpy
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ