We need to know what Adobe Flash Player URLs to allow through our gateway firewall, and what each URL is used for.
You're request is too broad, as there are many, and constantly, changing URLs. Please be more specific and describe exactly what you're objective is so that we may be able to better assist you.
We need to know what URLs the Flash Player add-on for Internet Explorer 11 uses to check for updates and any other URLs it uses to "call home" so we can allow that traffic.
As I said, there are many URLs and they change often. You're best option would be to license Flash Player for distribution within your organization (free for the vast majority of use cases) and host the update resources locally. Your client systems would then check your local server for an update, instead of Adobe's servers. When hosting update files locally, only Background Updates would happen as this is the only supported method for customers to host update files locally. Background Updates updates silently in the background (within 24 yours of you posting new files) with no user interaction required. For more information on hosting Background Update resources locally see 'Performing a background update' section in Chapter 3 of the Flash Player Administrator's Guide
Thanks for your response. We'll take at look at the Admin Guide for future reference.
We have a license to distribute for Flash Player. For the ActiveX.exe install, it appears that it calls home. I guess that we'll look at the network logs to see what it's connecting to.
How are you deploying Flash Player to new clients, and how are subsequent updates being deployed?
When we execute the ActiveX.exe installer - example: install.flash.player_28_active_x.exe, we see it connecting to fpdownload.macromedia.com on TCP port 443. This is what we are looking for. We have automatic updates disabled on the clients.
When we download the executable as instructed in our license, it connects to the same URL for the download.
Our question concerns what ADOBE URLs the product may connect to during installation so that we don't inadvertently block something it needs to install.