Locked

Setup of Background Flash updates from an internal server

New Here ,
Aug 24, 2017 Aug 24, 2017

Copy link to clipboard

Copied

We are setting to receive flash background updates from an internal server for our 1200+ enterprise pcs.

We created the server with the open port 443 for HTTPS requests and a SSL certificate for HTTPS access on port 443.   However, we are not seeing in the Flash 26 admin guide instructions on creating an application or service that calls out and stores the updates.  We only see the mms.cfg file change (which is not enough). 

What are we supposed to install on the server that looks for the updates and downloads the files?   Do we need to create an IIS server?

Thanks.

TOPICS
Download install

Views

1.2K

Likes

translate

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 ,
Aug 24, 2017 Aug 24, 2017

Copy link to clipboard

Copied

Hi,

Please follow the instructions mentioned on page 21 to configure the server mentioned in the Admin guide.

Thanks!

Likes

translate

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
New Here ,
Aug 28, 2017 Aug 28, 2017

Copy link to clipboard

Copied

To confirm, we have to install the IIS role on the windows server, correct?  If so I am not seeing that as a prereq on page 21.

Likes

translate

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 ,
Aug 28, 2017 Aug 28, 2017

Copy link to clipboard

Copied

Hi,

There is no such requirement that it should be an IIS server. You could even use Apache server for the same.

Thanks!

Likes

translate

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
New Here ,
Aug 30, 2017 Aug 30, 2017

Copy link to clipboard

Copied

Ridhijain,

I followed the instructions on page 21.

Port 80/443 is allowed.

We can store files.

MMS Configure

Downloaded the Background update resource

Exported to the assigned directories after creation.

I installed 26.0.0.131 on the test workstations

set the Mms.cfg to point to the server.

Kicked off the task schedule on the local workstaiton to start the update process.

Not updating.

Please advise.

Thanks!

Likes

translate

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
Community Beginner ,
Aug 31, 2017 Aug 31, 2017

Copy link to clipboard

Copied

Do you have activated verboselogging at mms.cfg?

If not, please add the following Line to mms.cfg:

SilentAutoUpdateVerboseLogging=1

(0 = false, 1 = true)

Could you post the content of the Log?

The Log-Files are located at:

32Bit: C:\Windows\System32\Macromed\Flash

64Bit: C:\Windows\SysWow64\Macromed\Flash

Before updating again about the FlashPlayerUpdateService.exe you should delete the Registry Entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayerSAU\LastUpdateCheck

I have an identical Issue, but from Adobe i get no Details about the Error Codes:

2017-8-29+13-38-45.795 [info] 1629 server.company.local:8084

2017-8-29+13-38-45.795 [info] 1614

2017-8-29+13-38-45.811 [info] 1615

2017-8-29+13-38-45.811 [info] 1618

2017-8-29+13-38-45.827 [info] 1619 1063

2017-8-29+13-38-45.857 [info] 1629 server.company.local:8084

2017-8-29+13-38-45.857 [info] 1614

2017-8-29+13-38-45.872 [info] 1615

2017-8-29+13-38-45.872 [info] 1618

2017-8-29+13-38-45.890 [info] 1604

2017-8-29+13-38-45.890 [info] 1608

2017-8-29+13-38-45.905 [info] 1631 /pub/flashplayer/update/current/sau/currentmajor.xml

2017-8-29+13-38-45.905 [warning] 1468 183

2017-8-29+13-38-45.921 [warning] 1469 183

2017-8-29+13-38-45.921 [warning] 1470 183

2017-8-29+13-38-45.936 [warning] 1474 183

2017-8-29+13-38-45.936 [warning] 1475

2017-8-29+13-38-45.952 [info] 1432

2017-8-29+13-38-45.952 [info] 1612

2017-8-29+13-38-45.968 [info] 1620

Likes

translate

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
New Here ,
Aug 31, 2017 Aug 31, 2017

Copy link to clipboard

Copied

Current mms.cfg

AutoUpdateDisable=0
SilentAutoUpdateEnable=1
SilentAutoUpdateServerDomain=servername.domain.com
SilentAutoUpdateVerboseLogging=1

