Skip navigation
HansBrockstedt 4 posts
Apr 4, 2012
Currently Being Moderated

Flash player silent auto update not working

Apr 4, 2012 1:03 AM

I was glad to read the news about the new feature of silent auto updates of the Adobe Flash player, but unfortunately this is not working on my machine. Has anyone had the same problems and was able to solve them?

 

Some information on my setup:

 

I had previously installed Flash player version 11.1.102.63, both ActiveX and Plugin version (installed through the .msi files, deployed via Active Directory/GPO - no further configuration, just plain original .msi files).

 

To test the auto update feature, I decided to install the new 11.2.202.228 version, but only the ActiveX version. I installed this via the .exe installer (install_flash_player_11_active_x_32bit.exe) manually, choosing "Install updates automatically when available (recommended)" in the last step of the installation, as seen here:

http://www.adobe.com/devnet/flashplayer/articles/background-updater-wi ndows.html

 

When I open Control Panel -> Flash Player, under the "Advanced" tab I see:

  • "Install updates automatically" is chosen, but greyed out (no admin rights with this windows user)
  • ActiveX version: 11.2.202.228
  • Plug-In version: 11.1.102.63

 

The file "mms.cfg" under C:\WINDOWS\system32\Macromed\Flash\ contains:

AutoUpdateDisable=0

SilentAutoUpdateEnable=1

 

The task "Adobe Flash Player Updater" was created and is scheduled to run every 1 hour. I can see that it is started ("last start time"), the result code is 0x0 which means "no error".

 

So everything as expected. But the auto update is not working, since the plugin version of flash player never gets updated!

 

I edited the "mms.cfg" and added:

SilentAutoUpdateVerboseLogging=1

 

After manually starting the task, there are some lines added to "FlashInstall.log" in the same directory:

2012-4-4+7-20-48.814 [info] 1614

2012-4-4+7-20-48.829 [info] 1615

2012-4-4+7-20-48.829 [info] 1618

2012-4-4+7-20-48.829 [info] 1619 1063

2012-4-4+7-20-48.876 [info] 1614

2012-4-4+7-20-48.876 [info] 1615

2012-4-4+7-20-48.876 [info] 1618

2012-4-4+7-20-48.876 [info] 1608

2012-4-4+7-20-48.876 [info] 1604

2012-4-4+7-21-10.425 [warning] 1403 12029

2012-4-4+7-21-10.425 [warning] 1407 183

2012-4-4+7-21-10.425 [warning] 1408

2012-4-4+7-21-10.456 [info] 1624

2012-4-4+7-21-10.456 [info] 1612

2012-4-4+7-21-10.456 [info] 1621

 

What does this mean?

 

 

Some more information:

  • Windows XP SP3, all windows updates installed, german
  • Avira Professional Security anti-virus software
  • Machine is behind a proxy server, but this is set up in Control Panel -> Internet Options

 

 

I suppose this is a problem with our proxy server. Does the auto updater not use the proxy information from the Windows Control Panel settings?

 

Kind Regards,

