How to use mms.cfg file after Dec 2020

[lalajeehai]

Hi,

I created a mms.cfg file with all of the option but when I visit a site which has swf movie its still blocking it.

File Name: MMS.cfg

Format: UTF-8

File Data:

EOLUninstallDisable=1

AutoUpdateDisable=1

EnableAllowList=1

AllowListURLPattern=*:*

How can i test to see my mms.cfg file is working or not.

I'm only doing this on Windows 10 1809/1909 Mahicnes

[lalajeehai]

File is saved in

C:\Windows\System32\Macromed\Flash

C:\Windows\SysWOW64\Macromed\Flash

[alexander5FDA]

we found that after restart file in C:\Windows\SysWOW64\Macromed\Flash get overwritten and browser (IE11) stopped working again. but it is possible that some other Enterprise update doing it.

So if you see the same issue - double check that files are updated correctly

[Test Screen Name]

Well, all browsers will be blocking it, I'm not sure what good whitelisting would do...

[lalajeehai]

it will be blocked but if you allow it through mms.cfg file then these site should not be blocked

[lalajeehai]

Also you have a choose the remove from your browser or leave it. For some user we need to have flash player enable and working, in IE or edge Windows 10

[Alexei5D13]

FireFOX ESR does not block it. Then, you can easily disable browser updates.

IT is for enterprises, so enterprise versions allows it, as we need AdobeFlash to work for at least next 10 years. Too many management systems uses it (Vmware VDP for example, VC 6.5, some hardware).

Tested today - it works. * did not work in whitelist but exact URL-s are recognized.

[#8]

What is the location for mms.cfg with FF ESR on Win 10 64-bit? Adobe's documentation doesnt' reference FF.

Thnx!

[Alexei5D13]

Location for FF is the same

C:\Windows\System32\Macromed\Flash

C:\Windows\SysWOW64\Macromed\Flash

[alexander5FDA]

New EDGE version will not work even with mms.cfg file updated. only IE11 and old EDGE

[jeromiec83223024]

AllowListURLPattern=*:* is not valid.  There's no "allow everything" setting.  The intent of this feature is to allow Enterprises with business-critical internal applications that are dependent on Flash to allow those specific applications in their managed environments.  This is not a mechanism to allow end-users to continue using Flash Player.

[jeromiec83223024 · Accepted solution]

Also, the documentation for these features is in the "Enterprise Enablement" section of the Admin guide, here:

https://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_guide.html

There are a couple documentation bugs that we're in the process of getting corrected and published.  You can't allow all ports, and you can't allow all domains.  You have to specify at least *.<something>.<something>  (e.g.*.adobe.com, etc).