This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Strange behaviour when installing per user
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 10, 2008
10:21 PM
Strange behaviour when installing per user
I want to make the setup to install per user rather than for local machine. So based on KB Q105063 I set ALLUSERS. Apparently there are two ALLUSERS variables (the InstallScript ALLUSERS variable and the MSI ALLUSERS property) I have tried the followings:
1. Do not set ALLUSERS
In this case unlike what is said in KB Q105063 it installs for local machine and the registry key goes under HKEY_LOCAL_MACHINE
2. Set the ALLUSERS property in Property Manager with an empty value. (I suppose this is how to set it to NULL)
Installs for Local Machine (all users)
3. Set the ALLUSERS property in Property Manager to NULL. (I think this sets it to string "NULL", but I had to try)
Installs for Local Machine (all users)
4. In the InstallScript use MsiSetProperty(ISMSI_HANDLE, "ALLUSERS", "");
Installs for Local Machine (all users)
5. In the InstallScript set ALLUSERS=FALSE
Installs for user A and the registry key goes under HKEY_CURRENT_USER as expected. Then for user B allows installing in a new directory but depending on the selected features leaves the selected directory empty and overwrites the installation of user A!! Or installs the diff of features selected for user A and user B in the installation path of user B!! When uninstalled by each user uninstalls from both places.
6. In the InstallScript set ALLUSERS=NULL
Same as above.
7. In the InstallScript set ALLUSERS=0
Same as above.
So how should I make it work?
Thanks
1. Do not set ALLUSERS
In this case unlike what is said in KB Q105063 it installs for local machine and the registry key goes under HKEY_LOCAL_MACHINE
2. Set the ALLUSERS property in Property Manager with an empty value. (I suppose this is how to set it to NULL)
Installs for Local Machine (all users)
3. Set the ALLUSERS property in Property Manager to NULL. (I think this sets it to string "NULL", but I had to try)
Installs for Local Machine (all users)
4. In the InstallScript use MsiSetProperty(ISMSI_HANDLE, "ALLUSERS", "");
Installs for Local Machine (all users)
5. In the InstallScript set ALLUSERS=FALSE
Installs for user A and the registry key goes under HKEY_CURRENT_USER as expected. Then for user B allows installing in a new directory but depending on the selected features leaves the selected directory empty and overwrites the installation of user A!! Or installs the diff of features selected for user A and user B in the installation path of user B!! When uninstalled by each user uninstalls from both places.
6. In the InstallScript set ALLUSERS=NULL
Same as above.
7. In the InstallScript set ALLUSERS=0
Same as above.
So how should I make it work?
Thanks
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 13, 2008
12:58 PM
Any ideas how to fix this? I'd appreciate your help.
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 15, 2008
06:58 PM
For reference, the value NULL means enter no value in the scope of the property manager / property table. Entering NULL will set the property to the literal "NULL" as you found.
What project type are you using?
What project type are you using?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 19, 2008
08:52 PM
The project type is InstallScript MSI.
Thanks
Thanks
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 23, 2008
08:33 AM
You may want to try applying this hotfix, rebuilding, and seeing if the issue persists:
http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q113652&sliceId=1&docTypeID=DT_HOTFIX_1_1&dialogID=18740588&stateId=0 0 18742225
http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q113652&sliceId=1&docTypeID=DT_HOTFIX_1_1&dialogID=18740588&stateId=0 0 18742225
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 23, 2008
02:13 PM
My test machines are Windows Servier 2003 Enterprise SP2. Thanks for the link anyways.