Martin

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Apr 18, 2012 9:42 AM   in reply to HansBrockstedt

    I'm in the same boat, though my log looks a little different:

     

    2012-4-18+14-26-5.844 [info] 1613

    2012-4-18+14-26-5.869 [info] 1615

    2012-4-18+14-26-5.871 [info] 1618

    2012-4-18+14-26-5.873 [info] 1619 1063

    2012-4-18+14-26-5.882 [info] 1613

    2012-4-18+14-26-5.882 [info] 1615

    2012-4-18+14-26-5.882 [info] 1618

    2012-4-18+14-26-5.884 [info] 1608

    2012-4-18+14-26-5.884 [info] 1604

    2012-4-18+14-26-8.412 [info] 1626

    2012-4-18+14-26-8.510 [info] 1612

    2012-4-18+14-26-8.511 [info] 1621

    2012-4-18+14-26-8.511 [info] 1620

    (begin repeat 1 hour later)

    2012-4-18+15-26-0.146 [info] 1613

    2012-4-18+15-26-0.148 [info] 1615

    2012-4-18+15-26-0.149 [info] 1618

    2012-4-18+15-26-0.151 [info] 1619 1063

    2012-4-18+15-26-0.160 [info] 1613

    2012-4-18+15-26-0.160 [info] 1615

    2012-4-18+15-26-0.160 [info] 1618

    2012-4-18+15-26-0.162 [info] 1608

    2012-4-18+15-26-0.162 [info] 1604

    2012-4-18+15-26-1.329 [info] 1626

    2012-4-18+15-26-1.329 [info] 1612

    2012-4-18+15-26-1.330 [info] 1621

    2012-4-18+15-26-1.330 [info] 1620

     

    Would really like an answer from Adobe as to whether the background auto-updater will use system proxy settings.

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Apr 18, 2012 11:33 AM   in reply to spence2326

    The silent update service uses the SYSTEM user account when running, so this might be causing issues with your proxy service.  We're currently considering adding the ability to host these updates on corporate networks and allowing administrators to redirect the updater to an internal server.

     

    Another possibility, though unsupported and untested, would be to try to change the user account used by the service to a user that has proper proxy authentication.

     

    I'd like to recommend opening a new bug/feature report on proxy support for the silent auto updater over at bugbase.adobe.com.  Please post back with the bug number so that others interested in this can cast their vote and add comments.

     

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 18, 2012 12:30 PM   in reply to Chris Campbell

    Thanks for the response, Chris.

     

    Just FYI: I tried your suggestion of running the Adobe Flash Player Update Service as a user account that is authorized on our proxy, but I still got the same results in FlashInstall.log:

     

    2012-4-18+19-26-0.444 [info] 1613

    2012-4-18+19-26-0.507 [info] 1615

    2012-4-18+19-26-0.507 [info] 1618

    2012-4-18+19-26-0.507 [info] 1619 1063

    2012-4-18+19-26-1.443 [info] 1613

    2012-4-18+19-26-1.443 [info] 1615

    2012-4-18+19-26-1.443 [info] 1618

    2012-4-18+19-26-1.458 [info] 1608

    2012-4-18+19-26-1.458 [info] 1604

    2012-4-18+19-26-2.597 [info] 1626

    2012-4-18+19-26-2.613 [info] 1612

    2012-4-18+19-26-2.613 [info] 1621

    2012-4-18+19-26-2.613 [info] 1620

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Apr 18, 2012 3:48 PM   in reply to spence2326

    Spence - Does the user that you used for the service have admin privileges? 

     

    No log entries are created after 1620, which means that the service was started. The service itself (now running under the new user) must not have been able to write to FlashInstall.log, which usually means that the account does not have admin privileges. This is required to run the Updater.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 19, 2012 5:29 AM   in reply to Chris Campbell

    Yes, the account running the service is a domain account that is a member of the local Administrators group on the machine.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 23, 2012 5:56 PM   in reply to HansBrockstedt

    I can confirm that the Flash Player Updater attempts to connect to the internet directly after doing some testing with netstat and wireshark.

    I have logged a feature requests for a proxy option to be created for the mms.cfg file. The feature request is #3173300 on bugbase.adobe.com


    The second issue I ran into was the Flash Player Updater doesn't support the ability to use a SSL self-signed certificate when using the SilentAutoUpdateServerDomain option and I have submitted feature request for this aswel #3173327 on bugbase.adobe.com

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Apr 25, 2012 2:53 PM   in reply to Tyrone Wyatt

    For those admins that would like to use the silent auto update service, but are behind a proxy server, you now have the capability to do background updates from an internal server using the SilentAutoUpdateServerDomain property.  Please see the section "Background updates from an internal server" in the Flash Player 11.2 Administration Guide for complete information.

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Apr 26, 2012 4:31 PM   in reply to HansBrockstedt

    Thanks Hans,

    I've forwarded this along to the developer who implemented this for his review.

     

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 26, 2012 11:34 PM   in reply to HansBrockstedt

    Hey Hans,

    After reading of your sucsess I attempted to replicate it.

     

    I am happy to say that I managed to update from Adobe Flash 11.2.202.228 to 11.2.202.233 on serveral different windows 7 notebooks and desktops sliently.

    I went into the windows task scedular and ran the Adobe Flash Player Updater task (I didn't need to change anything in the task or the service for it to work).

    The only issue I found was that if I ran the task again without restarting the computer no requests from the client would show up in the logs from my web server but if I restarted my computer and then reran the task it would work again. I'm assuming that it will only sent requests out every 24hours is talked about in page 18 of the Flash Player 11.2 Administration Guide

     

    My Web Servers logs look like this:

    2012-04-27 05:45:01 W3SVC1967680676 10.135.12.38 GET /pub/flashplayer/update/current/sau/11/xml/version.xml - 443 - 10.135.13.17 Get+Flash+Player+version+xml/1.0 200 0 0

    2012-04-27 05:45:05 W3SVC1967680676 10.135.12.38 GET /pub/flashplayer/update/current/sau/11/install/install_all_win_ax_sgn .z - 80 - 10.135.13.17 Download+Flash+Player+Installer/1.0 200 0 0

     

    My mms.cfg looks like this:

    AutoUpdateDisable=0

    SilentAutoUpdateEnable=1

    SilentAutoUpdateServerDomain=proxy.tallangatta-sc.vic.edu.au

     

    I think the biggest issue I had during testing was that I forgot to my web servers certificate into the windows certificate stores trusts root certs of my notebooks/desktops. EG: http://blogs.adobe.com/livecycle/2012/04/rights-management-how-to-get- windows-7-to-trust-a-self-signed-server-certificate.html

     

    I have since deployed the mms.cfg file and added my web servers certificate into the trusted root certs via group policy to all my clients and it is working very well. I have also writen a batch file to download the needed files from adobe for that backgroup updater and to put them on my web server. I created a daily task on my web server to run the batch file. If anyone wants the batch file or shell script please email me and I'll forward it on.

     

    My batch file pretty much looks like this:

    @echo off

     

    :::::::::: INFOMATION ABOUT SCRIPT ::::::::::

     

     

    :: This Script Titled  adobe-flash-background-updates and was written by Tyrone Wyatt of www.cloudportal.org.

    :: This Script is open to use by everyone and is not under any licence.

    :: See flash_player_11_2_admin_guide.pdf for more infomation on how this script is required to function.

     

     

    :::::::::: SCRIPT CONFIG ::::::::::

     

     

    :: The TITLE option is the scripts name

    set TITLE=adobe-flash-background-updates

     

     

    :: The LOG option is the log file.

    set LOG=./%TITLE%.log

     

     

    :: The SOURCE option is the mirror on which you would like to download the flash files from.

    set SOURCE=http://fpdownload2.macromedia.com

     

     

    :: The DESTINATION option is where you would like your downloaded files to go so they are accessable by your web service.

    set DESTINATION=d:\wwwroot\Proxy

     

     

    :: The VERSION option is the current major version of Flash Player (for Flash Player 11.2, the major version is 11).

    set VERSION=11

     

     

    :: The Proxy settings for wget to use

    set HTTP_PROXY=http://edupass.tallangatta-sc.vic.edu.au:8080

     

     

    :::::::::: SCRIPT CORE ::::::::::

     

     

    echo Welcome to %TITLE% Script!

    echo =O====== %date% %time% ======== >> %LOG% 2>&1

     

     

    if exist %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml (

    echo Skipping destination folder structure creation.

    ) else (

    echo Creating destination folder structure.

    mkdir %DESTINATION%\pub >> %LOG% 2>&1

    mkdir %DESTINATION%\pub\flashplayer >> %LOG% 2>&1

    mkdir %DESTINATION%\pub\flashplayer\update >> %LOG% 2>&1

    mkdir %DESTINATION%\pub\flashplayer\update\current >> %LOG% 2>&1

    mkdir %DESTINATION%\pub\flashplayer\update\current\sau >> %LOG% 2>&1

    mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION% >> %LOG% 2>&1

    mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml >> %LOG% 2>&1

    mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install >> %LOG% 2>&1

    )

     

     

    echo Downloading files...

    wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/xml/version.xml -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml\versio n.xml >> %LOG% 2>&1

    wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install _all_win_ax_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\in stall_all_win_ax_sgn.z >> %LOG% 2>&1

    wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install _all_win_pl_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\in stall_all_win_pl_sgn.z >> %LOG% 2>&1

    wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install _all_win_64_ax_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\in stall_all_win_64_ax_sgn.z >> %LOG% 2>&1

    wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install _all_win_64_pl_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\in stall_all_win_64_pl_sgn.z >> %LOG% 2>&1

     

     

    echo Script complete! See log file for more infomation %LOG%

    echo =X====== %date% %time% ======== >> %LOG% 2>&1

    echo. >> %LOG% 2>&1

     

     

    :::::::::: END OF SCRIPT ::::::::::

     

    Thanks for your help,
    Tyrone Wyatt.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 30, 2012 10:37 AM   in reply to HansBrockstedt

    Hi Hans,

     

    There shouldn't be a need to change the user account for the service, unless you're using proxy servers. If you're in this situation, it is recommended to duplicate the Flash Player Updater task in Windows Task Scheduler and to change the user account for the duplicated task, rather than the automatically created task. The reason here is that the automatically created task may be changed by an update to Flash Player and the user account may be changed back to the default SYSTEM account.

     

    You need to run the updater twice to update both ActiveX and Plugin because each update to Flash Player will also update the Background Updater, if necessary. Note that this is usually handled automatically and with a delay of 1h. In other words, in 1 hour and 5 minutes or so, both ActiveX and Plugin should be automatically updated.

     

    Hope this helps.

     

    Thanks,

    Stephen

     
    |
    Mark as:
  • Currently Being Moderated
    May 4, 2012 6:36 AM   in reply to Stephen Pohl

    I experienced the same problem as Hans with running the silent update from an internal server. Initially I got the same error log sequence:

     

    2012-5-4+11-58-0.348 [warning] 1403 12175

    2012-5-4+11-58-0.348 [warning] 1407 183

    2012-5-4+11-58-0.348 [warning] 1408

     

    I figured out that the first line was caused by the fact that I did import the server self-signed certificate into the personal trusted store on the client instead of the Local computer store. So running the mmc with certificates (Local Computer!!) and import the cert has fixed that issue. I now see the line in the server logfile:

     

    GET /pub/flashplayer/update/current/sau/11/xml/version.xml - 443 - xx.xxx.xx.xx Get+Flash+Player+version+xml/1.0 500 0 64 0

     

    so obviously the version.xml is found but it doesn't go further and it doesn't seem to find the z-files. The client log now tells me:

     

    2012-5-4+13-24-37.320 [warning] 1407 12044

    2012-5-4+13-24-37.320 [warning] 1408

     

    Any idea what these error codes mean?

     

    -Steve

     
    |
    Mark as:
  • Currently Being Moderated
    May 4, 2012 9:13 AM   in reply to flash_karotti

    Hi Steve,

     

    This error is most likely due to the fact that you selected "Require client certificates" on your webserver. Please uncheck this and try again. If you're still seeing errors, please post a new log with the error codes after making this change.

     

    Thanks,

    Stephen

     
    |
    Mark as:
  • Currently Being Moderated
    May 7, 2012 4:26 AM   in reply to Stephen Pohl

    Hi Stephen,

     

    that was exactly the reason. It's now working fine.

     

    Thanks!

     

    -Steve

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 13, 2012 6:26 AM   in reply to Stephen Pohl

    Hello!

     

    I am experiencing very similar issues that I have not been able to resolve even though I've read through this thread  and checked everything that I know I can.  I am attempting to update from an internal server.  When I comment out that line, the silent update goes well.  If I don't comment out that line, I get warnings in my log as shown below:

     

    [info] 1628 internalserver.domain.local

    [info] 1629 internalserver.domain.local

    [info] 1614

    [info] 1615

    [info] 1618

    [info] 1608

    [warning] 1403 12175

    [warning] 1407 183

    [warning] 1408

    [info] 1612

    [info] 1621

    [info] 1620

     

    My mms.cfg contains the following entries:

     

    AutoUpdateDisable=0

    SilentAutoUpdateVerboseLogging=1

    SilentAutoUpdateEnable=1

    SilentAutoUpdateServerDomain=internalserver.domain.local

    AVHardwareDisable=1

     

    We're using Windows Server 2008 R2 and IIS 7.5.  I don't require SSL connections to the server.  If I browse to http://internalserver.domain.local/pub/flashplayer/update/current/sau/ 11/xml, I can see the version.xml without a problem.  I can also get to all of the file downloads without a problem, using standard http.

     

    No SSL.PNG

     

    A reading from the IIS logs shows the following entries:

     

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 328

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 203

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 203

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 218

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 218

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 203

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 203

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 187

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 171

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 171

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 171

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 156

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 203

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 171

    GET /pub/flashplayer/update/current/sau/11/xml/ - 80 - 172.16.1.38 Mozilla/5.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+WOW64;+Trident/5.0 ) 403 14 0 218

     

    Any further help would be greatly appreciated!!

     

    Thanks!

    Anthony

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 13, 2012 10:01 AM   in reply to antsman

    Well, I figured out what my problem was!  I ended up using Microsoft TCPView to see what was happening.  As it turns out, the service only seems to connect via https.  So, my counterpart created an enterprise-signed certificate and applied that to the server.  That fixed the problem...no more errors!

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 21, 2012 7:06 AM   in reply to antsman

    Apologies to hijack this thread but I have been following the admin guide to set up the internal server and followed all the suggestion contained on this page to try and get the server/client working but to no avail. I have done self signed certificates in on the web server and test client, edited my mms.cfg properly as far as I can tell, I can browse to the xml on port 80 and 443 with no problem and have tried duplicating the scheduled task and changing the user but none of it has worked.

    I seem to have different codes in my flashinstall.log file that I can't seem to find any information on. Is there any reference material to look up what the codes mean?

     

    Here is a copy of my log file in case anyone can offer some insight:

     

    2012-9-21+13-44-21.994 [info] 1628 webserver.domain

    2012-9-21+13-44-22.67 [info] 1629 webserver.domain

    2012-9-21+13-44-22.121 [info] 1614

    2012-9-21+13-44-22.182 [info] 1615

    2012-9-21+13-44-22.254 [info] 1618

    2012-9-21+13-44-22.310 [info] 1619 1063

    2012-9-21+13-44-22.330 [info] 1628 webserver.domain

    2012-9-21+13-44-22.330 [info] 1629 webserver.domain

    2012-9-21+13-44-22.330 [info] 1614

    2012-9-21+13-44-22.330 [info] 1615

    2012-9-21+13-44-22.330 [info] 1618

    2012-9-21+13-44-22.331 [info] 1604

    2012-9-21+13-44-22.331 [info] 1608

    2012-9-21+13-44-22.374 [warning] 1411

    2012-9-21+13-44-22.374 [warning] 1409

    2012-9-21+13-44-22.374 [info] 1612

    2012-9-21+13-44-22.374 [info] 1620

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 21, 2012 11:39 AM   in reply to m_sutton

    Hi m_sutton,

     

    A couple of things:

    1. Why do you change the user of the scheduled task? This shouldn't be necessary.

    2. Have you imported the self-signed certificates to the certificate store on your client?

    3. Are you using the official version.xml file (obtained through the Flash Player licensing program)?

     

    The warning 1409 means that the version.xml file could not be parsed. This usually means that a SSL connection could not be established. Another indicator for this is warning 1411 which indicates that the version node could not be found in the version.xml. Another option is that your xml file is not in a valid format.

     

    To rule out problems with your self-signed certificate, please follow the instructions here and let us know if that fixed it: http://blogs.adobe.com/livecycle/2012/04/rights-management-how-to-get- windows-7-to-trust-a-self-signed-server-certificate.html

     

    Best,

    Stephen

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 24, 2012 12:56 AM   in reply to Stephen Pohl

    Hi Stephen,

     

    Thank you very much for replying.

     

    I changed the user of the task simply to eliminate that as a possible fix - it had been mentioned higher up this thread so thought it was worth a try but obviously to no avail.

     

    I have imported the self-signed certificate to the certificate store on my client. Followed the instructions on your link to verify that I had done it correctly and all settings are ok.

     

    I am using the xml that was discussed in the flash player 11.2 admin guide. If there is another one that I should be using, please could you point me in the direction where I may be able to obtain it?

     

    Many thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 24, 2012 10:11 AM   in reply to m_sutton

    Hi m_sutton,

     

    The administration guide has been updated. Please refer to http://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_gu ide.html for the latest version. If you're still running into these issues after following the updated instructions, please let us know!

     

    -Stephen

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 25, 2012 2:06 AM   in reply to Stephen Pohl

    Hi Stephen,

     

    Obtained the new admin guide and files - thank you for pointing me in that direction.

     

    Downloaded the new files and set everything up. The warning element of my flashinstall.log file has gone away but I can't see anything indicating success nor has my flash version updated. The flash version I had installed to test is 11.4.400.252 and my log file reads as:

     

    2012-9-25+8-53-7.441 [info] 1628 webserver.domain

    2012-9-25+8-53-7.492 [info] 1629 webserver.domain

    2012-9-25+8-53-7.543 [info] 1614

    2012-9-25+8-53-7.594 [info] 1615

    2012-9-25+8-53-7.645 [info] 1618

    2012-9-25+8-53-7.697 [info] 1619 1063

    2012-9-25+8-53-7.812 [info] 1628 webserver.domain

    2012-9-25+8-53-7.812 [info] 1629 webserver.domain

    2012-9-25+8-53-7.813 [info] 1614

    2012-9-25+8-53-7.813 [info] 1615

    2012-9-25+8-53-7.813 [info] 1618

    2012-9-25+8-53-7.815 [info] 1604

    2012-9-25+8-53-7.815 [info] 1608

    2012-9-25+8-53-7.815 [info] 1612

    2012-9-25+8-53-7.816 [info] 1620

     

    Is there anything further I can do to try and ensure the update process works?

     

    Many thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 25, 2012 10:08 AM   in reply to m_sutton

    Hi m_sutton,

     

    Please follow these steps and let us know if it worked:

    1. Verify that the version numbers in the version.xml are indeed higher than the version of Flash Player currently installed.

     

    2. Make sure that the following settings are still present in the mms.cfg:

    - SilentAutoUpdateEnable=1

    - AutoUpdateDisable=0

     

    3. In the registry, remove the following keys (if present):

    - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer\LastUp dateCheck

    - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer\Update Attempts

    (If you have a 32-bit system, please remove "Wow6432Node" from the two paths given above.)

     

    After following the three steps above, you may trigger an update check manually by running the service or launching the scheduled task for Adobe Flash Player Background Updater.

     

    Background: The log shows that the update check was skipped. This is usually due to the fact that your system already performed an update check in the past 24 hours. By removing the "LastUpdateCheck" key from the registry, you should be able to trigger another check. Step 1 and 2 are given to ensure that your system is still in a good state to get updates from your server.

     

    Hope this helps!

     

    -Stephen

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 7:29 AM   in reply to Stephen Pohl

    Thanks Stephen, will check this in the coming days and let you know either way. Much appreciated

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 19, 2012 2:41 PM   in reply to Stephen Pohl

    I am trying to set up silent auto updating on Windows 7. Currently 11.4.402.287 is installed. I understand 11.5.502.110 is available.

     

    mms.cfg look like this:

    AutoUpdateDisable=0

    SilentAutoUpdateEnable=1

    SilentAutoUpdateVerboseLogging=1

     

    I saw the above post and deleted the LastUpdateCheck and UpdateAttempts registry keys.

     

    I ran the updater task and the following entries are added to the log.

    2012-11-19+22-20-55.471 [info] 1614

    2012-11-19+22-20-55.488 [info] 1615

    2012-11-19+22-20-55.491 [info] 1618

    2012-11-19+22-20-55.495 [info] 1619 1063

    2012-11-19+22-20-55.507 [info] 1614

    2012-11-19+22-20-55.513 [info] 1615

    2012-11-19+22-20-55.518 [info] 1618

    2012-11-19+22-20-55.524 [info] 1604

    2012-11-19+22-20-55.524 [info] 1608

    2012-11-19+22-20-55.846 [info] 1612

    2012-11-19+22-20-55.852 [info] 1620

     

    What else can I check?

     

    Thanks

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Nov 20, 2012 2:39 PM   in reply to dvcroft1

    @dvcroft1 - After major releases, silent updates from adobe.com will not be available for 30 days (or sooner, if a zero day security update is made available). 

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 21, 2012 6:05 AM   in reply to Chris Campbell

    @Chris Campbell - But even when using your own update server (SilentAutoUpdateServerDomain parameter) flash won't update to the latest major version. I'm not really understanding this behaviour. For 30 days I have people complaining they get a flash-update-available message when booting their computer. For 30 days we can't use new flash features and we're missing security updates. What's the reason for this 30 day waiting period?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 26, 2012 9:30 AM   in reply to Chris Campbell

    So you mean it is working as designed? I guess some people may want to vet a new version or have a chance to update internal apps against a new version. That doesn't fit our situation. We would like to have a configuration option that allows us to get all updates immediately.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 26, 2012 1:48 PM   in reply to dvcroft1

    I have to agree with dvcroft1. In my work enviroment our users dont have admin rights and are not plugged into a power source (always on battery power) so they will never receave updates. We need options develepted to bypass these by-design-road-blocks.

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Nov 28, 2012 5:33 PM   in reply to Bram_ins

    @Bram_ins - If you have specified your own internal server in the SilentAutoUpdateServerDomain parameter (see this post for details) your users should be getting the latest update within 24 hours.  Can you post the contents of the mms.cfg on one of these systems along with their flashinstall.log file?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 4, 2012 6:56 AM   in reply to Chris Campbell

    @Chris Campbell

     

    Thanks for the follow up.

     

    We push the following mms.cfg to our users:

    AutoUpdateDisable=0

    SilentAutoUpdateEnable=1

    SilentAutoUpdateServerDomain=flashupdate.ourserver.eu

     

    I just noticed since the silent 11.4.402.278 update, the mms.cfg on our devices have the SilentAutoUpdateEnable parameter set to 0. The two other parameters are still the same. Now we only pushed our cfg once after the first install. Could a silent update change this specific parameter? I just doublechecked the initial cfg we push and it has SilentAutoUpdateEnable=1. So I have no idea at the moment how all our devices have a value of 0 now.

    I'll deploy our config again to all machines and post back soon.

     

    /edit:

    At the end of the install log the following errors are shown:

    2012-10-27+9-5-0.750 [error] 1217 -2146881269

    2012-10-27+9-5-0.750 [error] 1234 183

    2012-10-28+9-5-1.63 [error] 1217 -2146881269

    2012-10-28+9-5-1.63 [error] 1234 183

    2012-10-29+10-5-1.225 [error] 1217 -2146881269

    2012-10-29+10-5-1.226 [error] 1234 183

    2012-10-30+11-5-1.537 [error] 1217 -2146881269

    2012-10-30+11-5-1.538 [error] 1234 183

    2012-10-31+12-5-1.409 [error] 1217 -2146881269

    2012-10-31+12-5-1.409 [error] 1234 183

    2012-11-1+13-5-1.337 [error] 1217 -2146881269

    2012-11-1+13-5-1.339 [error] 1234 183

    2012-11-2+14-5-1.469 [error] 1217 -2146881269

    2012-11-2+14-5-1.471 [error] 1234 183

    2012-11-3+15-5-1.241 [error] 1301

    2012-12-3+15-5-1.143 [error] 1301

     

    /edit2:

    I checked the log file again today and the following was added:

    2012-12-4+13-5-1.104 [info] 1628 flashupdate.ourserver.eu

    2012-12-4+13-5-1.106 [info] 1629 flashupdate.ourserver.eu

    2012-12-4+13-5-1.107 [info] 1614

    2012-12-4+13-5-1.108 [info] 1615

    2012-12-4+13-5-1.108 [info] 1618

    2012-12-4+13-5-1.110 [info] 1619 1063

    2012-12-4+13-5-1.539 [info] 1628 flashupdate.ourserver.eu

    2012-12-4+13-5-1.540 [info] 1629 flashupdate.ourserver.eu

    2012-12-4+13-5-1.540 [info] 1614

    2012-12-4+13-5-1.541 [info] 1615

    2012-12-4+13-5-1.541 [info] 1618

    2012-12-4+13-5-1.544 [info] 1604

    2012-12-4+13-5-1.544 [info] 1608

    2012-12-4+13-5-1.594 [info] 1612

    2012-12-4+13-5-1.596 [info] 1620

     

    I've then deleted the LastUpdateCheck and UpdateAttempts from the registry and ran the update task again:

    2012-12-4+14-34-40.886 [error] 1226 1062

    =O====== M/11.5.502.110 2012-12-04+14-34-30.729 ========

    0000 [I] 00000010 FlashPlayerInstaller.exe -install -iv 9

    0001 [I] 00000020 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl

    0002 [I] 00000011 1

    0003 [I] 00000013 C:\Windows\SysWOW64\Macromed\Flash\Flash32_11_5_502_110.ocx

    0004 [I] 00000015 C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_11_5_502_110_ActiveX.e xe

    0005 [I] 00000016 C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_11_5_502_110_ActiveX.d ll

    0006 [I] 00000023 C:\Windows\SysWOW64\Macromed\Flash\activex.vch

    0007 [I] 00000019 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl

    0008 [W] 00001024 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl 183

    0009 [W] 00001024 C:\Windows\SysWOW64\FlashPlayerApp.exe 183

    0010 [I] 00000021 C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

    0011 [W] 00001106

    0012 [W] 00001106

    0013 [W] 00001024 C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe 183

    0014 [I] 00000012

    =X====== M/11.5.502.110 2012-12-04+14-34-42.000 ========

     

    It seems the activex version has been updated correctly now but the plugin version is still 11.4. This has probably to do with the [error] 1226 1062?

     

    /edit3:

    After running the update task again, the plugin version has been updated. It was probably in use by a browser.

    I'll now monitor our environment the following days to check if other devices are picking up the update as well. If nothing happens i'll delete those reg keys on all computers.

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Dec 5, 2012 5:27 PM   in reply to Bram_ins

    @Bram_ins - I've forwarded your post to our installer team.  Afaik, we don't write to the mms.cfg but I'm confirming.  I've also asked for confirmation on the errors.

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Dec 6, 2012 4:35 PM   in reply to Chris Campbell

    Here's what I found out from our installer engineer.

     

    This failure was due to failed installer validation. This can happen if the SAU installers he hosted internally were corrupted in some way, or became corrupted in transit from his hosting server to the client. If it’s working now, perhaps the problem sorted itself out.

     

    The other two behaviors he noticed are expected:

    - SAU automatically configures the client as a notification client when there are consecutive silent autoupdate failures (such as he had with the ActiveX install failures). This ensures that users with systemic issues that break SAU do not get orphaned and miss out on Flash Player updates altogether.

    -  The ActiveX Player is updated vi SAU first, then an hour or so later the Plug-in is updated. This is by design.

     

    Good info on the two behaviors.  I wasn't aware (or just didn't remember ) that we reset the mms.cfg if the autoupdate failed multiple consecutive times.  Good thing to know.

     

    Hope this helps,

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2012 12:27 AM   in reply to Chris Campbell

    Thanks Chris! Very valueable information.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 11, 2013 6:27 AM   in reply to Bram_ins

    Never worked for me on 2 machines with a fresh clean Windows 7 Home Premium x64 SP1 installation.

    For example now 11.7.700.169 is out but I still have 11.6.602.180...

     

    Since Windows installations are fresh and clean I've never touched Sheduled Task or the Service that are set properly at default.

    I use UAC at max level, not default.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 16, 2013 5:09 AM   in reply to Chris Campbell

    Hi Chris,

     

    I just discovered this interesting post and i have a question about silent update. We work with Mac OSX 10.6, 10.7 and 10.8 in public schools ans we have silent update ON (with mms.cfg looks like : AutoUpdateDisable=0 SilentAutoUpdateEnable=1). Evrything fine, we have Flash 11.6.x. But now, Flash 11.7 is out ans Safari shows an alert saying that an update is out. So if i understand correctly, silent update isn't working if there is a major update. Right ? Second question, i read in this post what you write (After major releases, silent updates from adobe.com will not be available for 30 days (or sooner, if a zero day security update is made available). So, is it possible to reduce this time ) ?

     

    Thanks in advance

     

    :-))  Christian

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Apr 16, 2013 6:46 PM   in reply to ramuntcho2

    Hi Christian,

    That is correct, for 30 days (or sooner if another update is made available), we do not use the silent auto udpate mechanism.  However, admins do have another option and can implement their own internal update server if desired.  If you haven't already, please see this blog post for details:

     

    http://blogs.adobe.com/spohl/2012/04/24/it-admin-deploying-flash-playe r-via-background-updater/

     

    Thanks,

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 18, 2013 5:48 AM   in reply to Chris Campbell

    Hi Chris,

     

    Thanks for the quick answer !

     

    Christian

     
    |
    Mark as:
1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (2)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points