However, I then saw this post on the Adobe forums: Therefore, my assumptions were that I could create an SMS/SCCM advertisement to run this uninstaller program, prior to then running the new 11.5.7.609 MSI. ![]() However, I see that Adobe do an uninstall program (as downloadable via here: ) and whilst I've not done any exhausted testing, I've tried running this "sw_uninstaller /s" and it does appear (albeit this might be on the surface?) to uninstall both an 11.0.x and a few different versions of 10.x Shockwave. I can see that the Shockwave Player 11.5.7.609 corporate MSI won't remove any previous versions it encounters (10.x, 11.0.x), and thus I've read posts on forums where people have put together scripts that will detect previous versions first (whether that be based on SMS inventories, traversing through registry uninstall keys, etc) to do this. Unfortunately I have inherited an environment where proper managed automation of such updates was not done, and thus it's chaotic!! We've got 5,000 XP images, and having used SMS/SCCM hardware/software inventory, and I can see that we have various flavours of 10.x, 11.0.x, and some 11.5.x's already (manually installed by users). I'm wondering if anyone can volunteer their experiences before I roll? However, having read so many different scenarios, I'm finding it a little confusing as to know what sort of route to go down with this. I've read numerous posts here relating to the update of Adobe Shockwave Player 11.5 (11.5.7.609).
0 Comments
Leave a Reply. |