/build/static/layout/Breadcrumb_cap_w.png

Do you like or hate self healing?

I recent ran accross a situation where a company is considering to change the way MSIs are packaged. They want to minimize self healing because they are finding out that self healing is causing applications to wreck each other. What is your experience with self healing in the enterprise?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: WayneB 17 years ago
Blue Belt
0
kkaminsk,

Just thinking it through, we are gearing up our packages to be Vista compatable, I believe self healing is going to be an issue in regards to User Account Control (UAC). If you haven't seen the remifications, check out this blog:
http://silverstr.ufies.org/blog/

Anyway, we'll run them up on Vista and see what gives. I'm betting a formalised repair functionality is the way to go ie KIS (Keep It Simple) principles and following correct packaging guidelines (isolation, per machine etc).

Cheers
WayneB
Posted by: revizor 17 years ago
Third Degree Blue Belt
0
Kkaminsk,
I've seen (and early in my days authored myself) several sloppy packages that kept kicking off self-healing for all wrong reasons.
People hated it, and rightfully so.

Currently I prefer not to resort to self-healing features for HKCU registry keys because of the terminal environment considerations.
Self-healing is a nice feature, though, to ensure package integrity (if done properly).

I think it would make whole a lot of difference if self-healing routines were optimized a little bit better, with users not having to wait for 2-3 minutes for an application to open...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