Locked

ProductDisabled list of applications for mms.cfg

New Here ,
Apr 26, 2019 Apr 26, 2019

Copy link to clipboard

Copied

I am in the process of creating an mms.cfg file to push out to our clients.

Per the administrator guide in Chapter 4 page 50-51:

I have set DisabledProductDownload=1

But the value(s) I need for ProductDisabled is unknown.

Does Adobe have a list of the applications?

Some of our remote works have to install updates on their own systems and if they install McAfee it messes with our AV and causes Windows Updates to become corrupt. This is a real issue for us and the mms.cfg will fix it if Adobe has a list of the application name(s) some place that we need to put in this list.

TOPICS
Download install

Views

175

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 26, 2019 Apr 26, 2019

Copy link to clipboard

Copied

LATEST

Some of our remote works have to install updates on their own systems and if they install McAfee it messes with our AV and causes Windows Updates to become corrupt. This is a real issue for us and the mms.cfg will fix it if Adobe has a list of the application name(s) some place that we need to put in this list.

You're misunderstanding the purpose of the DisableProductDownload directive.  It's not for third party products (such as McAfee) but for Adobe products.  The Admin Guide states "Adobe uses this capability to deliver Flash Player updates through developer initiated Express Install process, and to deliver the Adobe Acrobat Connect screen-sharing functionality."  Having DisableProductDownload=1 disables the download of these products.

Also, you have a typo in the directive.  It is DisableProductDownload, not DisabledProductDownload, however, since this doesn't accomplish what you're attempting to do, it's not relevant and not necessary.

If the goal is to prevent the remote users from accidentally installing McAfee, hosting the Background Updates locally and having Flash Player update via your locally hosted resources would be the best solution.  See the section 'Performing a background update' in Chapter 3 page 32 for more information.

Alternatively, you can use  Adobe's servers for the Background Updates, however, if Background Update installation fails after 7 attempts, Flash Player falls back to Notification Updates which would introduce the possibility accidentally installing McAfee.

Background Updates occurs completely silently in the background without user interaction, as long as an internet connection is present, and updates all Flash Player types (non-embedded ActiveX, NPAPI, and non-embedded PPAPI) within 24 hours of a new version being available.

To opt into background Updates, add the following to the mms.cfg file:

AutoUpdateDisable-0

SilentAutoUpdateEnable=1

If you're hosting the resources locally, also add the following, after deploying the resources locally:

SilentAutoUpdateServerDomain= your.server.com

Note that to distribute Flash Player in this manner requires a Flash Player distribution license (free for the vast majority of uses cases) as indicated in the Admin Guide.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines