/build/static/layout/Breadcrumb_cap_w.png

self-healing trigger

hi all,
i have a repackaged app that has to be installed per-user. it's an internet addon.
there is no trigger to repair the installation for a user. how can i force a repair, aside from active setup?
if i have no choice, i'll use active setup, but it frequently is in conflict with sccm deployments.
thanks!
PS: the edit field in ITNinja is too small :(

0 Comments   [ + ] Show comments

Answers (6)

Answer Summary:
Posted by: pjgeutjens 9 years ago
Red Belt
4
While I have no way to give you practical advise on this case without actually seeing the contents of the package, you should know that shortcuts are not the only advertisement mechanism available in an MSI. I believe there are a total of 5 tables that can contain advertised entrypoints, i.e. Class, ProgID, Mime, Extension and Shortcuts, but there might be more, you should look it up :-)

If you can populate one of these in your package you should be able to trigger self-healing even without a shortcut.

PJ
Posted by: andys0123 9 years ago
Orange Senior Belt
1
Create an SCCM program to install your MSI (with no Active Setup) & set it to run ‘Only when a user is logged on’. On the Advanced tab, under ‘When this program is assigned to a computer’, set the dropdown to ‘Run once for every user who logs on’.

Comments:
  • hmm, interesting. i'll try that.
    thanks! - kardock 9 years ago
  • Altiris and Zen both have these options as well; other products I cant speak for, but it certainly makes life a lot easier. - Moedius 9 years ago
Posted by: dandirk 9 years ago
Third Degree Green Belt
0
pjgeutjens or Andys0123 are probably you bet bet. I have never had to do a class or extension entry point/self-heal but know it can be done. There isn't a whole lot of info about it, since most use shortcuts.

Though the argument against active setup, applies also to advertised entry points/self-heal. (Conflicts with SCCM installations).

Thus Andy's solution is probably the better one, since SCCM will manage its installations in order.
Posted by: Arminius 9 years ago
Second Degree Green Belt
0
Normally I'd say to use an advertised shortcut. However, since it's an internet add-on, there most likely won't be a shortcut that the user will launch to trigger that. You could put some things in the default user profile, but that won't help the users with existing profiles. IMHO, you're stuck. Maybe someone smarter than I has a better idea.

Comments:
  • that someone needs to be smarter than me too ;-) - kardock 9 years ago
Posted by: piyushnasa 9 years ago
Red Belt
0
Active setup is the only solution for these cases. What conflict does it have with SCCM deployments?

Comments:
  • as an example, when we image a computer, in the apps phase, there are multiple reboots. if an active setup kicks off, another app can say that it can't install because msiexec is busy. - kardock 9 years ago
    • That is why I avoid using calls to MSI files in active setup. Creating the user deployment with Wisescript Editor is so much more reliable. - EdT 7 years ago
Posted by: pjgeutjens 9 years ago
Red Belt
0
Adding to my previous comment, have a look at this link:
http://www.symantec.com/connect/articles/deploy-msis-have-no-advertised-entry-points

The vbs solution at the bottom might be interesting to you, basically triggering a selfheal at each logon if needed for that specific user through a ..\CurrentVersion\Run key. It seems more robust to me than an ActiveSetup solution..

PJ

Comments:
  • i checked this vbs solution but it's the same as active setup, msiexec will be busy after the reboot. i'm looking for a way to repair this addon when IE is launched.
    thanks! - kardock 9 years ago
 
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