MSI Self Healing
Working on a vendor MSI that has about 10 Features. I moved all the Features into a single parent Feature and also created an advertised shortcut which i want to Self Heal so it can copy all the Current User registry settings. I want my MSI to Self Heal but no luck what am i doing wrong here? I've already tried an ActiveSetup but no luck. Please advise
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
timmsie
14 years ago
Posted by:
thugz888
14 years ago
Posted by:
mekaywe
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
stabish
14 years ago
timmsie - All the Features are now a child feature to my new feature.
thugz888 - Shortcut is located under one of the child feature.
mekaywe- I can accomplish this with an Active setup by copying and xcopy command in my active setup stub path but i actually wannated my MSI to self heal n copy the registry setting.
VBScab - I started wondering what happend to you, there were about 30 sum hits but no reply to my post yesterday, im glad to hear from you & i will follow up on John McFadyens blog hope i'll find something good there....
thugz888 - Shortcut is located under one of the child feature.
mekaywe- I can accomplish this with an Active setup by copying and xcopy command in my active setup stub path but i actually wannated my MSI to self heal n copy the registry setting.
VBScab - I started wondering what happend to you, there were about 30 sum hits but no reply to my post yesterday, im glad to hear from you & i will follow up on John McFadyens blog hope i'll find something good there....
Posted by:
pjgeutjens
14 years ago
stabish,
3 things
1) try making a new parent level feature that contains your CU settings. See if that will get repaired ...
2) when using Active Setup you could use the command msiexec /fu <ProductCode> instead of an xcopy, thus letting Windows Installer handle the setting
3) there's a very long and fairly recent thread on self healing mechanisms somewhere on these message boards, you should try to find it.
Rgds,
PJ
3 things
1) try making a new parent level feature that contains your CU settings. See if that will get repaired ...
2) when using Active Setup you could use the command msiexec /fu <ProductCode> instead of an xcopy, thus letting Windows Installer handle the setting
3) there's a very long and fairly recent thread on self healing mechanisms somewhere on these message boards, you should try to find it.
Rgds,
PJ
Posted by:
cygan
14 years ago
ORIGINAL: stabish
VBScab - I started wondering what happend to you, there were about 30 sum hits but no reply to my post yesterday, im glad to hear from you & i will follow up on John McFadyens blog hope i'll find something good there....
EASY EASY
if ian decides to quit appdeploy or go on a holiday to hawaii hope you will cope without him
as was suggested
what you need
an advertised shortcut
create a feature make it the parent - add your hkcu stuff into your hkcu components
make sure the child features have your parent feature as the top feature
features/ features component table
and thats it
over to you ian =)
Posted by:
anonymous_9363
14 years ago
I've been trying to work out why anyone would move all an MSI's features into one. Then I thought that maybe the OP wants every feature to be repaired, if any component is broken which is..........an individual approach.
As I keep saying, if you go the AS route, remember that you get no self-healing: it's a one-hit deal.
As I keep saying, if you go the AS route, remember that you get no self-healing: it's a one-hit deal.
Posted by:
pjgeutjens
14 years ago
ASetup it is :) thanks guys
Stabish,
while it's good you've chosen a solution, I would like to point out that, given the fact that you're able to use advertised shortcuts and self-healing, you should really try to. I've always considered Active Setup to be an alternative in situations where you can't use self-healing. Self-healing is, in my opinion, a much more stable and dependable solution. I understand that you may be under time pressure to deliver the package, but I can only advise you to try the suggestions in this thread and work on the better option some more. It might save you grief in the future.
Also, like Ian said, unless you have a really good reason to reshuffle the vendor msi's feature structure (and personally I cannot really think of any), you should really leave that as-is and add your User Settings in a top-level feature alongside it.
Rgds,
PJ
Posted by:
rbrucelee1978
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.