New MSI does not run when a different user logs in
I have created an MSI for PaintShopPro with Wise Package Studio, as I want to deploy PSP to several desktops. To create the MSI, I logged in as Admin user (full administrator rights) and installed PSP whilst Wise Package Studio was watching my system. This created an MSI which runs sucessfully when I log on as admin.
However.... when I log in as another user (a test user with no admin rights) the registry keys I have added in HKEY_CURRENT_USER do not work. The package runs, but the changes I have made are not installed.
I tried adding these keys instead to HKEY_LOCAL_MACHINE but this location is not picked up by PSP.
So my question is: how do I force a new install to happen when a new user logs in? (just to change the registry keys in HKEY_CURRENT_USER).
This must be possible, as I have created an MST for Adboe Acrobat MSI that does precisely this, and it works fine. The new user logs in, runs Acrobat and they get a short installation dialog (which they don't need to click anything in, great!) which adds the new registry key. But I can't find a way of forcing this new installation dialog in Wise.
Any ideas?
I have changed the isntallation method to Machine instead of Current User. I have added the keys I want into HKEY_CURRENT_USER.
However.... when I log in as another user (a test user with no admin rights) the registry keys I have added in HKEY_CURRENT_USER do not work. The package runs, but the changes I have made are not installed.
I tried adding these keys instead to HKEY_LOCAL_MACHINE but this location is not picked up by PSP.
So my question is: how do I force a new install to happen when a new user logs in? (just to change the registry keys in HKEY_CURRENT_USER).
This must be possible, as I have created an MST for Adboe Acrobat MSI that does precisely this, and it works fine. The new user logs in, runs Acrobat and they get a short installation dialog (which they don't need to click anything in, great!) which adds the new registry key. But I can't find a way of forcing this new installation dialog in Wise.
Any ideas?
I have changed the isntallation method to Machine instead of Current User. I have added the keys I want into HKEY_CURRENT_USER.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
cdupuis
19 years ago
Change the MSI to install for "ALLUSERS". You should be changing the value to 1.
Posted by:
MSIMaker
19 years ago
You could also export the CurrentUser registry settings and then reimport them to their own component with its own keypath.
The missing keypath will trigger the self repair for any user that runs PSP from its shortcut.
The missing keypath will trigger the self repair for any user that runs PSP from its shortcut.
Posted by:
olivier
19 years ago
hi,
I have a similar problem but no shortcut (no advertising). Is there a possibility to "self repair" and install registry key wihout a shortcut?
already read an articel but didn't help me
http://www.wise.com/KBArticle.aspx?articleno=1438&keywords=
olivier
I have a similar problem but no shortcut (no advertising). Is there a possibility to "self repair" and install registry key wihout a shortcut?
already read an articel but didn't help me
http://www.wise.com/KBArticle.aspx?articleno=1438&keywords=
olivier
Posted by:
MSIMaker
19 years ago
You could create a Wisescript to act as the shortcut and have it insert the registry keys and then start the app for you.
Posted by:
Richard_Artes
19 years ago
Thanks for all your tips guys.
cdupuis - Yes I already had ALLUSERS=1, this made no difference.
moderator - How do I 'reimport CurrentUser registry settings to their own component with its own keypath' ?
olivier - you're on your own there i'm afraid buddy! (Any luck?)
moderator - How do I create a Wise Script to do this ?!?!?
Sorry if I seem such a novice - I am. But we all gotta start somewhere!!!
cdupuis - Yes I already had ALLUSERS=1, this made no difference.
moderator - How do I 'reimport CurrentUser registry settings to their own component with its own keypath' ?
olivier - you're on your own there i'm afraid buddy! (Any luck?)
moderator - How do I create a Wise Script to do this ?!?!?
Sorry if I seem such a novice - I am. But we all gotta start somewhere!!!
Posted by:
MSIMaker
19 years ago
Richard
If you want to have the registry split into components then do the following
Ok start on the Installation Expert page and go to Registry tab.
1. Select HKCU key and right click.
2. Export to reg file. Call it HKCU or whatever. Save the file in a source folder.
3. Do the same for HKCR and HKLM keys.
3. Go to Setup Expert page.
4. Go to Features Tab
5. Right click on the Complete feature and select New > Registry key.
6. Drill down and right click the registry icon and select Import .REG file.
7. Import your registry files 1 at a time.
Now your registry key are in their own components. So you can move them to whichever feature you want and can ensure that self repair will happen if a component is missing.
I like to move the HKCU component into its own feature.
Hope this helps.
-----------------------------------------------------------------------------------------------
Olivier,
I dont think its possible to do what you are asking......you must have a trigger point for the self repair or you have to script it within Wise.
If you want to have the registry split into components then do the following
Ok start on the Installation Expert page and go to Registry tab.
1. Select HKCU key and right click.
2. Export to reg file. Call it HKCU or whatever. Save the file in a source folder.
3. Do the same for HKCR and HKLM keys.
3. Go to Setup Expert page.
4. Go to Features Tab
5. Right click on the Complete feature and select New > Registry key.
6. Drill down and right click the registry icon and select Import .REG file.
7. Import your registry files 1 at a time.
Now your registry key are in their own components. So you can move them to whichever feature you want and can ensure that self repair will happen if a component is missing.
I like to move the HKCU component into its own feature.
Hope this helps.
-----------------------------------------------------------------------------------------------
Olivier,
I dont think its possible to do what you are asking......you must have a trigger point for the self repair or you have to script it within Wise.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.