The automatic update solution is great for companies who are incapable of deploying a Flash update before Firefox blacklists it.
The Flash auto-updater is a scheduled task that by default runs once an hour every hour, regardless of the browser. I'm not sure why a company who has virtual desktop infrastructure doesn't have SCCM or another tool to deploy Flash updates. Daniel Wolf -----Original Message----- From: Enterprise [mailto:[email protected]] On Behalf Of Klaus Hartnegg Sent: Tuesday, April 19, 2016 6:45 AM To: [email protected] Subject: Re: [Mozilla Enterprise] Firefox 45 deploy with Flash + Java Click_to_Play off One solution could be to disable the automatic update of the blocklist of Firefox. Then Firefox does not know that flash is outdated. Am 19.04.2016 um 00:08 schrieb Wolf, Daniel: > If deploying updates to computers is beyond your organization's abilities, > here's the administration guide for Flash, which details how to enable > automatic updates. He said he cannot do AUTO-Updates, which I perfectly understand, because some enterprise-procedure are simply incompatible with this concept, and most auto-updaters are crap anyway. > Create a text file named mms.cfg and put the following in it: > > AutoUpdateDisable=0 > SilentAutoUpdateEnable=1 > > And place it in the following locations with Group Policy Files Preferences: > > "%windir%\system32\Macromed\Flash\" > "%windir%\SysWOW64\Macromed\Flash\" > > That way Flash will update itself and you never have to worry about it being > disabled by Firefox. One of the problems with this is that it appears to be only triggered when Flash is actually being used. If one computer does not use it for a while, the old version remains installed. Another problem is that it always comes too late. Not only that it checks at most once per week. Also when it finally does check, the old version will keep being used the whole day, and only then it will switch to the new version. Also he wrote they are using virtual machines, so they might reset them to a snapshot before each use. This is what I am doing on my computer. This means that "auto-update" would *never* update, because it always runs when it is too late. In this case auto-update is definitely not an option, they can only deploy a new virtual machine image. By the way due to the shortcomings of the automatic updater, a manual deployment of an updated image can actually reach the client machines earler than the "automatic" update would. _______________________________________________ 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"
