Why simply do a routine that check if firefox is still install and wait for it to be false before running the install? Doing so in a script will solve the problem.
I myself is using the stock exe, modification made with CCK2. I supersede without uninstall, simply to replace older deployment. The autoupdate in background is better than uninstall/install, especially because users lose all there shortcut and Firefox get closed when uninstall, not to user friendly. JEAN-SÉBASTIEN FRENETTE Analyste - Environnement bureautique Parc & Gestion des actifs Service des technologies de l'information (514) 350-1357 [email protected] -----Message d'origine----- De : Enterprise [mailto:[email protected]] De la part de Klaus Hartnegg Envoyé : 10 octobre 2016 12:01 À : [email protected] Objet : Re: [Mozilla Enterprise] SCCM always rings twice Am 10.10.2016 um 16:40 schrieb Hunziker, Jonas M (Henderson): > The fix was to create a Firefox uninstall package in SCCM that waits > 10 seconds after the uninstall has been triggered. The problem with this fix is that sometimes a PC may be slow and take more than 10 seconds for the uninstall. Then this will fail. This was one of the reasons why I decided to build an MSI file for Firefox. With this the uninstall is handled by windows installer, and that is 100% reliable. _______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe" _______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
