Skip to main content
bb74483076
Participant
May 24, 2016
Question

Auto-updating Flash behind proxy - account for the scheduled task auto-updater

  • May 24, 2016
  • 1 reply
  • 1111 views

Can anybody suggest a good way to automatically update Flash behind an authenticated proxy, without using an internal deployment server?

Why by default the scheduled task for the Flash updater runs on SYSTEM account (doesn't work behind the proxy), while a similar task for Reader updater runs on the user's account (works behind the proxy)? What's the logic here?

Thanks.

This topic has been closed for replies.

1 reply

_maria_
Legend
May 24, 2016

Hi,


I'm inquiring about the first question.

For the second question, Background Updates runs as SYSTEM account to enable Background Update to run even when no users are logged on, which allows for the system to updated as soon as Flash Player determines an update is available.

--

Maria

bb74483076
Participant
May 24, 2016

Thanks for your quick reply.

> For the second question, Background Updates runs as SYSTEM account to enable Background Update to run even

> when no users are logged on, which allows for the system to updated as soon as Flash Player determines an update

> is available.

I understand your point, but that also makes it obsolete behind the authenticated proxy.

We'd love to schedule the Flash auto updated on the user account, so it would work behind the proxy, but it's then causing a pop-up window for a moment on a user's screen... Can it be hidden?

Frankly I still don't understand why 2 Adobe programs use 2 different auto-update methods / accounts...


Thanks,

Bartosz

_maria_
Legend
May 24, 2016

I'm not sure I understand what you're referring to here:

We'd love to schedule the Flash auto updated on the user account, so it would work behind the proxy, but it's then causing a pop-up window for a moment on a user's screen... Can it be hidden?

Can you post a screenshot​ of the pop-up window?

This article, https://support.microsoft.com/en-us/kb/2778122 discusses authenticated proxy servers and the Windows App store.  The recommendation is to enable unauthenticated access to URLs by white listing them.  Not sure if this would work for your situation.  If you'd like to test it out, Background Updates uses the domains fpdownload.macromedia.com and fpdownload2.macromedia.com.