Hi,

I am creating packages using a launch condition so I can restrict users from installing our application. Here is an example of the command line to launch my app:

msiexec.exe /I "acrobat.msi" /QB VALUE=0

If VALUE is 0 then my application will install, if not then it will not install.

Now here is my problem. I would like to give the users the capability to remove application by selecting to remove from ADD/REMOVE programs. Unfortunately, my launch condition prevents this. Only way to remove is through another command line:

msiexec.exe /X "acrobat.msi" /QB VALUE=0.

Do any of you guys have an idea where I can store the Property Value = 0 so that user can simply select "Remove" to uninstall the app? Your help is greatly appreciated.

BTW: I tried to manipulate the UninstallString to MsiExec.exe /I{GUID} VALUE=0 and this didn't work.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
During uninstalls, the property REMOVE is set to 1. Add an IF THEN somewhere in the beginning of the MSI Script so if REMOVE then set property VALUE to 0.

That's an odd way of restricting installs, btw...
Answered 02/15/2005 by: VikingLoki
Second Degree Brown Belt

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
Thanks "VikingLoki". It worked beautifully. [:)]

BTW: Just for giggles, how would you limit users from installing apps?
Answered 02/15/2005 by: chungt1
Senior Yellow Belt

Please log in to comment
2
Windows security policies. If you're restricting installs for users, those users are usually a member of the USERS local security group. This group can't install software or change base OS configuration. To install software for them, it's either pushed by a distribution system that has local admin security access, or manually installed by staff with local admin access. I've also seen it done so that the user can install/reinstall any software they have been approved for, the approval list is accessed through a browser and the web session can initiate the install with local admin access.

Adding a stealth value requirement would restrict installs, but only on software you repackage. It only amounts to security through obscurity, which isn't all that secure. The cat's out of the bag once the secret value is exposed. It also wouldn't stop them from installing System Choker Holiday Screen Saver and other lovely apps... unless you found another obscure hurdles for that too. :-)
Answered 02/15/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Hi "VikingLoki",

You are absolutely right. Unfortunately, the user I am targeting are remote contracted financial support employee who loads our financial apps via CD in remote locations. We had to come up with a simple solution where users would not load our CD on other machines. The property value changes using an encrypt program depending on the app.

I know it would not stop determined pirates, but we just wanted to prevent casual pirates. Thanks for all your help.

Chungt1
Answered 02/16/2005 by: chungt1
Senior Yellow Belt

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