2017-8-31+17-16-1.172 [info] 1614
2017-8-31+17-16-1.204 [info] 1615
2017-8-31+17-16-1.219 [info] 1618
2017-8-31+17-16-1.235 [info] 1604
2017-8-31+17-16-1.235 [info] 1608
2017-8-31+17-16-1.250 [info] 1612
2017-8-31+17-16-1.266 [info] 1620
2017-8-31+18-16-0.85 [info] 1629 servername.domain.com
2017-8-31+18-16-0.101 [info] 1614
2017-8-31+18-16-0.132 [info] 1615
2017-8-31+18-16-0.148 [info] 1618
2017-8-31+18-16-0.163 [info] 1619 1063
2017-8-31+18-16-0.210 [info] 1629 servername.domain.com
2017-8-31+18-16-0.226 [info] 1614
2017-8-31+18-16-0.242 [info] 1615
2017-8-31+18-16-0.273 [info] 1618
2017-8-31+18-16-0.288 [info] 1608
2017-8-31+18-16-0.288 [info] 1604
2017-8-31+18-16-0.304 [info] 1612
2017-8-31+18-16-0.320 [info] 1620
2017-8-31+19-16-0.76 [info] 1629 servername.domain.com
2017-8-31+19-16-0.92 [info] 1614
2017-8-31+19-16-0.107 [info] 1615
2017-8-31+19-16-0.138 [info] 1618
2017-8-31+19-16-0.138 [info] 1619 1063
2017-8-31+19-16-0.201 [info] 1629 servername.domain.com
2017-8-31+19-16-0.217 [info] 1614
2017-8-31+19-16-0.232 [info] 1615
2017-8-31+19-16-0.248 [info] 1618
2017-8-31+19-16-0.263 [info] 1604
2017-8-31+19-16-0.263 [info] 1608
2017-8-31+19-16-0.279 [info] 1612
2017-8-31+19-16-0.295 [info] 1620

Likes

translate

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 ,
Aug 31, 2017 Aug 31, 2017

Copy link to clipboard

Copied

Hi coreyh59418516​,

What is the structure hierarchy for the background update resources on your machine? As per the logs, none of the xmls files have been hit.

Thanks!

Likes

translate

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
New Here ,
Sep 01, 2017 Sep 01, 2017

Copy link to clipboard

Copied

C:\inetpub\wwwroot\pub\flashplayer\update\current\sau\26

"C:\inetpub\wwwroot\pub\flashplayer\update\current\sau\26\xml\version.xml"

"C:\inetpub\wwwroot\pub\flashplayer\update\current\sau\26\install\install_all_win_ax_sgn.z"

"C:\inetpub\wwwroot\pub\flashplayer\update\current\sau\26\install\install_all_win_pep_sgn.z"

"C:\inetpub\wwwroot\pub\flashplayer\update\current\sau\26\install\install_all_win_pl_sgn.z"

"C:\inetpub\wwwroot\pub\flashplayer\update\current\sau\currentmajor.xml"

Likes

translate

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
New Here ,
Sep 05, 2017 Sep 05, 2017

Copy link to clipboard

Copied

Anything on this?

Likes

translate

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 ,
Sep 05, 2017 Sep 05, 2017

Copy link to clipboard

Copied

Hicoreyh59418516

I am not seeing any errors in the log file excerpt you posted. Please do the following:

  • Install previous version of Flash (e.g. 26.0.0.137 or older)
  • Delete the registry entry at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayerSAU\LastUpdateCheck and run the SAU service again.
  • If the update doesn't install, upload the FlashInstall32.log file saved at C:\Windows\System32\Macromed\Flash directory to cloud.acrobat.com/send using the instructions at How to share a document and post the link to the uploaded file in your reply.  If this is a 64-bit OS, the FlashInstall64.log file saved at C:\Windows\SysWOW64\Macromed\Flash directory is also required.

--

Maria

Likes

translate

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
New Here ,
Sep 05, 2017 Sep 05, 2017

Copy link to clipboard

Copied

Likes

translate

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
New Here ,
Sep 05, 2017 Sep 05, 2017

Copy link to clipboard

Copied

It's a 64-bit system.  But I took all of the install logs and uploaded for you to review.  I'm seeing errors now.

Likes

translate

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
New Here ,
Sep 05, 2017 Sep 05, 2017

Copy link to clipboard

Copied

Likes

translate

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 ,
Sep 06, 2017 Sep 06, 2017

Copy link to clipboard

Copied

Hi,

If the files are posted, but you're getting error 404 then your server is not configured correctly and you'll need to troubleshoot why.  I found the following article on support.microsoft.com which may be of assistance https://support.microsoft.com/en-us/help/248033/how-system-administrators-can-troubleshoot-an-http-4...

--

Maria

Likes

translate

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
New Here ,
Sep 07, 2017 Sep 07, 2017

Copy link to clipboard

Copied

In this case on IIS within Windows 2016, the site binding for https needed to be listing the hostname, port 443, and asterisk (*) for the IP.

