Urgent help needed........
Hi All
I am working on an application which has msi as a source. it install fine for admin users but when i am installing it on test user account and launching application from start /menu it starts installing application again.and creates a desktop shortcut. Also i noted the shortcut is advertised shortcut. i tried to change it to non-advertised shortcut and install application through msi and mst in standard user/test user but it still starts new application installation when launched from start /menu. does any one knows how i can make changes to msi --shortcuts sections or some where in msi in order to not the relaunch of application in standard user?
Appreciate responses.
Thanks
I am working on an application which has msi as a source. it install fine for admin users but when i am installing it on test user account and launching application from start /menu it starts installing application again.and creates a desktop shortcut. Also i noted the shortcut is advertised shortcut. i tried to change it to non-advertised shortcut and install application through msi and mst in standard user/test user but it still starts new application installation when launched from start /menu. does any one knows how i can make changes to msi --shortcuts sections or some where in msi in order to not the relaunch of application in standard user?
Appreciate responses.
Thanks
1 Comment
[ + ] Show comment
Answers (3)
Please log in to answer
Posted by:
dj_xest
10 years ago
Since you are installing for a test user, I assume that you are using another account with admin permission or might be using a deployment tool running in system context. Whatever the case is, the reason for that self-healing is missing a missing a keypath that could be residing on user's profile or HKCU registry. Go and search the Event Viewer and find out the component so you can track down the real culprit.
Once you have done that, you have 2 choices that I can think of right now. Use the active setup approach and repair the MSI using the /fu or /fup stub path once the user has logged and logged in. The other one one is to set the shortcut to non-advertised but I have no idea how you did it so I guess that you made it incorrectly.
Once you have done that, you have 2 choices that I can think of right now. Use the active setup approach and repair the MSI using the /fu or /fup stub path once the user has logged and logged in. The other one one is to set the shortcut to non-advertised but I have no idea how you did it so I guess that you made it incorrectly.
Comments:
-
hi thanks for reply. i tried to use mst and change the shortcut to non-advertised which is advertised originally. how i can change shortcut to non advertised in msi itself? also obeserved that application does not launch start /menu shortcut if it is installed with msi and mst or if i do some changes in msi. what may be the reason? it launches shortcut only when i am installing it through vendor msi. - swap20june 10 years ago
-
I don't recommend changing the shortcut to a non advertised. Since the vendor set that, it would be better for you to apply the Active Setup if you dont wan't the application to self heal on first launch, yet applying the user's profile reg keys or files. Normally, repair will trigger a default of "sumo" (check msiexec parameters for details) and we want to avoid it by initiating a repair during Active Setup to only repair the missing files or specific user registry keys (hkcu). Disable or delete also the shortcut in desktop because during a self heal, I am sure that it will also come back.
Do this, install your application and load the HKCU reg keys that you have just captured and see if it's still going to repair on first launch. If it does not repair anymore, then follow what I have just said about AS. If not, keep looking for more missing keypaths. - dj_xest 10 years ago
Posted by:
EdT
10 years ago
Does the repair happen repeatedly for a non-admin user, or just once? Clearly from the event log, the repair is being triggered because of missing registry keys in the user profile. If the MSI is correctly structured, this should be able to complete without needing elevated privileges or any special solutions such as active setup. Simplest fix is to create a new feature which is the parent of all other features, create a new component in this feature, and move the user registry keys into this component ensuring that the key path is set as before. This will limit the extent of the self healing to just the registry keys needed for the user profile, and you will not need to change the advertised status of the shortcuts. Since there are five different ways that an application can trigger self healing, just changing shortcuts to non-advertised only addressed one of them.
Posted by:
cornevdb
10 years ago
First question that comes to my mind:
How are you distributing this installation?
Depending on that, the answer to your question may vary.
Comments:
-
hi i am using sccm 2007 for deployment and can we use non advertised shortcut method instead of active setup?it sounds easy but non advertised shortcut doesnt work... - swap20june 10 years ago
-
indows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Medtronic]
[HKEY_CURRENT_USER\Software\Medtronic\Medtronic N'Vision® Report Link]
[HKEY_CURRENT_USER\Software\Medtronic\Medtronic N'Vision® Report Link\Settings]
"AutoOpenDirectory"=dword:00000001
"Directory"="C:\\ProgramData\\Medtronic NVision Report Link"
"FirstRun"=dword:00000000
"StartWithWindows"=dword:00000001
"Language"=dword:000003e8
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
"Report Link"="C:\\Program Files (x86)\\Medtronic\\Report Link\\Medtronic N'Vision® Report Link.exe" - swap20june 10 years ago
Detection of product '{B2366536-4B5E-418A-B681-A8DB857AA96C}', feature 'DefaultFeature' failed during request for component '{C30C0D74-D734-9B6B-3845-AB4DB04C7458} and
Detection of product '{B2366536-4B5E-418A-B681-A8DB857AA96C}', feature 'DefaultFeature', component '{5268CF88-47C2-7AF8-2F5D-1035D7F2F908}' failed. The resource 'HKEY_CURRENT_USER\Software\Medtronic\Medtronic N'Vision® Report Link\' does not exist. - swap20june 10 years ago