Not sure, but this may be the problem. Many sites test if the latest Flash Player (10.1.102.64) is installed, so maybe installing an old Flash Player version is not a good idea.
Installing via MSI should work without a problem - I have used it many times in the recent past.
You can download the latest MSI installer from http://www.adobe.com/products/flashplayer/fp_distribution3.html
Additioal information can be found in http://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_guide.html
Sorry, I mistyped in my original post. The image with 10.1.53 isn't our latest image, its just the one thats currently deployed. 10.1.53 was current when we imaged.
I'm pretty sure (about 95%) we tried using MSI installers for newer versions (10.1.85 and 10.1.102) as well to try and correct the issue, but I will try that again to be sure. I currently have a couple other work arounds I can do for now. I can push firefox and flash plugin to the computers. I have also built a new installation of Flash using AppV which seems to work good. I have rebuilt our images with 10.1.102, hoping that will resolve the issue on anything imaged going forward....but mass imaging is tricky mid school year.
It would be nice to figure out the underlying issue, but if I don't I guess I can use my workarounds for now.
Tried pushing a newer version of MSI to fix the problem, and like I thought it doesn't seem to correct it. Are there some basic troubleshooting steps that I can use to troubleshoot a broken Flash Player on a workstation (log files, registry entries, missing files on the hard drive etc)?
But this is not how I would start investigating; my first steps would be:
- does the Flash animation show at http://www.adobe.com/software/flash/about/ ?
- is the Shockwave Flash object add-on enabled in Internet Explorer?
- what files are in C:\Windows\system32\Macromed\Flash?
- what is the content of FlashInstall.log?