We have an application called Dictaphone that we made into an MSI (Wise Package Studio 5.6) The problem is that the Dictaphone server does a check when the client contacts it. If an update is necessary, the files are pushed (or pulled) to the client. After the update, you must double-click the app icon to launch it. As soon as you do that guess what happens...self repair (self healing). Now you just lost the updates the server pushed.

And no we cannot turn off the auto-updates on the server. There are specific machines that only get updates this way.

The only options I see are to manually install the applications (not native msi packages) or somehow turn off the self-healing. This package includes sql pieces and a ton of registry entries (clsid, hkcu, hklm)
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
Hi Gator,
the quickest way to break self healing would be to remove the entry points. This are typically advertised shortcuts, com objects, file extensions and a few others.
Please read: http://itninja.com/question/distribution-message21
http://209.104.132.210/filelib/KB/WindowsInstallerRepair.pdf

Regards, Nick
Answered 08/28/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
If you know what components will be updated in the future, you could just remove the GUID for those components. Then the MSI will abandon them there but keep repairing the rest of the application. Or you could bundle those files/registry entries with a keypath you know won't change.
If you don't know what will be updated, then yes, you'll have to remove all the entry points as Nick said.
Answered 08/29/2006 by: turbokitty
Sixth Degree Black Belt

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