Configurations on registry
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?
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
Answers (6)
Please log in to answer
Posted by:
sanhivi
13 years ago
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....
Posted by:
anonymous_9363
13 years ago
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.
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.
Posted by:
kardock
13 years ago
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]
Posted by:
cmi2000
13 years ago
Excellent! I did it, I put the key under HKCU in the same feature that the shortcut...
Posted by:
anonymous_9363
13 years ago
...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.
Create a NEW feature for your HKCU stuff and make IT the parent of the feature containing an advertised entry-point.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.