I read quite som threads on the silent Flash Player upgrade (amongn them How it works, long thread on not working updates, fixed bug on SSL certs), and got it finally working on our internal server but not directly from Adobe. <edit>In one discusison - which I unfortunately cannot find anymore - In this post, Chris stated 11.4 requiring an internal server, e.g.</edit> when adding SilentAutoUpdateEnable to the mms.cfg, also SilentAutoUpdateServerDomain had to be specified.
<edit>My tests seem to confirm this for player 11.4.402.287, I only see these lines in the FlashInstall.log when running the Adobe Flash Player Updater scheduled task:
2012-11-26+10-54-41.306 [info] 1614
2012-11-26+10-54-41.384 [info] 1615
2012-11-26+10-54-41.446 [info] 1618
2012-11-26+10-54-41.509 [info] 1619 1063
2012-11-26+10-54-41.571 [info] 1614
2012-11-26+10-54-41.571 [info] 1615
2012-11-26+10-54-41.571 [info] 1618
2012-11-26+10-54-41.587 [info] 1608
2012-11-26+10-54-41.587 [info] 1604
2012-11-26+10-54-41.837 [info] 1612
2012-11-26+10-54-41.837 [info] 1620
My mms.cfg contains the following lines:
When setting up an internal server and adding SilentAutoUpdateServerDomain, the update works as expected. If this is true, this Was this a limitation of 11.4, which is gone for 11.5? Having a mandatory requirement for internal server </edit> seems to contradict the spirit of the Adobe Flash Payer 11.5 Deployment Guide. Why have two sections (pages 18/19), first "Performing a background update" and then "Background updates from an internal server" if silent updates always require an internal server?
Would anyone care to share their understanding? Does SilentAutoUpdateEnable require SilentAutoUpdateServerDomain <edit>for 11.5</edit>?
Edited to specify observed update behavior for 11.4 with and without SilentAutoUpdateServerDomain
You do not have to have SilentAutoUpdateServerDomain set for SilentAUtoUpdateEnable. With the release of 11.5 (or any major release), we do not update through the silent auto update (SAU) system for the first 30 days. This can be circumvented by setting up your own internal SilentAutoUpdateServerDomain.