Next on the pub, install, and xml virtual directories, they need to be coverted into an application.

All directories will if viewed through a browser will return a 400 type error because there is not landing page.  I tested by placing a test.aspx within each directory to confirm it is accessible from a browser.  They were accessible.

Running the task schedule originally did not work.  I had to then delete the reg key LastUpdateCheck again on the local workstation, reran the task schedule and it worked.

Maria, Do you have instructions for automatically downloading the background update resources automatically, and distributing them automatically to the premade directories on the IIS server to make this a truly seamless process?

Likes

translate

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
New Here ,
Sep 07, 2017 Sep 07, 2017

Copy link to clipboard

Copied

To add:  The NPAPI does not immediately come down.  There either is a delay, or you have to rerun the task schedule a second time.  Maria,  Is this normal behavior?

Likes

translate

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
New Here ,
Sep 08, 2017 Sep 08, 2017

Copy link to clipboard

Copied

Maria,

We appreciate your timely response.

We have reports that the NPAPI is not responding to the upgrade request at all, while the active x resolves without issue after removing the LastUpdateCheck key.  There were hourly automated requests from the updater since the Active x came down yesterday afternoon.  Let it go through the night, return in the morning. Still no NPAPI.

This begs two questions:

  1. Why do we even have to go into the registry to "fix" the updater of the program?
  2. How do we repair the NPAPI?

Logs enclosed.

Shared Files - Acrobat.com

Likes

translate

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 ,
Sep 08, 2017 Sep 08, 2017

Copy link to clipboard

Copied

Why do we even have to go into the registry to "fix" the updater of the program?

Under normal operation you don't.  This is for testing purposes only to force the update (and isn't always required)

The NPAPI does not immediately come down.  There either is a delay, or you have to rerun the task schedule a second time.  Maria,  Is this normal behavior?

This is normal behaviour.  When Background Updates executes it updates the Player types in the following order, one at a time:

ActiveX

NPAPI

PPAPI

If ActiveX and NPAPI are both installed, the first time Background Updates runs it'll update ActiveX. The next time it runs (in 1 hour), it'll update NPAPI.  If PPAPI is also installed, the next time it runs (in 1 hour), it'll update the PPAPI plugin.  If ActiveX is not installed, it skips that and goes to the next installed plugin, in the order above.

In the most resent log file you sent, the NPAPI plugin is not installed.  The standalone uninstaller (uninstall_flash_player.exe) was executed, which uninstalls ALL Flash Player types (E.g. ActiveX, NPAPI, PPAPI) installed on the system. Then ActiveX Control 26.0.0.131 was installed using the MSI.  Then Background Updates was executed and the ActiveX Control was updated to 26.0.0.151. Since only ActiveX Control is installed and it's the latest version, there is nothing to update to.

Likes

translate

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
New Here ,
Sep 08, 2017 Sep 08, 2017

Copy link to clipboard

Copied

No. The steps taken were as follows.

Uninstall ActiveX/NPAPI 151 manually.  However ActiveX had errors uninstalling.

I used the uninstall tool.

I was then able to install 131 both activex/npapi.

I then ran the updater from task schedule

Nothing happened.

I deleted the reg key.

It brought down activex, not npapi.

I then had it sit overnight.

No Npapi in the morning.

Likes

translate

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 ,
Sep 11, 2017 Sep 11, 2017

Copy link to clipboard

Copied

I was then able to install 131 both activex/npapi.

Looking at the FlashInstall32 (1).log file from the bottom:

  • lines 21924 - 22008 log the uninstallation using the standalone uninstaller.  Line 21927 has:

0002 00000010 "\\phxutil\sources\Adobe\Flash\UninstallTool\uninstall_flash_player.exe" -force  This removes all Flash Player instances from the system.

    • This is the standalone uninstaller, removing the ActiveX Control and the NPAPI plugin.
  • Lines 22010 - 22028 are the ActiveX Control installation using the MSI installer.
  • Lines 22030 - 22053 are Background Update logging.
  • Lines 22054 - 22090 show the installed ActiveX Control version (26.0.0.131) is being uninstalled
  • Lines 22092 - 22108 show the ActiveX Control being updated to 26.0.0.151 via Background Update
  • Lines 22110 - 22319 are all Background Update logging.
    • Background Update Task wakes up, checks to see if it's time to ping the server for an update.
      • If it's not, it goes back to sleep.
      • If it is, it checks the server and doesn't find an update, so goes back to sleep.
    • Since only ActiveX Control is installed, and the most recent version is installed, there is nothing to update.

