Hi,

i have a program which is used by several departments. Every appartment has the same shortcut but with different arguments.
So what i did was the base install in a parent feature and i made child features to have the ability to install the shortcut for the right department. The shorcuts have to point to a cmd file in the parent feature, but this isn't possible.

Adding the cmd file to all of the sub-features doenst help as Wise shows that i use duplicate files. When i want to create a shortcut there arent any files in any of the sub-features.

Who could shine a light? Who has other solutions? Who can help me?
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
Well, most of my answers will point to deploying it via group policy in active directory as it is free and simple (well simpler). My suggestion would be to create a base MSI then a new transform file for each department, then deploy them via group policies and assign the package and the corresponding MST file to the correct OU.
Answered 08/31/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
Hi, can't say I totally understand the solution you are trying to implement but I'd suggest you either;

1) Create a different package for each department, with the relevant command line (inc arguments) run via vbscript - each package can then have just one shortcut.

2) Create 1 base package with all x number of shortcuts (again each unique command line run via separate vbscript) then use a custom .mst file to remove the shortcuts that aren't required for each department.

3) Create just one package which contains all x number of shortcuts which all users will see, leaving them to run the appropriate one - this may not be suitable depending on how secure / sensitive the data is.

We use a product called QVTNet - just a terminal emulator but different depts needs access to different systems (which are just different arguments on term.exe). We use option 1 but have a base package of the QVTNet software, then separate package/s which check for installation of / or install QVTNet first, then run the appropriate command line via vbscript.

Hope this makes sense!

Cheers,
Rob.
Answered 08/31/2004 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
The problem is that when i have to change the msi file, the mst's don't work anymore. How can i solve that problem, besides totally recreate the mst's?
Answered 09/01/2004 by: mickman
Orange Belt

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