MMS.cfg file is not pick up by Google Chrome

[lalajeehai]

Hi,

I have MMS.cfg file which is working fine for IE 11 but Google Chrome is not picking the same file.

How can I make the chrome to work with same file?

Do I need to copy the file in to different location for chrome

[_maria_]

Google Chrome uses its own version of the mms.cfg file, saved at:

• Mac: /Users/<username>/Library/Application Support/Google/Chrome/Default/Pepper Data/Shockwave Flash/System
• Win: %USERNAME%/AppData/Local/Google/Chrome/User Data/Default/Pepper Data/Shockwave Flash/System

For more information on the mms.cfg file, see the Flash Player Admin Guide

[Randall5CDC]

So after Jan 12th / Chrome version 88 that removes flash, where do we need to maintain the mss.cfg file so that Flash will continue to function?

[_maria_]

I'm confused - Flash won't function on Chrome once Google removes support for it.

[lalajeehai]

We are trying to do PPAPI plugin install to make the flash work for little bit longer to upgraded all our system

[lalajeehai]

We only need a flash to work on the internal site.

We are slowly moving to alternat but it's a very slow process for us

[jeromiec83223024 · Accepted solution]

At the point that Chrome removes support for plug-ins, there's no infrastructure in the browser to allow Flash to run.

We'd strongly recommend talking to HARMAN about licensing a secure, maintained solution.

Running Flash Player in Chrome after EOL will quickly require running an outdated version of Chrome, which is really not a great solution.

See our Enteprise EOL FAQ for more: 

https://www.adobe.com/products/flashplayer/enterprise-end-of-life.html

[jeromiec83223024]

Also, managing mms.cfg is pretty ugly in the context of Chrome.  Chrome effectively runs Flash Player in something like a chroot jail.  Flash Player thinks it's running in the default system location, but it's running in a folder that's isolated from the system, and is specific to the active Chrome profile.  This ensures that data can't leak between multiple Chrome profiles running on the same Chrome instance, but it makes administering Flash Player super painful. 

On Chrome, the first Profile is called "Default".  Subsequent profiles are enumerated "Profile 1", "Profile 2", "...", etc: 

• Mac: /Users/<username>/Library/Application Support/Google/Chrome/Default/Pepper Data/Shockwave Flash/System
• Win: %USERNAME%/AppData/Local/Google/Chrome/User Data/Default/Pepper Data/Shockwave Flash/System

If you're going to comprehensively deploy mms.cfg to your network for all users and all user profiles on a system, you're going to need to write a script that detects all of the Chrome installations and applies mms.cfg to all of those places.