I'm not concerned with entries prior to line 21924 because whatever was installed prior to line 21924 was uninstalled when the standalone uninstaller was executed, which uninstalled ALL Flash Player types (ActiveX and NPAPI) that were installed on the system.

Likes

translate

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
New Here ,
Sep 12, 2017 Sep 12, 2017

Copy link to clipboard

Copied

9/11/17 - afternoon

  • Re-performed the steps again.
  • Uninstall of 26.0.0.151 active-x/npapi
  • Attempted install of 26.0.0.137 active-x.  Failed
  • Ran uninstaller.
  • Successful.
  • Reinstall active-x -success .137
  • Reinstall NPAPI - success .137

  • Placed updated mms.cfg to C:\Windows\SysWOW64\Macromed\Flash

  • Allowed Task Schedule to continue on with hourly updates.
  • No auto updates took place overnight.

Shared Files - Acrobat.com

Likes

translate

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
New Here ,
Sep 12, 2017 Sep 12, 2017

Copy link to clipboard

Copied

  • ***Deleted HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayerSAU\LastUpdateCheck
  • Forced update through task scheduler
    • Active-X only came down
  • To mimic hourly behavior based on your statement of order forced another task schedule:
        • When Background Updates executes it updates the Player types in the following order, one at a time:

        • ActiveX

        • NPAPI

        • PPAPI

  • NPAPI comes down.

Summary:  Will not update without deleting the LastUpdateCheck reg key.  Why?

Shared Files - Acrobat.com

Likes

translate

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 ,
Sep 12, 2017 Sep 12, 2017

Copy link to clipboard

Copied

We're investigating this further.  I most likely won't have an update until tomorrow.


Also, there's a new version of Flash Player, 27.0.0.130, released earlier today.

Likes

translate

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 ,
Sep 13, 2017 Sep 13, 2017

Copy link to clipboard

Copied

Unfortunately, I am not able to reproduce the behaviour you are observing.  Both the ActiveX Control and NPAPI plugin are being updated as expected.

I did notice you have a typo in the mms.cfg file, but it doesn’t impact Background Update behaiour. You have SAutoUpdateDisable=0.  This should be AutoUpdateDisable=0 (no S).

I performed the following:

  • Run Flash Player uninstaller to uninstall Flash Player that may be installed on the system.
  • Deploy 26.0.0.151 Background Update resources to a test server (this is the version you are hosting on your internal server).
  • Install 26.0.0.137 ActiveX Control and NPAPI plugin (same version and install vector you are using).
  • Configure mms.cfg file the same as you have in your screenshot posted earlier today
  • Force Background Updates by running the Task in Task Scheduler
  • In Task Scheduler, refresh the Adobe Flash Player Updater task and verify the Last Run Time
    • It has been updated, indicating the Task ran
  • Wait a few minutes and view contents of the C:\Windows\SysWOW64\Macromed\Flash directory
  • Verify ActiveX Control was updated from 26.0.0.131 > 26.0.0.151 – it was
  • Launch RegEdit and view the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayerSAU\LastUpdateCheck registry entry
    • Data field is 0x00000000 (0) as expected, indicating Background Update ran and installed an update
  • Go back to Task Scheduler, select Adobe Flash Player Updater task and run it
  • Refresh the Adobe Flash Player Updater task and verify the Last Run time
    • It has been updated, indicating the Task ran
  • Wait a few minutes and view the contents of C:\Windows\SysWOW64\Macromed\Flash directory
  • Verify NPAPI plugin was updated from 26.0.0.131 > 26.0.0.151 – it was
  • Go to RegEdit and Refresh it (View > Refresh)
  • View the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayerSAU\LastUpdateCheck registry entry
    • Data field is 0x00000000 (0) as expected, indicating Background Update ran and installed an update
  • Go back to Task Scheduler, select Adobe Flash Player Updater task and run it
  • Refresh the Adobe Flash Player Updater task and verify the Last Run time
    • It has been updated, indicating the Task ran
  • Go to RegEdit and Refresh it (View > Refresh)
  • View the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayerSAU\LastUpdateCheck registry entry
    • Data field has an alphanumeric entry.  This indicates Background Updates ran, did not find an update and populated the field with the time it ran. 

This is the behavior you should be observing in your system.  Please follow the above steps, exactly as I have, but fix the typo in the AutoUpdateDIsable=1 entry in the mms.cfg file (again, this typo has no impact on the functionality, but you should correct it).  I expect the results to be the same.  If not, provide new FlashInstall log files.

Thank you.

Likes

translate

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