Hi,
I'm packaging an application called Synchro Tributary, I put every specifications and customization asked by the client but I have a problem with a update's path.
This application has a path for updates, the path point to HKEY_USERS\S-1-5-21-1608400361-xxxx\Software\xxx
That key refers to logued user, but how can I insert it on my msi if they isn't the same for every pc?
0 Comments   [ + ] Show Comments

Comments

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
you should put it under HKEY_CURRENT_USER
Answered 04/27/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
Add the key in HKCU\Software\xxx and create active setup. When you logoff and login to the machine then those keys will come to every user....
Answered 04/27/2011 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
Close, but no cigar.

You should either create a new feature containing the HKEY_CURRENT_USER data and make that feature the parent of an existing feature which contains an advertised entry-point e.g. an advertised shortcut or you could use Active Setup. Both have been dealt with at length here on AppDeploy so search for "self healing" or "repair" for the former or "Active Setup" for the latter.
Answered 04/28/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

Close, but no cigar.

You should either create a new feature containing the HKEY_CURRENT_USER data and make that feature the parent of an existing feature which contains an advertised entry-point e.g. an advertised shortcut or you could use Active Setup. Both have been dealt with at length here on AppDeploy so search for "self healing" or "repair" for the former or "Active Setup" for the latter.



exactly what i was saying!

[:D]
Answered 04/28/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
Excellent! I did it, I put the key under HKCU in the same feature that the shortcut...
Answered 04/28/2011 by: cmi2000
Senior Purple Belt

Please log in to comment
0
...meaning that your MSI/MST probably won't validate because you now have mixed machine-level (shortcut) and user-level (HKCU registry data) components.

Create a NEW feature for your HKCU stuff and make IT the parent of the feature containing an advertised entry-point.
Answered 04/28/2011 by: VBScab
Red Belt

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