This one seems odd. I think Adobe may be redirecting the Shockwave download based on browser.
I’m having a problem with Fixlet 12011064 in “Updates for Windows Applications” - “Adobe Shockwave Player 12.2.3.183 Available”. When a client runs this Fixlet the Action’s download status shows a sha1 mismatch.
When I download http://fpdownload.macromedia.com/get/shockwave/default/english/win95nt/latest/sw_lic_full_installer.exe
via Google Chrome, I get the correct file (version 12.2.3.183 with a sha1 matching the Fixlet). When I download the same URL using Internet Explorer, I get version 12.2.2.172 instead and the sha1 mismatches the Fixlet.
I don’t know whether BES Server is using a browser agent string to identify as Internet Explorer, or whether Adobe has “file X for Chrome, file Y for all others” and both IE and BigFix match “all others”.
In any case, I had to download the files using Chrome, rename them to their sha1 values, and manually cache them at wwwrootbes\bfmirror\downloads\sha1 in order to execute the Shockwave actions.