Where Did the Adobe Flash (All IE) Package Go?

4/26/2018 3193 Contributors

You are unable to locate and download the Adobe Flash (All IE) Package from the Package Library and require an appropriate Adobe Flash IE package in the PDQ Deploy Package Library.

Short Answer: Use the Flash patches relative to the target OS that you are supporting. At this writing there are three packages:

Adobe Flash for IE - Use this package on Windows XP, Vista and 7.

Adobe Flash for IE - Windows 8.1 - Use this package on Windows 8.1 and Server 2008R2 (if the server has the Desktop Experience feature enabled)

Adobe Flash for IE - Windows 10 - Use this package on Win 10, Win 10 Release 1511 and Win 10 Release 1607.

If you use the PDQ Inventory Collection Library to find the necessary targets you will find the appropriate collections for each OS.

The All IE package has become confusing because we are dealing with two different publishers, Adobe and Microsoft, and the different Flash patches get released at different times and, often, with different versions.

In a simpler time there was just one Adobe Flash Package for Internet Explorer. There was one MSI installation file that was provided by Adobe. The IE Flash world became more complex with the onset of Windows 8 where now we needed three installation files. The normal IE Flash from Adobe and two hotfix patches from Microsoft for the 32 and 64 bit architectures. After Microsoft released Windows 8.1 the number of installation files jumped to 5.

Admin Arsenal was up to the task and it was decided to create an all encompassing package that was complete and powerful and fulfilled all the needs of the people once more.  

The package became much more complex with the birth of Windows 10 (at this writing there are 6 different Flash patches for Windows 10), and we truly felt like we were letting our customers down.  We continued to create individual packages (for Windows 10, 8.x and XP/7) and update them quickly, but the All IE package suffered while waiting for all the package versions to be released and align once more, most times delaying crucial updates to the customers. Another wrench thrown in is that one of platforms would often receive a mid-month patch which raised the version for just that platform (e.g. Windows 8.1). We would update the All IE but had to decide what version to use (the new version that impacted 8.1 or the old version that was applicable to the other OSes. We had customers asking us in droves why the non-Windows 8.1 patches were the same as the previous releases. Then Windows 10 would jump in with another mid-month patch a few days later and the cycle would begin again.

This confused the people even more and a stirring ensued in the streets.  Something had to be done.

In all seriousness, we at Admin Arsenal hate taking things away from our customers, but in this case, using an All-in-one package wasn’t leaving our customers with warm fuzzies at the end of the day when an old version was redeployed to their sites or they were questioned by their own staff why there were differences. We’ve changed the names of the packages in the Package Library to be easier than ever to decide which package is for which application. In addition we have corresponding collections in the Collection Library that we keep up to date. Armed with these tools you can still completely automate Adobe Flash in your environment with success and control using separate schedules for each version you require.

See also:
Why We're Discontinuing the Adobe Flash All IE Package (Video)
Create and Schedule Auto Deployments (Video)
Auto Deployment Best Practices (Video)
Deploying Adobe Flash for IE (Video)