Adobe CS6 Package and Extension Manager

[jescala]

Has anyone figured out how to stop Adobe Extension Manager from opening at the end of an install for Adobe CS6 created with AAMEE? I've seen this problem mentioned in a couple of places but no solutions have been offered. I tried skipping the 6.0.4 update to Extension Manager, leaving it at 6.0.0.412. That fixed a bunch of errors that were appearing in Extension Manager, but I can't figure out how to stop it from launching altogether. It still opens to a EULA that needs to be accepted and then displays an error that says "The extension 'Adobe Flash Professional Toolkit for CreateJS' does not contain a valid signature. The extension will not be installed."

-- Jorge

[donmontalvo · Accepted solution]

Wow that was a quick ansewer from an Adobe engineer...gotta love the AAMEE forum :)

Hi, A new update to fix this problem has been posted on http://www.adobe.com/support/flash/downloads.html. You need to download this update and add it manually when creating a package using AAMEE. There is a "Add manually" button on updates screen of AAMEE. You that to add this update manually and create a package. please follow this forum post - http://forums.adobe.com/message/4790883#4790883. It has more details regarding this. Thanks, Saransh katariya | Adobe Systems | skatariy@adobe.com

[donmontalvo]

@jescala In case you don't get an answer here, Adobe has an enterprise deployment forum, with fairly active Adobe engineer participation:

http://forums.adobe.com/community/download_install_setup/creative_suite_enterprise_deployment

[jescala]

Thanks Don! I'll try asking there. I didn't know about that forum, but I did find this update to the extension with the invalid signature on their website:

http://helpx.adobe.com/flash/kb/error-installing-toolkit-createjs-11.html

I'm not sure if that will fix it, but can't figure out how to include it in the AAMEE generated package.

[greatkemo]

Jorge,

I had the same trouble, so all i did is write a simple shell script to kill extension manager and add it as part of the deployment policy or as part of a configuration.

#!/bin/sh
killall "Adobe Extension Manager"

just double check the process name in Activity monitor as i can't remember it off the top of my head

Kamal

[jescala]

Kamal,

I guess that's one way to fix it. Did you add that as a "run after" script and did it catch it quickly? Or does the extension manager interface appear and linger for a while?

-- Jorge

[jescala]

FYI: In case any one wants to follow it, here is the thread on Adobe's forums:

http://forums.adobe.com/thread/1091932

[donmontalvo · Accepted solution]

Wow that was a quick ansewer from an Adobe engineer...gotta love the AAMEE forum :)

Hi, A new update to fix this problem has been posted on http://www.adobe.com/support/flash/downloads.html. You need to download this update and add it manually when creating a package using AAMEE. There is a "Add manually" button on updates screen of AAMEE. You that to add this update manually and create a package. please follow this forum post - http://forums.adobe.com/message/4790883#4790883. It has more details regarding this. Thanks, Saransh katariya | Adobe Systems | skatariy@adobe.com

[jescala · Accepted solution]

Yeah, that was great!

The solution offered on the Adobe forum worked. The fix was to manually add the "Flash Professional CS6 Update 2 (12.0.2.529) – Silent Installation" update found here:

http://download.macromedia.com/pub/flash/updates/cs6/mac/Adobe_Flash_Professional_CS6_Update_3.dmg

The only problem is that manually adding the update does not provide any kind of feedback to let you know it worked. The only way to know is to finish the new package and then test it by installing it.

[carlo_anselmi]

Hello, I just would like to confirm that the solution works, same behavior here, exactly as jescala wrote.
No more Extension Manager!
Ciao
Carlo