You can make your lief an awful lot easier by pointing to the MST file as one of the "additional files" to be copied down to the client.
--> Main Package File == MyPrettyMSI.MSI
--> Additional File 1 == SomeCAB.CAB
--> Additional File 2 == MyPrettyMST.MST
--> Additional File 3 == Subdirectory_Name\SomeDataFile.dat
This way, you will have the MST file down on the client, and can simply add the command-line "TRANSORMS=MYPRETTYMST.MST" (since it'll be executed in THAT directory, and the MST will be in the same place). This way you don't need to worry about accessing it.
The following two documents would hopefully help you along the way, since they deal with BKM's for Office .
Best Known Method for Deploying Office 2007 with LDMS:
Best Known Methods for Installing Microsoft Office 2003:
Using the "additional files" option correctly, you can make your life a whole lot easier, because all the files you could possibly want (whether it's a VB-script or anything really) will be available locally as well .
Hope this clarifies things for you .
- Paul Hoffmann
LANDesk EMEA Technical Lead
Paul raises some good points. Some additional comments - TRANSFORMS= can not be a http path. Try just specifying the transform name without any path, or specify a unc path. One issue with using additional files, is that some MSIs use the cache path for the installsource that gets written as the sdmcache location. Once the client purges the cache this may cause issues. If you use additional files always check the hKLM\software\microsoft\windows\currentversion\uninstall\your pid\install source.
I'm not sure about awesome but we try hard - LOL. So to help us old guys out just close the thread if you are satisified. It helps us to only search through open threads.
Consider it done! Thanks again.