Hi Guys,
Has anyone else come across this issue. I am coming up with a corporate deployment of Flash and have downloaded the MSI which Macromedia supply (theactive xone)and according to the security document have created an MMS.cfg file with the following two lines in :- AutoUpdateDisable=[1]
The idea being to diss-able autoupdate and ensure that users cannot change this. I put the MMS.cfg file down C:\WINDOWS\system32\Macromed\Flash on our Windows XP machines but every time I log in to flash settings it shows autoupdate as on ?

I am obviously doing something wrong but for some reason it does not seem to be reading the MMS.cfg file ? Does anyone know why and if I am missing something simple.

Whenever I go into the Flash site and check my settings it says download updates and i can change the options ?

I have looked on Appdeploy.com and although they have some stuff seeming to indicate the creation of this mms.cfg file is the way to go it don't work ?

Any help much appreciated, many thanks,
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


the only files you need for flash 8 to work in flash8.ocx and the Downloaded Program Files inf files once your register the ocx you are fine. i thin the getflash files is the problem
Answered 11/22/2005 by: linstead
Blue Belt

Please log in to comment
have you typed it as "AutoUpdateDisable=[1]" with the brackets? or is that just my imagination?.. [8D]

Answered 11/22/2005 by: rikx2
Purple Belt

Please log in to comment
It is not your imagination I had LOL
However it is not the issue as it still shows as autoupdate settings on the control web page for Flash with the =1 etc.

However I did go into the .sol file that sits down docs and settings app data macromedia etc and when that is read in it says AutoUpdate disabled ?

Therefore I think the control panel for Flash is showing faulty readings ?

To be on the safe side I have deleted GetFlash.exe as well....Only way to be safe !
Answered 11/24/2005 by: Tocra
Senior Yellow Belt

Please log in to comment
Yeah i had the same problem, set the mms file proper syntax and location.
Chk settings and its doesnt show up the changes. Maybe the settings it displays are derived from the local user settings and not the global settings that the mms file manipulates.
Maybe an email to Macromedia might help finally solve this one.
Answered 11/24/2005 by: rahvintzu
Orange Senior Belt

Please log in to comment
According to Macromedia, (http://livedocs.macromedia.com/flex/15/flex_docs_en/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Flex_Documentation&file=00000941.htm), there is no bracket with the value pair. Also, I did not find AutoUpdateLock listed as supported.
Answered 11/29/2005 by: Rick.Tuttle
Senior Yellow Belt

Please log in to comment
This post is old, but as a newbie to packaging I've been put to the task of creating a few small little packages. One is Flash Player (FP)! In my testing I confirmed the mms.cfg file does work. Here's what I did:

I installed an older version of FP (located at http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_14266) on a clean XP system and then created a mms.cfg file with the following info and saved it into C:\WINDOWS\SYSTEM32 (Seeing it was a v7.x player):


This basically allows the Autoupdate to run and then looks for an update once the player is loaded (in a web browser) within 1 millisecond. I would then open www.msn.com (because there was a Flash graphic on their mainpage) and I would see the SysTray Flash Player update balloon. Thats great, I know the autoupdate works. I then would re-open mms.cfg and change to just contain the following:


I would then open the www.msn.com web page again and notice there would be no balloon or update prompt! Cool! Just for kicks I went back to the mms.cfg and reverted back the settings, saved the file and then re-opened the msn.com page...there would be the prompt again!

As you could probably tell, I'm a noob but I think this proves that the mms.cfg file works as stated by Macromedia.

To get things up to the latest version, I ran the uninstall_flash_player.exe file (downloaded from http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_14157) for the v7.x version and then installed the latest version (which is in MSI format) file for v8.22.0. I then take that same mms.cfg file with just the AutoUpdateDisable=1 line in it and move it to C:\WINDOWS\SYSTEM32\MACROMED\FLASH directory for the new v8.0.22.0 Flash Player. Seeing there's no new update available, that's all the testing I can do at this point.

Hope this helps someone in case they are looking for some answers when testing the MMS.CFG file.
Answered 01/17/2006 by: benducklow
Senior Yellow Belt

Please log in to comment
Hi Guys!
It's an old thread but I try to put my post here.

What about the license agreement from Macromedia? If you use the MSI-file from Macromedia the license says
"Can I repackage the Macromedia Player installers or create my own?
The Agreement does not allow for modifying or re-packaging the installers that are provided via the Free Licensing Agreement in any way. If you would like information about a custom agreement, please fill out the Contact Request form to speak more with someone at Macromedia about your needs. Macromedia offers the License Agreement as-is and enters into custom agreements on an extremely limited basis."


That means that you're not allowed to do any modifications? Or doesn't that include modifications with the mms.cfg?
// Jörgen
Answered 02/07/2006 by: everts
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity