Not packaged for a while, HKCU selfhealing query
I need to get a package together to insert a single HKCU entry. Its a locked down environment with restricted users so I'll need to do this through self healing so the key gets populated on user first signon - I've done this through a CurrentUser/Complete feature mod in Wise Package Studio.
When I did this before (a few years ago), it was when I packaged Winzip 9. As theres an application, the self healing was triggered by starting Winzip through the shortcut.
As this package doesn't have an application, is there an easy way to trigger the HKCU self healing without having the usual advertising points?
All the package needs to do is set a single key to allow "Word for Windows 2.0" files to be opened in Word 2003 but it needs to go into the current user hive.
Any assistance gratefully received....
When I did this before (a few years ago), it was when I packaged Winzip 9. As theres an application, the self healing was triggered by starting Winzip through the shortcut.
As this package doesn't have an application, is there an easy way to trigger the HKCU self healing without having the usual advertising points?
All the package needs to do is set a single key to allow "Word for Windows 2.0" files to be opened in Word 2003 but it needs to go into the current user hive.
Any assistance gratefully received....
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
langa100
14 years ago
Use ActiveSetup details in the link http://itninja.com/blog/view/appdeploy:-articles:-activesetup
Posted by:
upthorpe
14 years ago
Thanks for the article link, I've never had to do it this way before but once I understand what I need to do, it looks like this will be just what I need...
Posted by:
MSIPackager
14 years ago
Yes if you don't have an advertised shortut as an entry point to invoke self-healing then your best bet is AS - it's a handy tool to understand anyway [:)]
Posted by:
AngelD
14 years ago
Why not abuse the COM-Advertising from the Office 2003 package so the self-healing triggers a repair for the "HKCU" package when Word 2003 is launched.
AS is much cleaner but it is possible :)
AS is much cleaner but it is possible :)
Posted by:
upthorpe
14 years ago
This won't be installed on all machines, only those ones whose user needs to access old format docs. I'm going to do some tests with the active setup - it does look pretty good and would have saved me time and a lot of grief if I'd have known about it a couple of years ago.
The way I read it, it looks like I have two options:
1) Put something like "regedit.exe /s <<PATH>>myregfile.reg" into the stubpath - meaning a new package would need to set up the HKLM active setup entry AND put the "myregfile.reg" somewhere loal on the machine to be referenced in the stubpath.
2) Change my existing package to create the HKLM active setup, and use an "msiexec /f" <<GUID>> in the stubpath to force the selfhealing for user sign=on
The way I read it, it looks like I have two options:
1) Put something like "regedit.exe /s <<PATH>>myregfile.reg" into the stubpath - meaning a new package would need to set up the HKLM active setup entry AND put the "myregfile.reg" somewhere loal on the machine to be referenced in the stubpath.
2) Change my existing package to create the HKLM active setup, and use an "msiexec /f" <<GUID>> in the stubpath to force the selfhealing for user sign=on
Posted by:
MSIPackager
14 years ago
Yes you have those two options..
Given that it's a single reg key you could probably also get away with just running the reg add command directly
Personally I'd go for the msiexec /f repair option but use /fu to just repair user reg entries.
Given that it's a single reg key you could probably also get away with just running the reg add command directly
Personally I'd go for the msiexec /f repair option but use /fu to just repair user reg entries.
Posted by:
pjgeutjens
14 years ago
2) Change my existing package to create the HKLM active setup, and use an "msiexec /f" <<GUID>> in the stubpath to force the selfhealing for user sign=on
Might just seem like a detail, but I'd go for /fu instead of /f, matter of limiting the scope of the repair to just what you need.
EDIT: beaten by 74 seconds [:(]
Posted by:
MSIPackager
14 years ago
EDIT: beaten by 74 seconds
haha - I hate it when that happens! It's usually Ian that gets me [:@]
Of course another option - to avoid he package / AS solution for 1 reg key is to use the logon script (or possibly group policy) but let's not start talking ourselves out of work here!
Cheers,
Rob.
Posted by:
anonymous_9363
14 years ago
Remember also that AS is a one-off - the setting won't get repaired/healed.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.