So the two paths for keeping up with Adobe quarterly and or security updates is to either package the applicaiton (includes custom mms.cfg) which we currelty perform or now that we have moved from SCCM to to SMP 7.5 SP1, leverage patch management solution.
The latter choice of staging and deploying a quarterly/security update of Flash Player ActiveX is a novel idea. However, with that patching the customer loses their mms.cfg file and one is replaced with Adobe's default mms.cfg (which includes automatic updates enabled) - not ideal in an enterprise environment.
How would one handle leveraging patch management solution for this product but ensuring the mms.cfg in Windows 7 is your custom version vs. Adobe?
I have test both major release upgrades, quarterly, and security updates and they all replace the mms.cfg file back to Adobe default
Is anyone setting up a managed SW delivery that runs a task to replace the file on a scheduled basis? How are you preventing the automatic updates from occuring if you're not managing the disabled automatic update value in your mms.cfg using patch solution?
Any direction would be appreciated.