As with the last update, Adobe has yet to update their FlashPlayer xml page with the new version information. This means products like AutoPkg, which use that page, won't see that there's a new version until Adobe gets around to updating it. it also means Flash clients with the auto update setting on won't get the new version until its updated since it uses the same xml file. Not a huge deal, and I'm sure it will be updated later today, but just something to be aware of.
@rtrouton, any idea why using your script as a policy would report a failure on some computers? Log shows that the upgrade completed successfully, but some computers are reporting a failure after completion.
A
Anonymous
June 10, 2014
@cstout I noticed that if there was another volume mounted, you'd see an error in the policy logs. View the actual installation and you should see that it was successful - that was my experience, anyway.
I removed the -verbose from the v14 of Rich's (awesome, as usual) script.
Can this be deployed with the rest of my packages? I've got the script as part of my deployment, it's priority is set to "After". But Flash isn't getting installed, and there's no mention (fail or success) of the script in the install log on the machine.