The user settings are set either within the browser or through the Windows Control Panel. This configuration file overrides any user settings that are set in thefile and applies to the computer.
The details about the file are below: Screenshot of file on a Windows 7 32-Bit machine: As you can see its a simple 3 liner cfg file that needs to be created\copied in the corresponding folder to force your desired configuration.
What I do is use Group Policy Preferences to copy a file from the network (I have saved to the GPO source location eg.
\Domain.local\DFS\Install\Adobe Flash\mms.cfg) to the client destination. Note: I have attached a sample file which is included in the package at the bottom of this article.
There are several sections that we need to individually configure to get it all to work, and at the end they should all work together to give us the end result of auto-updating clients in the enterprise.
Deploying the client in the enterprise is relatively straight forward and I have covered it in the a previous article:| Adobe provide specifications for an configuration file that configures Adobe Flash player.
This part is required for any organisation who want to overcome the following scenarios: What we will have at the end of this is an internal web server which hosts the files for your clients to access, a DNS entry with a common name to access the files, and a scheduled task which runs a script to download the latest files every day (directly from the Adobe download site).
This configuration can be hard coded on a client using
The problem with this method is that if its a laptop that may connect to wifi outside the business, some internet access (where the system account is used) may not work.
Invoke, threading within the called class and nothing seems, to work.
The best solution so far is an Extension method which calls the invoke of the control.