Skip to main content
Participant
February 19, 2018
Question

Local storage settings

  • February 19, 2018
  • 1 reply
  • 1247 views

Hi,

I am hoping this is a simple one.  The following link details how to change the local storage settings in flash from the default 100kb to which ever option suits best.  Adobe - Flash Player : Help - Local Storage Settings.

I just wanted to know if you were to change the setting, ie: to 1mb, where does it write this value to?  I ask because we are looking to use group policy to manage this value for particular workers/departments and if it's just a registry tweak or amendment to a file then we can centrally manage this.

I have looked at the forums and have not found anyone with a similar query.

Thanks

B​

This topic has been closed for replies.

1 reply

jeromiec83223024
Inspiring
February 20, 2018

You can set this via mms.cfg. 

See the LocalStorageLimit directive on pp.38 of the system administrator's guide, here:

Adobe Flash Player Administration Guide for Flash Player | Adobe Developer Connection

Participant
March 8, 2018

Apologies for the late delay, I thought I would get an email notification if there was a response.

I can see two copies of the mms.cfg on my Windows 7 machine, and they reside in:

C:\Windows\SysWOW64\Macromed\Flash

C:\Windows\System32\Macromed\Flash

I tried amending them in turn, and then both at the same time with the following addition:

AssetCacheSize=1

I also tried different value's to 1 (5,10 etc) but whenever opening the browser and checking Adobe - Flash Player : Settings Manager - Global Storage Settings Panel  the default of 100kb is still there.

If I manually change the default via the web console I cannot see it writing back to the mms.cfg either.

Have I missed something obvious?

Thanks

jeromiec83223024
Inspiring
March 8, 2018

In general, you won't see mms.cfg directives reflected in the UI.  My guess is that if you wrote a little test that attempted to write an LSO that met or exceeded the defined size, you'd be able to confirm that it was behaving as expected.

Similarly, if you disabled camera/mic access via an administrative mms.cfg directive, users would be able to play with the UI, but the directive would override anything they set.


It's not ideal, but modifying the UI is problematic.