Link to home
Start Free TrialLog in
Avatar of kalyangkm
kalyangkmFlag for United States of America

asked on

InstallShield 2015 trial Version-Set Registry key permissions

Hi,

I am using InstallShield 2015 Trial version. I don't see "Permissions" buttons as mentioned in the help file. Need help with setting permissions for registry key.

Thanks.
Avatar of Vadim Rapp
Vadim Rapp
Flag of United States of America image

What do you need to accomplish with permissions?
In MSI installations, permissions are specified in the table LockPermissions. If your trial version has direct editor under Installation Designer, you can use it; otherwise, open resulting MSI in Orca (or any other MSI editor) and add the lines you want.  See https://support.microsoft.com/en-us/kb/288975 for details.
Avatar of kalyangkm

ASKER

I need my application to read and update registry values. Please let me know  how to set permissions from direct editor.
Add line to the table LockPermissions, as described in the article.

That said, usually the permissions on the registry keys created by the installation are sufficient without any extra efforts.  Can you tell, where are the values that your application needs to write and update?
By default administartors have full permissions, but other users dont have full permissions. So I need to set full permissions to all users.
ASKER CERTIFIED SOLUTION
Avatar of Vadim Rapp
Vadim Rapp
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
correction: leave Domain empty.
Thanks for the answer. I  have one more question.

I am creating registry keys , installing and starting services using installscript. I have no idea when should i delete keys and remove my Windows service while uninstalling. I mean, What is the function to write all removing code part_ Installshield doesnt do this by deafult.
Windows Installer is supposed to remove upon un-installation everything that was installed, without any extra efforts, including services, registry keys, files, and more. One widespread scenario where it's not happening is testing your installation on "dirty" machine, especially on development machine. Always test on clean virtual machine that you can reset to just-installed snapshot by one click. Avoid testing installations on your development machine, unless you enjoy clean installations of Windows.

Make sure you run validation of your installation, and make your best to address the findings.

I would highly recommend to forget about installscript once and forever. There are very few technologies that throughout the years have resulted in the amount of trouble for the users that could compete with Installscript. Use Basic MSI.
I am able to figure out the answer. Thanks for the help.