Copy link to clipboard
Copied
Our users use zscaler for web filtering and when it's running the online flashplayer install fails to initialize even if we remove all blocks. The online flashplayer install runs fine if we turn off zscaler to do it but that is a long process each time flashplayer has a new version. I can bypass the zscaler filter using the PAC file programming if I could get a list of all the URL's, IP's or server addresses that need to be bypassed to get the online installer to run properly. Where can I find such a list? Thanks in advance.
Unfortunately, the Flash Runtime team doesn't maintain the distribution infrastructure (there's a separate distribution organization the repackages our binaries for distribution and manages the hosting). Ultimately, much of it is coming off the Akamai CDN, so there's no guarantee that IPs are going to be consistent, or that the hostnames would remain static over time.
If you're administering an enterprise environment, there are better options for enterprise distribution and update management tha
...Copy link to clipboard
Copied
Unfortunately, the Flash Runtime team doesn't maintain the distribution infrastructure (there's a separate distribution organization the repackages our binaries for distribution and manages the hosting). Ultimately, much of it is coming off the Akamai CDN, so there's no guarantee that IPs are going to be consistent, or that the hostnames would remain static over time.
If you're administering an enterprise environment, there are better options for enterprise distribution and update management that would bypass all of that complexity.
Check out the administrator's guide for more details:
Adobe Flash Player Administration Guide for Flash Player | Adobe Developer Connection
Copy link to clipboard
Copied
Unfortunately our environment is not on a domain which makes distribution much more difficult. We do have LANDesk but we have never been successful pushing out flashplayer updates through LANDesk.
Copy link to clipboard
Copied
Yeah, that's not ideal. You could still run your own internal update server without installing the player over SCUP/SCM/etc, but you'd need to push an mms.cfg to your clients, and it doesn't really help you out of the first-time download problem. If you pre-configure the machines before they go out to clients, you could probably work around that, but yeah, it seems like a helpdesk nightmare.