I'm preparing an app called Reflection 2008 for a client.


The vendor has provided an MSI, which I can customise with their own administration tool to create an MST. Any file additions (such as files with theme settings) are suggested to be deployed with a 3rd file, a companion msi. When the MST and Companion MSI are created, running the Setup.exe installs the application fine.


My issue is that, deploying with Group Policy, I need an MSI and MST and not use the Setup.exe. If I create an MST with their tool, it then won't apply when I run it at a command prompt. If I try to create an MST with InstallShield Tuner (a simple response transform), Tuner comes back with an error that no TARGETDIR is set and won't create the transform.

I very simply need to install the original MSI with 2 files and 3 shortcuts to be deployed in addition. Has anyone experience of this app, or in a similar case where a change to the vendor MSI (regarding this TARGETDIR error) allowed an MST to be created which would apply?


I have contacted the vendor, and they have had a look at it (I suspect they outsource their packaging) and they have come back saying they don't have the resources at the moment to change any MSI for us. If I can't get a solution I'm going to have to repackage, which I would like to avoid of course. In the past at this client, they have repackaged this app due to various different issues.
0 Comments   [ + ] Show Comments

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.

Answers

0
ORIGINAL: Blue_Demon

If I can't get a solution I'm going to have to repackage, which I would like to avoid of course.




Why ? Your giving way too much credence to a vendor MSI, it doesnt work remember. Re-package it and it will work.


Can you not specify the TargetDIR in your transform ?
Answered 05/03/2009 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
The MSI works on it's own.


When combined with an MST (generated with their tool) and a Companion MSI, a Setup.exe installs everything fine.


Unfortunately, with Tuner, I cannot generate an MST with Installshield.

Also, the MST created with their tool won't apply if not being installed as part of a Setup.exe



A repackage seems like a lot of work to be able to install 2 extra files and 3 shortcuts. There has to be a simple setting in the MSI that can be changed to allow this to be done?
Answered 05/03/2009 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
I'm not too familiar with Tuner from AdminStudio, but I know at times with Wise I'm unable to create an MST using install tailor because I'm unable to run the vendor msi directly without providing command line parameters, such as TARGETDIR. What I've done in these instances is create a blank MST rather than use the wizard and then apply it to the MSI with whatever options/parameters I want.

- J
Answered 05/04/2009 by: jcarri06
Senior Purple Belt

Please log in to comment
0
Although I normally recommend avoiding the direct editing of vendor MSIs, in this case - providing you keep a back-up of the original - why not simply set TARGETDIR in the MSI using Orca or InstEdit?
Answered 05/04/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

Although I normally recommend avoiding the direct editing of vendor MSIs, in this case - providing you keep a back-up of the original - why not simply set TARGETDIR in the MSI using Orca or InstEdit?


I can give that a try.


Not sure why the MST created with their tool wouldn't apply though, perhaps they have some setting in the MSI that only applies the MST if it is run by the setup.exe?


Ever seen something like that before?
Answered 05/04/2009 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
ORIGINAL: jcarri06

I'm not too familiar with Tuner from AdminStudio, but I know at times with Wise I'm unable to create an MST using install tailor because I'm unable to run the vendor msi directly without providing command line parameters, such as TARGETDIR. What I've done in these instances is create a blank MST rather than use the wizard and then apply it to the MSI with whatever options/parameters I want.

- J


You did this when wanting to create a response transform??
Answered 05/04/2009 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
You did this when wanting to create a response transform?? Why do you ask? A response transform merely records property values from dialogs and Custom Actions. Provided the packager knows the property names and appropriate values to use, this is a sound tactic.
Answered 05/05/2009 by: VBScab
Red Belt

Please log in to comment
0
I found a LaunchCondition for the TARGETDIR which was stopping the creation of the MST. I removed it with Orca and was able to generate an MST which will apply to the MSI.


That's the good news, adding one file is still an issue. Even though it appears like the file is set for deployment within the MST, it doesn't deploy. And the 3 new shortcuts all point at that file. Log indicates that the transform is applied, but the file still doesn't get deployed??? Frustrating.
Answered 05/05/2009 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
Check the log for the installation status of the file's parent feature and component. Maybe it's conditioned in some way...
Answered 05/06/2009 by: VBScab
Red Belt

Please log in to comment
0
I've created a new component with the same name as the file.


The log file has details on the component, and nothing on the file.

MSI (s) (F4:A8) [15:19:06:973]: Component: Mainframe.rd3x; Installed: Absent; Request: Null; Action: Null



I even tried editing the vendor MSI and it won't deploy the file. I drag and drop the file, it adds it to the AllOtherFiles component and then appreas to ignore it completely when it installs. There has to be some condition on it.


All to try to get us to use their packaging tool I guess. Quite annoying.
Answered 05/06/2009 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
The log file has details on the component, and nothing on the file.That's because it's not selected for installation:MSI (s) (F4:A8) [15:19:06:973]: Component: Mainframe.rd3x; Installed: Absent; Request: Null; Action: NullI suspect it belongs to a feature which hasn't been selected for installation.
Answered 05/07/2009 by: VBScab
Red Belt

Please log in to comment
0
Doh! [&:]


Have it installing now. There's an issue when trying to start the application, so I'll run through all the components and make sure they're being installed, some might be missed as the original setup.exe is calling them rather than the MSI.
Answered 05/11/2009 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
There's an issue when trying to start the applicationUse ProcMon, or your favoured process/file/registry monitor. It will identify the problem much quicker than you wading through files and registry data. It'll almost certainly be either a missing file/dependency, missing registry data (most likely non-registration of a DLL/OCX) or permissioning.
Answered 05/12/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

There's an issue when trying to start the applicationUse ProcMon, or your favoured process/file/registry monitor. It will identify the problem much quicker than you wading through files and registry data. It'll almost certainly be either a missing file/dependency, missing registry data (most likely non-registration of a DLL/OCX) or permissioning.


Had a quick chat with the vendor on it.... seems it might be related to some files which are not being deployed, which are connected with our session file. Will run some tests now, don't think it's a DLL?OCX issue in this case, luckily enough!! [:)]

Thanks for your help, as always.
Answered 05/12/2009 by: Blue_Demon
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity