This entry was posted on January 18, 2013 at 6:52 pm and is filed under Adobe, Deployment, Packaging. You can subscribe via RSS 2.0 feed to this post's comments. Both comments and pings are currently closed.
Thanks, Greg. Had I not implemented my own version of the fix in a package on Friday, I would have used this. That being said, it’s a damn shame you have to do Adobe’s work for them. This is part of how their fix should have been distributed. It could have also added a flag such as –includePS that could have bundled in the update contents of the Photoshop update, thus including the entire fix in a native Apple pkg. But of course, they’d never do anything like that, so kudos to you for filling the void, as usual.
@mboylan Adobe is getting complacent, since they know Mac admins will step up with workarounds. Their dev team are incapable or indifferent. Adobe isn’t going to “fix” the dev team issue without a lot of pressure.
Your MacEnterprise thread is just the ticket, this fiasco is Adobe’s “Newtown” and we need to strike while the iron is hot. Publicly lambasting Adobe over their crappy installers got us AAMEE and Jody…
Steven, I had this happen with Acrobat as well. Were you able to reserialize it using Greg’s tool or did you do something else? Did you use the same serial number as Creative Suite or did you have to grab a standalone serial number for Acrobat?
The same number – it worked fine and so far (knock knock) all is well. The hard part is that not all our installations have actually had the problem come up so instead I just ARD to search for all installations with Photoshop<13.0.4 and went ahead whether they had the problem or not. It took several hrs. Still better than doing otherwise that this proceedure.
Can you share the LEID number you manually entered? I have been searching on Google and can only find LEID numbers for the Windows version of Acrobat. I finally looked through the CS6 install media and found AcrobatPro-AS1-Mac-GM. Is that what you used?