1 person found this helpful
If you haven't done already, apply for the Adobe Flash Player Distribution Rights for your company https://distribute.adobe.com/mmform/index.cfm?name=distribution_form&pv=fp , then you get access to a special page. On this page you'll find all required Downloads for distribution inside a company.
There is also the "Background Updates Resources" archive you can extract this and put it on a web server.
Then the only thing that's left is to change the mms.cfg on the clients to point to this web server. You could use a machine login script, GP preferences or other deployment tools at your hand to get this file out to your clients.
It's all outlined in the guides on the distribution page.
Page 28 "Backgroud Updates from an internal server"
Needless to say, that you have to download the Archive and extract it to your server every time a new Flash Player is published.
Had a quick question about the SSL Cert. If the process of Background Updates is all internal, is a SSL cert required?
Could we not do everything that is required and just have it internal?
I guess I'm a little confused. To setup a Flash Background Update Server requires an SSL Cert, but setting up an update Server using the Adobe Update Server Setup Tool (AUSST) doesn't?
AUSST is used for Creative Cloud...completely different technology from the Flash Player Background Update Service, and thus has different requirements. I don't work on CC and am not familiar with that product, or why it doesn't require SSL