Jun 1, 2010 Adobe Application Manager, Enterprise Edition Now Available Adobe posted the certified version of the Adobe Application Manager Enterprise Edition on our Developer Connection web page as well as our Licensing Web Sit today. You can find the Developer Connection downloads here: Both Windows and Mac versions of freely available to all who wish to use them, including documentation.
However, the MacOS version is a “Preview” version only due to a known issue with regard to deploying packages through ARD. When deploying through ARD a user is currently required to be logged in on the target system. We’re trying to fix this bug ASAP and will repost the MacOS version once the bug is fixed and a new build is certified. Current plans are to repost with the ARD fix so that no user is required to be logged in to the target system before the end of June.
Jan 06, 2016 Download Adobe Application Manager: https://drive.google.com/file/d/0Bw-8fzdMfWSFckYtMTZJWVcwTGc/view?usp=sharing.
Updated: It took much longer than expected to push to production; but, AAMEE should now be available on both LWS and the above URL. The above URL now points to production as well. So, we ran into a pretty serious issue using AAMEE; users will not be able to use the help functions because AIR and the community help application aren’t installed.
When you install one of the CS5 programs that was packaged using the AAMEE tool, and you either go to the help menu, or press ‘f1’, it will appear the program locks-up for 2-3 minutes, and then this error box is displayed: “Adobe ‘program name’ CS5 Help content is not installed, or the installation has been damaged. Please reinstall ‘program name’.” This is probably a show-stopper for our organization as this will generate a huge problem for our help desk. Any chance this will be solved quickly? AceHi75, The reason the Community Help Client is listed in the exceptions folder is because it is an AIR based app. Air based applications access the MSI database. Since the MSI technology does not support recursive MSIs, there is no way to wrap these payloads in our packages.
Instructions for deploying AIR apps can be found at. One question.
Do your end users have internet access? The Community Help Client requires internet access. The alternative is to supply users with a PDF version of the help. Hi Eric, I have to say I’m so glad to see this software arrive! We had so much trouble with CS4!
I am trying to build a package for Mac although seem to be stumbling at the very first step, for whatever I choose when asked to ‘Locate the Product Installation Folder’ I am told ‘A Valid Installer Could not be found.’ I have attempted to push toward a downloaded version of the software taken from LWS, the physical DVD, and also a mounted ISO of the DVD but all seem to bring up the same issue? Eric, Has Adobe provided a method for rolling any updates into the enterprise deployment after it has been created? This has always been a problem in the past with everything except for Acrobat and Reader. A year down the road when there are tons of updates on top of the base product, it becomes a nuisance for our users. They install the product, and then are barraged with a massive number of updates.
For security, and sanity, it would be good to be able to incorporate updates into the administrative install points for the CS5 products. Hi Victoria, Thanks for the response. 90% of our clients do have outward-facing internet access, but we do have users that run these programs in a stand-alone environment, as well as laptops that are being used offline. I’m assuming these users have no choice but to use the.pdf? I’m assuming from your response that there is a way to deploy the AIR and community help apps silently? Will doing this then give them access to all of the help files? Will we be able to deploy the product, (i.e.
Photoshop CS5), then silently deploy AIR and the community help app, and have it integrate into the products? We’re pretty concerned because we believe this will generate a large number of issues with our help-desk. Most of our seasoned Adobe product users are no-doubt used to just pressing ‘f1’ and getting the help menu, and we would like to make the transition to the CS5 products as seamless as possible.
Thanks for your time. Hi Jon, There can be 2 possible reasons for this issue 1) Please make sure that the product install folder that you are providing the path to, contains Install.app (for mac) or Set-up.exe (for win). It seems that you might be pointing to a top level folder. 2) If you are using multi-disk installer, please merge its contents using the steps below: (a)Create a folder and use it as product install folder. The product install folder contains all of the installation files and resources that you will use to create packages with the Application Manager.
(b)Copy the contents of multiple DVDs to your product install folder using the steps specified below: (i) Mount or insert Disk 1, and copy the contents to your product install folder. For example, /MCSuiteBuild/Adobe CS5 Master Collection/. (ii) Mount or insert Disk 2, and copy the contents of the payloads/folder to the payloads/folder in your product install folder.
For example, /MCSuiteBuild/Adobe CS5 Master Collection/payloads/. When asked if you want to overwrite files and folders, click “Yes to all”. (c)Provide path of this product install folder in “Locate the product install folder” text-box and continue with the package creation process. “With CS5 in the retail installer it is possible to place an update in the payloads folder it will deploy as expected with the main product install. I’m not sure what happens with AAMEE. Let me see if I can get one of the core engineers to respond.” Let me clarify that after talking with the engineering team: The internal product team has to rerun their media assembly after putting a patch in the payloads folder.
So this isn’t something that is possible for external customers. However, any product that does rerun their media assembly with a patch will be supported both by retain and AAMEE workflows. This means that if a product is shipped later (say a slipstreamed version of Photoshop, not that such a thing is currently planned) which includes a patch in its payloads then that patch will be deployed at initial install time. So a slip streamed product could include whatever patches that product has produced by that time.
Eric, That really doesn’t help me any. We (we being enterprise customers) need a way to deploy the application with updates without having the user sit through an arduous update process (using adobe updater). This has been achieved with the Acrobat installer by using MSPs. Yes, I know that the “MSI” generated by the AAMEE is simply a wrapper for setup.exe, so in its current incarnation it is not feasible since you can’t generate an MSP patch for a wrapper.
At least give us an “Updates” folder similar to what Microsoft did with the Office 2007 and Office 2010 installers. Any patch placed in that folder will be chained at the end of the installer automatically, simplifying the deployment process. Can we get a solution to this, please? Software updates, system updates after a fresh erase & install. I’ve installed Adobe Reader & Pro 9: next i was prompted to download shockwave player and adobecameraraw: i get errors that say: “Adobe Application Manager is needed to update your product.
Adobe appplication manager is needed to resolve this problem, however it is missing or damaged. Downlad a new copy of AAM from Adobe.com or install this product again. I also odn Adobe PSE8, CS4, but have had TWO damaged optical drives i exceeded the number of installed permitted on PSE8 snd.NEVER. I pad $90, when it came out, and went through many system reinstalls. And Adobe never “forgave” all i got was the $20 rebate So there is NO way i want to risk putting in the CS4 disk 2 wks ago this 2nd optimal drive left scratches on the install disk and if i try the PSD8 disk, it will only give me that same old “activation screen.” ANY solutions please. To ANY of the problems?
I used to have Adobe Reader Pro 9 guess what. I am going to try to get my email set up on wowway sp that address would be ty so very much. Please forgive if i’ve jan leslie (is it safe to buy CS5 yet? I am on MAC 10.6.4 – i have the iMac and the macbookpro. Any chance of the next version of AAMEE for the Mac creating actual Apple Package compliant packages? The current tool creates a shell of a package (that is payload free) that then relays on a set of scripts (preflight, postflight, etc.) to mount disk images and run another installer to actually install the applications. This causes a host of problems with many deployment tools that are expecting a valid package file.
The admin UI of AAMEE is great, nice and simple to use; however, the resulting “installer package” that it creates is lacking. Apple has an extensive documentation on their developer website. Please improve AAMEE to better support one of the preferred methods of deploying software in an enterprise environment.
I’d love to get more details on what problems you encounter with our current PKG solution. Can you provide more details?
I agree that our current solution is a straight-up PKG. Its still our proprietary installation technology with a PKG wrapper. It seems to solve the majority of our customer issues.
Moving to a straight-up PKG is a significant architectural challenge for us given the size and scope and interdependencies in the Creative Suite. As such, its quite costly to move. If you have any further details on what is not resolved and how painful/costly it is to workaround the problem please let us know. That data can then be used to prioritize the necessary design, implementation and testing work. A few easy examples are:. Creating a meta-package that combines the base installer & application updates into a single double-clickable install. This is not possible due to a “Could not copy scripts” error message in Apple’s PackageMaker when including the AAMEE created installer.
In order to do this one has to go through a painstaking process of recreating the Adobe installer via a “snapshot”, or similar process. Installing AAMEE package via ARD when no user is logged in fails. The task errors out with a ” could not be installed. Error message: “Running package scripts””; however, if you log into the workstation then the installer completes successfully. There’s a discussion of AAMEE on as well as a good afp548.com. I guess the short summary would be the two most suggested installer methods is either a) drag and drop, or b) a real package installer, with obviously “b” being the best option for Enterprise deployments. Anonymous, Thanks for the input.
The “no user logged in” bug is a bug that should be fixed in our next release (early July.) So that particular one doesn’t depend on a native PKG. Drag and Drop installs are very unlikely. Even many Apple or MSFT installers are no longer Drag and Drop on the Mac.
Also, as you state, there really isn’t a compelling need for Drag & Drop installers in the volume workflows. The single double-clickable install is a good point. Do you mind contacting me directly so that I know who you are and we can engage in longer discussions? When we’re ready to do another round of prerelease or design work it would be nice to include you in our customer outreach so that your input results in us delivering a better product.
Thanks, –Eric. Thank you for your reply, Jody. I’ve now resolved the issue. Since others experiencing similar problems may be interested to know more about this I’ll provide some details: Originally, after downloading several installation files (Windows version), I tried to run the file called ApplicationManagerEnterprise1all.exe directly, but that only caused an installer with no text to open. Instead it seems that I should download WinRAR, use it to uncompress the file(s) with file ending.7z, locate the uncompressed Set-up.exe file and run it. That seemed to work. The installer did show a long list of error messages, but it seems as if the programs are working.
We recently got licensed for Adobe CS5. I downloaded the ESD packages, have extracted them, followed the deployment guide, etc. Still getting an error A VALID INSTALLER COULD NOT BE FOUND Tried quite a few iterations with no success. We’re using AAMEE 1.1 on a Winxp SP3 computer.it happens during the on the first WELCOME screen when I click next. What’s the trick I’m missing? Can you assist?
I’ve been working on and off on this for a couple days and am getting pressured to get this software rolled out. Karl Zimmerman. I’m testing with Acrobat Pro 9. I’m able to manually install from the downloaded and extracted ESD files. When I try AAMEE again, If I point AAMEE to the directory that contains the Acrobat Pro 9 setup.exe file, I still get the error.
It’s also curious that of all the downloaded and extracted ESDs, only 2 contain a setup.exe – the Acrobat Pro 9 and the Design Premium packages. Not sure what to do with the other packages that only contain fonts folders, goodies folders, etc Thanks for getting back to me. Contacted Karl via email. FYI, AAMMEE does not work with Acrobat 9.
You would have to use an alternate method in deploying Acrobat 9. There is an online seminar on this topic that may be of help: The Acrobat IT Matters blog also has a few handy entries on deployment: Also, if there are other folks who receive the “A VALID INSTALLER COULD NOT BE FOUND” error, be sure to check the posting from Sumita – 1:16 AM on June 8, 2010. Cheers, Jody Rodgers Product Manager, Enterprise & Volume Customers Creative Suite Adobe Systems.
I have had about 60% success following the steps outlined in this article: For the remaining 40% I have had to call Adobe and watch them do various things from deleting files manually, editing the registry and the worst case was to load a new workstation and install the products. I will also add that the new creative cloud apps are very picky about the install process and the user account associated with the install. If Adobe is installed by a user that is no longer with the company and a new user profile is created for a new user and that user attempts to sign in there can be issues. The common remedy for me, as noted above in the troubleshooting link, was a complete uninstall with Adobe's tool and a reinstall of the Creative Cloud App manager and then add the specific Adobe apps through the application manager.
Hope that helps!