AAMEE 3.0 for CS6 available now! Removes puffer fishes!

This is it. The official launch day. You’ve seen the trailers. You’ve bought your popcorn, soda and candy combo. You are in your seat. The lights fade. You are reminded to mute your cell phone ringer. You adjust your 3-D glasses. And here it is Adobe Application Manager Enterprise Edition 3.0 in 3D! Or AAMEE 3-D as we like to call it. Wait why are you taking off your 3-D glasses? What? Your head is hurting? You didn’t ask for the ability to package CS6 applications for the enterprise in 3-D? But our marketing research firm told us that 3-D was still popular. Ugh!

We did not in fact, make AAMEE 3.0 in 3-D. Although that would of been awesome! Okay, no it wouldn’t. A little bit awesome? Okay, I’ll drop it. AAMEE was created back during the CS5 cycle to address the fact that our proprietary installer format was about as helpful to enterprise IT admins as a puffer fish. A puffer fish? What the heck is this? Does Adobe know anything about how things are deployed in an enterprise? What am I supposed to do with this tetraodontidae? But AAMEE outputted the CS installers into pkg and msi files and worked with existing deployment solutions and life was good. Okay, life was bumpy at first, but then it got better. But some folks in the IT admin community simply patted us on the head and said “Nice, Adobe. I’m going to keep my workflow as it is, thank you. You go play now.” And honestly, that was fine. At least we gave folks the option to use our tool and those that did mostly liked it and thanked us even.

Flash forward to the release of CS6. Adobe has introduced new licensing and activation in CS6 that are as helpful to IT admins as, well, a puffer fish. If you are not into the puffer fish metaphor I apologize. That’s all I got. But don’t worry, when we saw these changes coming we said wait, wait, they do not want a puffer fish. So that was the main goal of this release: minimize the impact of the CS6 licensing and activation on the the IT admin. Nothing else. Nothing. Okay, that is not true. We also wanted to update the look and feel. We wanted to re-evaluate the text and make it more user-friendly. And we also wanted to make it easier for the IT admin to push out the items in the Exceptions folder. Okay, well that is it. Nothing else. Except we wanted to give admins a way to remotely update the Creative Suite apps. But other than that, nothing else. Really.

Let’s get into some specifics. How bad is this puffer fish and how are AAMEE 3.0′s de-puffer fish abilities? If you do a manual install of CS6 on a system the following will happen: An Adobe ID request will come up. Your end users HAVE to login with an Adobe ID account or they can’t use the software. Oh, that will be popular. Wait, the systems aren’t online or behind a secure firewall? Won’t work. Also, the systems HAVE to activate on a regular basis. Once again, not connected to the internet or behind an overly secure firewall? Won’t work. Now maybe you do imaging for your organization. You do an install on one base system. Login in with an Adobe ID and serialize it. Looks fine. Then you clone it to another system. Won’t work. There is now a relationship between the machine and the licensing in CS6. Let’s say you used a third party packaging tool like the venerable JAMF Composer tool. Guess what? Won’t work. No place within Composer to validate the Adobe ID or the online serial number validation.

Okay, so how well does AAMEE 3.0 reduce the pain of this puffer fish? First, using AAMEE 3.0 makes it so you only have to create/login with one Adobe ID on behalf of your organization therefore negating the need for your end users to have an Adobe ID at all or even know what one is. Second, the serial number is validated and activated within AAMEE 3.0. The end user’s system does not have to activate because you have already done it using AAMEE. Third and final, if you are imaging then AAMEE 3.0 has a special unserialized/trial workflow and a new serialization executable that can be used to serialize once the image has been applied to the machine. BAM! Puffer fish be gone!

I realize this is a weird product announcement. But I wanted to cover again our focus for this release as there has been a lot of reaction in the comments of previous posts. We really have gone out of our way to make sure these licensing and activation changes have the smallest impact to our enterprise customers. In a perfect world, AAMEE would of also removed the licensing-to-machine relationship all together, but that didn’t happen and I think we have an adequate workaround. Not awesome, but bearable. But the truth is, nobody likes change when there isn’t an obvious benefit for them personally. Like the time the construction on Highway 99 was going on and I had to do a massive reroute. I was grumpy. But then I realized that the reroute took me by one of my favorite bakeries so I could stop and get breakfast each morning. And there is no hidden bakery with the CS6 and AAMEE 3.0 release.

Okay, there is no hidden bakery but we did provide betas of our the new command line tools with this release: Exceptions Deployer application and Remote Update Manager which are pretty sweet and we’ll go in depth on them in another post. And we even put the Adobe Customization Wizard X in the Windows installer into AAMEE’s Utilities folder just to save time for IT admins who need to tweak their Acrobat install on Windows.

Give us the links already! Okay, but before I do, let me warn you that AAMEE 3.0 is only for CS6 media with a volume serial number. It does not work with CS 5.x media, eLearning Suite, TLS, etc. Just CS6. It does not work with retail serial numbers. AAMEE 3.0 and AAMEE 2.1 can not exist on the same system. That is my list of caveats, except the obvious one: AAMEE 3.0 should only be used for good, never for evil. Good and evil is very much on my mind as I am counting down the hours for another 3.0 release: Diablo III. Links Jody, give us the links!

AAMEE 3.0 Read Me

CS6 Enterprise Deployment Guide

AAMEE 3.0 FAQ

Adobe Application Manager, Enterprise Edition AAMEE 3.0 – Windows

Adobe Application Manager, Enterprise Edition AAMEE 3.0 – Mac

Thanks to the entire extended AAMEE crew for pulling together this release. I am very lucky to work with such a great team. And thanks Adobe for giving me the resources to put puffer fishes back into the ocean where they belong.

Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

129 Responses to AAMEE 3.0 for CS6 available now! Removes puffer fishes!

  1. Don Montalvo says:

    We don’t have authenticating proxies but I sure hope the new (re)activation process doesn’t cause production downtime if there ever is a reason the suite can’t call home. :)

    • Jody Rodgers says:

      You don’t believe me do you Don? You think that even though we remove the puffer fish there is still a hidden puffer fish in there? Using AAMEE 3.0 makes it so you DO NOT have to reactivate. Your end systems do not have to activate AT ALL let alone reactivate. The activation occurs only within AAMEE. There is no hidden puffer fish.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

    • William says:

      Heck with fish, the AAMEE only creates a silent install (which is great for our SCCM server) but not so great when we have a web install we assign license to and allow users to install on their own. Creation of a msi file allows you to use the qb switch to show an unattended install. If we are stuck to qn or silent install the users are left waiting and wondering when their install is actually finished… nearly there, but not quite.

      • Jody Rodgers says:

        We are looking into making an option to create a non-silent version of the msi for a future version of the product.

        Jody Rodgers | Senior Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

        • Why not use msi and give the choice to whoom it belongs? It works, we can use it, we want it. :)

          Q: What happens when I reinstall 150 computers, are those licenses lost? (like in CS5 before you got the message).

          • Jody Rodgers says:

            Native MSI would be ideal.
            A: In the volume license workflow of CS6 using AAMEE 3.x created packages the licensing example you provided is not relevant. Meaning, no, you do not lose licenses by uninstalling volume licenses. They can be repurposed.
            Does that make sense?

            Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

  2. Don Montalvo says:

    LOL…looking forward to deploying. :D

  3. Pingback: Adobe unveils CS6 and subscription-based Creative Cloud service

  4. Pingback: Adobe CS5.5 Master Collection Questions...

  5. Josh says:

    Just a grammar note: It’s “would have” not “would of” — if it sounds like someone is saying “would of” out loud, it’s because they’re actually saying “would’ve,” or the contraction of “would have.”

  6. Tom says:

    Does 3.0 still support CS5.x products?

    If it doesn’t, will I still be able to use the previous version with 3.0 installed?

    Thanks

    • Jody Rodgers says:

      No, AAMEE 3.0 only supports CS6. If you install AAMEE 3.0 you will not be able to use AAMEE 2.1. If you have to build packages for both CS 5.x and CS6 I suggest having at least one of them in a VM or on an OS on another partition.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

  7. Todd James says:

    I’m not sure what the official channel is for support for this tool, but I’m encountering what I think may be a bug in AAMEE 3.0.166.0.

    I’m trying to create a serialization file for After Effects CS6 for Windows after successfully creating and using serialization files for Design and Web Premium CS6, and Premiere Pro CS6.

    I selected the installation source (which is the copy of After Effects 11.0 Win that I downloaded from the Adobe LWS), specified a folder name and destination. I get the following error when clicking Next: “You have selected the 32 bit package option. Please provide 32 bit media or select 64 bit package option.”

    The problem is that creating a Serialization file doesn’t allow you to choose between 32 bit or 64 bit packages. I also did not receive this error with Design and Web Premium or Premiere Pro, which I believe are also 64 bit.

    Any ideas what the cause of this may be and a solution? Here is the log from PDApp.log:

    5/15/2012 11:10:36 [INFO] EnterpriseNative – ewa_browseForMediaInput retValue falseC:\Users\tjames\Desktop\Adobe CS6\After Effects\Adobe After Effects CS6

    5/15/2012 11:10:39 [INFO] EnterpriseNative – ewa_browseForMediaInput retValue falseC:\Users\tjames\Desktop

    5/15/2012 11:10:41 [INFO] Utilities – File does not exist
    5/15/2012 11:10:41 [INFO] Utilities – Folder does not exist
    5/15/2012 11:10:41 [INFO] Utilities – Folder does not exist
    5/15/2012 11:10:41 [INFO] EnterpriseNative – drivePath retrieved
    5/15/2012 11:10:41 [INFO] Utilities – Folder does not exist
    5/15/2012 11:10:41 [INFO] EnterpriseNative – ewa_validatePackageInputData : Max output length for package output calculated to 168.
    5/15/2012 11:10:41 [INFO] EnterpriseNative – ewa_validatePackageInputData : Max output length for ASU calculated to 202.
    5/15/2012 11:10:41 [INFO] EnterpriseNative – ewa_validatePackageInputData : Max output length for package msi calculated to 115.
    5/15/2012 11:10:41 [INFO] EnterpriseNative – ewa_validatePackageInputData : Max output length for Updates calculated to 178.
    5/15/2012 11:10:41 [INFO] EnterpriseNative – ewa_validatePackageInputData : retValue 101010

    5/15/2012 11:10:41.552 [INFO] EWA.FetchMediaInformationCommand Started fetching the payloads data
    5/15/2012 11:10:41.558 [INFO] EnterpriseNativeApplet Media Signature found as {4817D846-700B-474E-A31B-80892B3E92E3}
    5/15/2012 11:10:41.559 [INFO] EnterpriseNativeApplet Fetching the setup manifest from media
    5/15/2012 11:10:43.034 [ERROR] EWA.FetchMediaInformationCommand Unable to find the driver payload
    5/15/2012 11:10:43.034 [INFO] EWA.FetchMediaInformationCommand Finding driver in exception list
    5/15/2012 11:10:43.034 [ERROR] EWA.FetchMediaInformationCommand Driver is present in x64 exception list. This installer is not applicable for this machine

    • Rahul says:

      Hi Todd,
      This is a issue with 64 bit standalone product media (like After effects) but works fine with suites containing 64 bit products.
      Can you please use following workaround – create the “CS6 Installation package” (1st option on welcome screen) using After effects media. this workflow will allow you to select 64 bit option while package creation. Since this package contains serial number information, it will serialize the product during product deployment itself.

      I hope this workaround works for you. please get back in case you see an issue with this.

      thanks,
      Rahul | Lead Software Engineer | Adobe

      • Todd James says:

        Rahul,

        Thank you for your comment. Unfortunately, I don’t believe this solution will work for us, as we are installing After Effects (and the other CS6 products) onto an image and we use the serialization executables as part of a script to activate our Adobe products after the image has been deployed.

        Our scenario is unique in that we deploy images to laptops for our students by replacing the hard drives with pre-imaged hard drives (where activation for Design and Web Premium and Premiere Pro are done on each machine via a script that calls the serialization executables for those products).

        Is there a workaround to create a serialization executable for standalone 64-bit products? Or activate these products in some other automated fashion after they have been installed?

        Thank you.

        • Ben Matthews says:

          We have the same issue with After Effects where we deploy onto hundres of machines australia wide so being able to create an AE Serializaiton is imperative. Rahul, is there any update on this since this post?

      • Leon says:

        That workaround doesn’t work for Imaging! We can’t go around activating this on 500 machines!

  8. Mik Ayre says:

    Where do I go for AAMEE support as I am having a problem deploying the .pkg files. Mac using ARD and 10.7.3 target.
    getting the following in the logs.

    15/05/2012 16:51:55.096 installd: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 “An error occurred while running scripts from the package “UNN CS6 MAster Collection 2012_Install.pkg”.” UserInfo=0x7ffd7b201190 {NSFilePath=./preinstall, NSURL=file://localhost/private/tmp/ARD_PKG_ITEMS.cSDN0X/0017F20992A4.5091/UNN%20CS6%20MAster%20Collection%202012_Install.pkg, PKInstallPackageIdentifier=com.adobe.Enterprise.install.6ACCD070-57CC-4EA9-8787-1BF39BB35B7D, NSLocalizedDescription=An error occurred while running scripts from the package “UNN CS6 MAster Collection 2012_Install.pkg”.} {
    NSFilePath = “./preinstall”;
    NSLocalizedDescription = “An error occurred while running scripts from the package \U201cUNN CS6 MAster Collection 2012_Install.pkg\U201d.”;
    NSURL = “file://localhost/private/tmp/ARD_PKG_ITEMS.cSDN0X/0017F20992A4.5091/UNN%20CS6%20MAster%20Collection%202012_Install.pkg”;
    PKInstallPackageIdentifier = “com.adobe.Enterprise.install.6ACCD070-57CC-4EA9-8787-1BF39BB35B7D”;
    }

    • Rahul says:

      Hi Mik, Can you please share the PDApp.log and installer logs files for this deployment failure. this will help me understand the cause of this deployment failure.

      • Mik Ayre says:

        I have uploaded a zip file containing the logs to my drop box get it from https://www.dropbox.com/s/aqmmt1ekgijicqk/Adobe%20installer%20logs.zip

      • Mik Ayre says:

        Has anybody picked up the logs?

        • Mik Ayre says:

          I have uninstalled all previous CS suites, rebuilt the installer and tried again without success. This is from the PDApp.log.

          =======================================
          Mon May 21 14:58:30 2012 [INFO] PIM – PIMSqlite closeDB status 0
          Mon May 21 14:58:30 2012 [INFO] PIM – FREE PIM Instance …
          Mon May 21 14:58:30 2012 [INFO] DeploymentManager – Build Version – 3.0.168.0
          Mon May 21 14:58:30 2012 [INFO] DeploymentManager – Logging Level verbosity Set to 4
          Mon May 21 14:58:30 2012 [INFO] DeploymentManager – The return code from the Bootstrapper Process is (0).
          Mon May 21 14:58:30 2012 [INFO] DeploymentManager – Correcting Dependencies in local db.
          Mon May 21 14:58:30 2012 [INFO] DeploymentManager – STEP 4: Starting to launch Adobe Installer.
          Mon May 21 14:58:30 2012 [INFO] DeploymentManager – Obtained Adobe Common Folder Path.
          Mon May 21 14:58:30 2012 [INFO] DeploymentManager – Adobe Installer launch location is :: /Library/Application Support/Adobe/OOBE/PDApp/DECore/Setup.app/Contents/MacOS/Setup
          Mon May 21 14:58:30 2012 [INFO] AAMEEUtilities – Launch Process With Task
          Mon May 21 14:58:40 2012 [FATAL] DeploymentManager – The return code from the Adobe Installer Process is (19).Stopping the installation process.
          Mon May 21 14:58:40 2012 [INFO] DeploymentManager – Starting to clean the partially installed payloads.
          Mon May 21 14:58:40 2012 [INFO] DeploymentManager – Undeployment XML created at path :: /tmp/84F792A9-E6B9-464D-A9BC-7E2211A8BB35//F550FDB8-1416-4830-A9DF-859886A2C603
          Mon May 21 14:58:40 2012 [INFO] DeploymentManager – Starting to launch the Adobe Installer for uninstall mode.
          Mon May 21 14:58:40 2012 [INFO] DeploymentManager – Obtained Adobe Common Folder Path.
          Mon May 21 14:58:40 2012 [INFO] DeploymentManager – /Library/Application Support/Adobe/OOBE/PDApp/DECore/Setup.app/Contents/MacOS/Setup
          Mon May 21 14:58:40 2012 [INFO] AAMEEUtilities – Launch Process With Task
          Mon May 21 15:01:22 2012 [INFO] PIM-Uninstall – Build Version – 6.0.335.0
          Mon May 21 15:01:22 2012 [INFO] PIM-Uninstall – Logging Level verbosity Set to 4
          Mon May 21 15:01:22 2012 [INFO] PIM-Uninstall – Start: Adobe Application Manager Uninstall…
          Mon May 21 15:01:22 2012 [INFO] PIM-Uninstall – Get RIBS Product count
          Mon May 21 15:01:22 2012 [INFO] PIM-Uninstall – RIBS Products install status :1
          Mon May 21 15:01:22 2012 [INFO] PIM-Uninstall – There are some ribs products using AAM. RIBS product use flag is 1.
          Mon May 21 15:01:23 2012 [INFO] DeploymentManager – The return code from the Adobe Installer Process is (0).
          Mon May 21 15:01:23 2012 [INFO] DeploymentManager – The install workflow is terminating.

          =======================================

          Thanks in advance.

          • saransh katariya says:

            Hi Mik, The error code 19 means that some conflicting process is running on the machine and this is causing the installer to quit. More detailed information, as to which process is conflicting can be found from that product’s installer logs. If the problem persists, you may also consider rebooting the machine so that all the conflicting processes gets terminated automatically.

            While creating the package, there is an option in configuration screen where you can select the behavior of installation in case of conflicting process. You can either abort the installation or ignore the conflicts and continue. By default, its set to abort the installation.
            You can also attempt to create a new package with this option set to ignore the conflicting processes. But in this scenario, some components may not get installed properly.

            Thanks
            Saransh Katariya | Member of technical staff | Adobe Systems

          • Rahul says:

            Hi Mik,

            From logs extracts that you have pasted here, it seems that conflicting process is running on machine where you are trying to deploy this package. please close all process (at least adobe process) to install this package successfully.

            Logs Snippet that you have pasted (from PDApp logs) are correct. More detailed logs are saved as /Library/Logs/Adobe/Installers/.

            please provide this log also for detailed debugging.

            thanks,
            Rahul | Lead Software Engineer | Adobe

    • Mik Ayre says:

      I have now managed to deploy a cs6 package using ARD. I rebooted the remote Mac and ensured that no Adobe processes were running, and all went smoothly. Thanks for your help.

  9. Gary Knigge says:

    Hi. I found a problem with the exceptions recommendation in Design & Web Premium CS6.
    The file recommends (among other things)
    ###################################### Command to install Acrobat X Pro ######################################
    msiexec.exe /i AcroPro.msi EULA_ACCEPT=NO REGISTRATION_SUPPRESS=YES SUITEMODE=1 INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1 TRANSFORMS=en_US.mst /qn
    msiexec.exe /p AcrobatUpd1011.msp /qn

    But the last command throws an illegal command error from msiexec. The correct syntax would be:
    msiexec.exe /update AcrobatUpd1011.msp /qn

    Cheers,
    Gary

    • Tushar Bammi says:

      Hello Gary ,

      We have verified that the command: msiexec.exe /p AcrobatUpd1011.msp /qn
      works fine for the installation of Acrobat patch . However , the command suggested by you : msiexec.exe /update AcrobatUpd1011.msp /qn is an alternative way of applying a patch.
      Let me brief out the detailed steps to follow :
      1. Install Acrobat X using the command:
      msiexec.exe /i AcroPro.msi EULA_ACCEPT=NO REGISTRATION_SUPPRESS=YES SUITEMODE=1 INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1 TRANSFORMS=en_US.mst /qn
      2. Then , install the Acrobat 10.1.1 patch using the command :
      msiexec.exe /p AcrobatUpd1011.msp /qn

      If you are facing issues in running any of the above commands , please send the verbose msi logs to tbammi@adobe.com.

      MSI verbose logging could be enabled by appending /l*v to the command line.

      Thanks
      Tushar | Software Engineer | Adobe

  10. Don Montalvo says:

    It would be great if Adobe provided a forum for AAMEE users…and have the engineers monitor and be active in the forum. :)

    Don

  11. Mik Ayre says:

    The documentation says that from the Welcome Screen there is a modify package option. That option is not there on the Mac.

    • Rahul says:

      Hi Mik,
      Modify package option specified in AAMEE Deployment Guide is for AAMEE 2.1 workflow and not for AAMEE 3.0 workflow.
      Deployment guide posted on web is combined document and contains separate chapters for AAMEE 2.1 and AAMEE 3.0. Please refer to AAMEE 3.0 chapters for feature information of current version.

      thanks,
      Rahul | Lead Software Engineer | Adobe

  12. Kyle says:

    Just downloaded CS6 in our school to get ready for deployment in the summer. You really took out the ability to slipstream updates in the Adobe deployment? And you also took out the ability to modify a package in order to slipstream new updates into the package?

    • Jody Rodgers says:

      Kyle,

      Maybe? It is just temporary. We are planning on reinstating those features in AAMEE 3.1 which will be available in the second half of 2012.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

      • Adam says:

        Good Lord! Please, please, please bring back the ability to build a AAMEE update package. We have 40+ locations and setting up local web servers at each location is not an option. We cannot use a central server and WAN the updates either due to our network infrastructure. Building update packages was the best feature of AAMEE for us and without it AAMEE is literally useless for our [very large] organization.

        • Jody Rodgers says:

          Oh trust me, we know how lame it is that we pulled this feature for this release. I am pretty much the worst Product Manager in the history of Adobe. No plaque needed thank you. No seriously, it WILL be brought back in AAMEE 3.1. But let me clarify that you can use the new Remote Update Manager aka RUM run without having any AUSST configured local Adobe Update servers set up. By default, RUM will pull the updates from Adobe’s servers. Please try it out!

          I have to disagree with your assessment that AAMEE 3.0 is “literally useless” without the update feature. AAMEE 3.0 allows you to package the CS 6 software in custom configurations, disable the need for end users to have Adobe IDs, disable updates, disable the EULA, and disable the required activation. According to the customers I have spoken to, that stuff is far from useless to them.

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

          • Quinn Stewart says:

            I’m sorry Jody, I really don’t think you understand how lame this all really is, and how incredibly annoying it all is to the higher ed community. I just spent a half hour of highly paid, highly trained information searching skills to find your hidden bottle of RUM at
            http://labs.adobe.com/downloads/aameetools.html

            Now I have to see what it tastes like, and whether I want to swallow it or not.

            Running support for CS6 issues out of a crappy blog is juvenile at best, and I can find nothing from the AAMEE webinar posted yet.

            For the Mac CS6 Users out there, here are a few truths to save you time, money, and your own sanity.

            1. You can use AAMEE to create a package that can be installed via Absolute Manage (LANrev) that will install CS6 without all the GD nagging for Adobe ID’s and serial numbers.

            2. However, you can’t then use the software itself to update itself.

            3. So my third day of dealing with this pufferfish-up-my-ass debacle will now be spent drinking RUM. You can use the link I posted to get a bottle of this stuff for yourself. If you are a Mac user with a command-line allergy like myself, you should probably get a real bottle of rum to get through this. OH, and it’s a public beta, which usually means alpha, so you might need two bottles of rum. Yo ho ho, I”m feeling all piratey now, let’s see now, AAMEE, what you gonna do, I think it’s time to uninstall you, for a while, maybe longer…….

            PLEASE treat us law-abiding, enterprising, voluminous educational users who train thousands of Adobe software users with a little more respect.

            Literally useless, no, AAMEE has some real benefits.

            PITA? The P stands for Pufferfish, you will experience the rest.

            Q

          • kagibson says:

            Hi Quinn,
            Sorry to hear you are unhappy with some of the changes in CS6 and our response to them. We have tried to keep the community in the know, both in advance of CS6 and post release. The Webinar we hosted was heavily attended and there was lots of great questions asked, because of this we intend to host more events in the future. We also continue to tweet updates through our @Adobe_ITToolkit and offer support through the Enterprise Deployment Forum http://forums.adobe.com/community/download_install_setup/creative_suite_enterprise_deployment

            Regarding the long search for the new Remote Update Manager tool, we did provide a link to it on the blog, under the Jamf Composer section. However you are correct it should be more prevalent and we will address this. We will also be creating a blog entry specifically on this topic in the near future. RUM does have a command line interface as it is designed to be remotely initiated through a 3rd party deployment tool and this allows greater flexibility. Please let us know how your testing with the tool guys. I think it will be of huge benefit to IT admins.

            Again thank you for your feedback, good or bad we take it onboard.

            Cheers
            Karl (Jody will be returning soon)

          • Don Montalvo says:

            $h!t happens when you’ve got a lot of people working on a complex project and you’re faced with a tight deadline. Something’s gotta give.

            We have departments asking us to get CS6 deployed, but we’re pushing back pending release of AAMEE 3.1, since we can’t deploy unpatched software.

            Hoping to see an ETA soon so we can set client expectation.

            PS, Jody, you know we know you know you’re one of the most valuable project managers in the Mac IT community. ;)

            Don

          • Quinn Stewart says:

            Hey Karl,

            Twitter? Seriously? If I wanted to tweet, I’d get a canary. I try to pay attention to the old saying, “Just because you can, doesn’t mean you should”.

            What I need is documentation, examples, answers. A nice HOWTO. How about a webinar that’s indexed and searchable? Yeah, there were a lot of great questions, but anyone paying attention knows that AAMEE 3.0 is beyond beta, and never should have been released without update capabilities. More than a few folks seems to have shared this sentiment. “Heavily attended” webinars usually signal desperation among those trying to get some work done, knowing that once again, the Adobe Ship has changed course.

            Please keep in mind I’ve been hitting the RUM today, in my ongoing debacle to deploy CS6 on my Macs, and with my well-earned command line allergy. Surely a company that can make Photoshop can do a better job than this? I”m missing the days when Photoshop came on 24 3.5 inch floppies, it certainly installed faster than this AUMAUSSRUMAAMEE edition.

            So, real info from the real world, buried in a blog. Ya’ll feel free to move it to a more helpful location. It’s only Day 4 of “lets install CS6!”

            So, I called in a few favors from our most highly respected and valued sysadmin about this whole command-line bottle of RUM. The first muttering I heard was something like “rm -r Adobe” or something like that. Eventually we determined the following:

            1. “Installing” RUM dumps a Unix executable and man page update at the root level of the hard drive.

            2. Even if you are logged in as an Admin, you still have to sudo to make the darn thing run, from the directory where it is installed.

            3. So, for me on a Mac, running Terminal, I have to first

            cd / (to move to the root directory)

            cd Remote\ Update\ Manager/ (to navigate into the installed directory where the script is)

            sudo ./RemoteUpdateManager (to run the script, and yes, even if you are logged into an Admin account, you still have to sudo and put in the admin password)

            Once you hit Return or Enter at the command line( you have been doing this, no?) sit back in your best Johnny Depp pose, arrgh a few times, and find a real bottle of rum, you earned it.

            The good news- RUM works, fast, and leaves a trail in /Library/Logs

            The bad news? Day 5 will involve trying to get RUM and AbMan to do this unattended.

            For the really geeky out there, the aameetools RUM also has a man page you can install, that mentions that, by the way, you gotta sudo this puppy. The EXAMPLE in the aameeetools_rum_docs.pdf file neglects to mention this little tidbit, and the Example it gives as a command to invoke Codename Remote Update Manager

            RemoteUpdateManager

            won’t get you anywhere unless

            1) you use sudo
            2) you are in the same directory as RemoteUpdateManager
            3) you use the command ./RemoteUpdateManager

            Man, I miss the days of double-clicking a file. I really thought that would catch on.

            Stay tuned for Day 5, where AbMan and RUM hopefully have a baby named “where did all these nice updates come from without me asking for them?

            Thanks Karl, but I really think there needs to be a single birdless, blogless, engineer and documentation-writer moderated forum called “Deploying Adobe CS6 in an academic environment” rather than a “lets throw this over the fence and let them figure out how to use it” approach.

            AAMEE and RUM have some impressive software engineering going on, in the name of protecting the Adobe gold from the pirating masses. With over 15 years of installing Adobe software in an academic environment, I”m beyond tired of getting caught in the crossfire. Please take notes for CS7.

            Q

          • Rahul says:

            Hi Quinn,

            You dont need to cd to folder where RUM is placed. Just specify the absolute path of RUM and run with sudo command.
            it needs to run in sudo (elevated) mode because updates are downloaded and “installed”. Hope you were able to install updates using RUM.
            Feel free to write to me if you face any issues with updates installation using RUM.

            thanks,
            Rahul Baiswar (mail: rbaiswar@adobe.com) | Lead Software Engineer | Adobe Systems

  13. Jeff says:

    HI, I have a couple of questions. From the documentation, I see:

    “The packages you create with the Application Manager have no UI (MSI), or only a default UI (PKG). You should not attempt to install them directly (for example by double-clicking the MSI or PKG file). You must use a third-party tool such as ARD or SCCM to deploy them.”

    We really need to use ARD to deploy these in OSX? I understand that these packages are payload-free, with scripts handling the real actions in the package. By we really can’t install them from a GUI on a client system?

    • Jody Rodgers says:

      Jeff, on the Mac the outputted AAMEE package is just a standard package that the system can read and you can do a manual click through installation. Works fine. Only caveat is that the status bar indicator of how much time is remaining is ridiculously off. It will grow larger and larger and not show an accurate representation of how long the install time is, at all. It is basically a bug.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

      • Jeff says:

        Thanks Jody, that is what I figured. Good to know.

      • Mark says:

        I figured this much out for myself on the Mac. However, what about Windows? Is there a way to do the equivalent for Windows 7? I can’t double-click the MSI. I can’t even seem to run it in /passive mode so that the progress bar shows.

        We don’t push apps, but would like a way to distribute with the serial number and an adobe ID already included.

        Incidentally, the Acrobat tools much more closely emulate the kind of behavior I’m looking for with a package customizer. All I really want is to include is the serial number (and the adobe ID, in this case, since it’s included) and maybe a few minor customizations. AAMEE does “too much” in my case.

        Thanks,
        Mark

      • Sara says:

        Jody: I used AAMEE 3.0 to create a deploy package for CS6 for Windows 7. I am also seeing that the Time Remaining in the progress window is very very off. Is there a fix for this? Thanks!

        • Jody Rodgers says:

          When you are making the packages?

          Jody Rodgers | Senior Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

  14. Nick says:

    I successfully created a Master Collection CS6 deployment, but when I run msiexec.exe /i “Master Collection CS6.msi” /quiet REBOOT=ReallySuppress, it just hangs without using any cpu.

    Since my test box is a Windows 7 machine, I tried to look at C:\Windows\Temp\PDapp, but it didn’t appear to write anything there.

    Any advice?

    • Jody Rodgers says:

      Nick,

      What is the actual deployment method/solution you are using to push these out to systems?

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

      • Nick says:

        We /will/ be using LANDesk, but for now I’m just trying to test out the installer on its own.

        • Jody Rodgers says:

          Please test out the AAMEE produced package with LANDesk and let us know if you are seeing issues.

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

          • Nick says:

            I don’t understand–if I deploy it with LANDesk, all it’ll be doing is run automatically the same command that I was running manually, how would it make a difference?

          • Nick says:

            Deploying it from LANDesk works, but I still don’t see why I can’t do it manually. We would still like for our technicians to be able to manually run the deployment file so they wont need the license key, which we’ve been able to do with both CS4 and CS5.

          • Zeb says:

            I’m able to install Photoshop CS6 from the command line by using msiexec.exe /i “Package from AAMEE.msi” /qn with no problems.

        • Sachin Porwal says:

          Hi Nick,

          Thanks for confirming the installation with LANDesk. Please note that the AAMEE created packages are Pseudo installers, it is normal to show very low cpu utilization for ‘msiexec’ processes. Normally it takes 20-30 minutes for the whole CS6 Master Collection deployment, please wait till the ‘msiexec’ processes quit. You can monitor the progress by observing the regular updates in logs at:

          PDApp logs : %temp%\PDApp.log (if msi is run from logged-in user account) or [BootDrive]:\Windows\Temp\PDApp.log (no user logged in)
          Installer logs : %programfiles(x86)%\Common Files\Adobe\Installers\.log

          Please share the exact steps & PDApp.log/Installer log, if the logs are not getting created/updated for a long time.

          Thanks,
          Sachin Porwal | Computer Scientist | Adobe Application Manager Enterprise Edition | Adobe

    • Tushar Bammi says:

      In case if you are deploying the MSI by running the command on the machine itself (without using any tool/deploying when client is logged out) , then the logs would be created at user temp location.
      Please send PDApp.log present at location %temp% to tbammi@adobe.com so that we can look what happened with the installation
      Incase if MSI is installed with no user logged in on the client machine , then the logs get created at [BootDrive]:\Windows\Temp

      Also , please ensure that command prompt is launched with administrative priveleges before running the command.

      Tushar Bammi | Software Engineer | Adobe

  15. CJ says:

    So, for those of us who have enough machines in a multi-OS environment where we ordinarily clone computer images, but not enough machines to have ever needed to run SCCM, ARD or any similar package deployment tool…?

    • Jody Rodgers says:

      Then I recommend trying out the Serialization Executable as a “first-run” script once the image has been laid down onto the system. Are you using any first-run scripts at the moment? Can you describe your imaging process?

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

      • CJ says:

        No, never used first-run scripts.

        For the PC side, we create a master image and then use UDPcast or Clonezilla to clone every computer on the network that needs to be cloned (lab environment) or disk dump for individual PCs.

        • Jody Rodgers says:

          And you have no mechanism of delivering files to systems?

          Am I to assume you do no patching of the systems during the semester/quarter?

          Once the image is on the system does someone sit down at each system to verify that the image was applied correctly, logged onto the system to verify the network connection is working, etc.?

          What about for the Mac side?

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

          • CJ says:

            Correct. We currently do not use a mechanism of delivering files to systems.

            We set them to do automated patching, but yes, we generally do a reimaging each semester.

            Once the image is on the system, someone sits down at each system to verify that the image was applied correctly, set names/IPs, etc.

            On the Mac side, we clone the disks using (I believe) the regular Apple utilities.

      • Les says:

        I’ve been running tests with a Serialization Executable via a “first-run” script on a Win7 64-bit OS (as a Boot Camp partition) with mixed results. When I apply a copy of the sysprep’ed image with the script & package to a new machine and start it up, everything appears to run as it should (ie. no error msgs), BUT, when I launch any of the Adobe Products, they still think they’re Trial versions…. until I restart the machine, launch a product and wait a minute or two (or three), and then — magic! Serialized version. Any suggestions as to why this occurs?

        • Jody Rodgers says:

          Hello. So sorry for the delay. That is rather strange and I doubt magic is involved. Sounds more like gremlins. I’ll discuss with the team and if they have any insight we’ll let you know.

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

  16. Don Montalvo says:

    Hate to be a pest, but have we designated the “official” AAMEE 3 support forum? We’re training new Mac Packagers, so we need to point them to a good resource.

    Thanks,
    Don

    • Jody Rodgers says:

      A support forum for Adobe CS enterprise deployment has been in the works but is not live. At this time this blog and the @Adobe_ITToolkit Twitter account get you direct access to the AAMEE engineers. If your organization has an active Support contract with Adobe you can contact Adobe Support for official support as well.

      As far as pointing them to good resource, look no further then the CS IT Resources page where they can download the thorough CS6 Enterprise Deployment Guide:

      http://www.adobe.com/products/creativesuite/it.html

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

  17. Jim Kirkum says:

    Can you provide information on where the information related to the machine-license tie-in exists? I am planning on managing using Radmind, so if I know where this location exists on the machines, I can just set an ignore rule for the file/directory where this information lives. I am guessing /Library/Application Support/Adobe/Adobe PCD but would like confirmation before spending all my time deploying, only to be back to having them all run in trial mode. Or is that not necessary, if I have created AAMEE packages already using the 3.0 tool along with our CLP Volume license codes and organizational email address? I plan to use the products with KeyServer.

  18. Jim Kirkum says:

    Just for the record -

    1) I created AAMEE installers that included the license # and email address.
    2) I captured the installation using Radmind.
    3) All machines come up asking for the license # and email address again.

    How can resolve issue #3 without having to touch each machine individually? Also, Radmind updates the machines (e.g. rolls them back to the previous state) each time they reboot.

  19. Jim Kirkum says:

    I figured out some workarounds and posted my results to the Radmind list, so you can disregard and/or delete my previous posts.

  20. Angry Admin says:

    Awesome tool. /s

    Creates the PKG file successfully, but then fails to install on exactly on 100% of the machines using ARD.

    The time I spent screwing around with this would have been better spent manually installing this on every machine in my office.

    Stupid question time: Why don’t you guys make an Apple compatible PKG file yourself instead of turning your paying customers into beta testing engineers?

    • Don Montalvo says:

      “Stupid question time: Why don’t you guys make an Apple compatible PKG file yourself instead of turning your paying customers into beta testing engineers?”

      …it’s an industry trend…pass the cost to the customer. Microsoft is doing the same thing. Build it cheap, let it loose, wait for complaints, fix the biggest issues…rince, lather, repeat.

      I agree 100% regarding Adobe’s insistence on using proprieteary installer technology vs following Apple guidelines.

      Don

  21. Angry Admin says:

    It get even better! Since the PKG installer automatically fails using ARD, I tried installing it manually on one of my target machines. Install completes successfully, yet no CS6 applications appear anywhere!

    Nothing at all appears in /Library/Logs/Adobe/Installers

    This tool is completely unusable.

    ———

    After further testing it appears that deselecting some of the apps when creating the PKG causes the ARD install to fail. Copying the PKG to the target machine and manually installing succeeds according to the installer, but no CS6 apps appear anywhere.

    Including all apps when making the PKG will install successfully using ARD, but again, no CS6 apps appear in the Applications folder, and no log files appear anywhere.

    Seriously brilliant you guys. Bravo.

    • Jody Rodgers says:

      Sorry you are having issues. Please report this to the new Creative Suite Enterprise Deployment forum:

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

      Please provide us with as specific background info as possible such as version of ARD, OS version, settings that were selected in AAMEE, etc. We’d also be curious if you have packaged CS 5.x media with AAMEE 1.x-2.x and deployed it in your environment in the past successfully and if anything has changed since that time (i.e. proxy or firewall changes.)

      And for the record, ARD has always been part of the core of our Quality Engineering process with AAMEE.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

    • Rahul says:

      If you are not able to see any logs in /Library/Logs/Adobe/Installers, then can you please share PDApp logs created at – ~/Library/Logs.
      If target machine is in logged out mode, then PDApp logs will be created at – /var/root/Library/Logs/PDApp.log

      About Application not visible after installation, this happens only if we do custom installation.

      • Rahul says:

        About Adobe application not visible after installation in /Applications folder, this happens only if we do custom installation. If no custom location is specified while package creation (on config screen), then Application should get installed in /Applications folder.

        please email logs to rbaiswar@adobe.com

        thanks
        Rahul Baiswar | Lead Software Engineer | Adobe

  22. Jeff Arris says:

    I run a network of 800 PC’s and we’ve purchased a volume site licence for 250 users of Adobe Creative Suite 6 Master Collection. We create disk images which are rolled out using Windows Deployment Services (WDS). With CS3 we just installed the software to the image and all was simple.
    I had planned, after reading up, to install AAMEE and create a custom install which I could put on the master image and duplicate to the PC’s as we image…..from reading the posts above this seems like it may not be the route to go….
    We don’t have SCCM and either install our existing software on the build, roll it out using Group Policies OR install it manually when needed.

    How do you suggest we roll out 200 copies of CS6 to fresh images of Windows 7 64bit?

    Regards

    • Daniel says:

      Hi Jeff. I have a similar issue. I think, from what I understand, the best way is to create a Trial Deployment and the Serialize file. You install the Trial Deployment to your image and add the Serialized file somewhere on the image also. After each machine deployment you have to run the serialized file. I am just going to create a script that runs it on startup then delete the file off the machine. That should activate the trial into a full version. I think! Going to test today.

    • Kyle says:

      I’m curious as to why you are installing CS6 on a master image and not deploying the application via an application task sequence if your using WDS?

  23. Pingback: Rolling out Adobe Suite 6 Master Collection to 200 windows 7 PC's

  24. Dave says:

    Forgive me if I missed this somewhere… but to prepare a package for Mac, I have to use the AAMEE for Mac? Our users are all Mac, but our IT staff is all PC. In fact, the designers are the only Macs in the whole directorate.

    • Rahul says:

      Hi Dave,

      AAMEE package to be deployed on mac machine – these packages need to be both created and deployed from mac machine.
      Same is applicable for windows.

      thanks,
      Rahul Baiswar | Adobe Systems

  25. Kildare says:

    Re-packaged MC6 with 3.0 & currently get this error when attempting to deploy via SCCM…

    “Windows Installer per-user elevation of this program (“PRI00089″ – “Install – Adobe Master Collection 6.0b”) failed for advertisement “PRI20077″.This program was started. Please check the status of this program to determine whether or not it was completed sucessfully
    Possible causes: The version of Windows Installer on the computer is less than version 2.0, or the setup program does not support Windows Installer per-user elevated rights installations.
    Possible solutions: Update the version of Windows Installer on the computer to version 2.0 or later, or contact the software vendor that supplied the install program to determine if a version of setup that supports per-user elevated rights is available.”

    Previous MC6 package created with 2.1 installed fine – minus activation issues.

    • Tushar Bammi says:

      Hello Kildare ,

      Could you please also share some more details regarding the deployment -
      1. Logged in User (Administrative/Standard/LoggedOut)
      2. Rights with which Program Ran (User’s/Administrative)

      Tushar Bammi | Software Engineer | Adobe

      • Kildare says:

        Thanks Tushar,

        This advertisement is set to run only when users are logged off with administrative rights.

  26. saransh katariya says:

    Hi Jeff,

    If you create disk images and duplicate to the PC’s, the ideal way for you should be –

    1. Create a trial package using AAMEE. As you have mentioned that the machines in your organization are 64 bit windows machines, remember to select 64 bit option on welcome screen while creating your package. If any of your machines are 32 bit then you must create a different package for 32 bit machines. A package created for 64 bit machine should not be deployed on 32 bit machines.

    2. Deploy the trial package to all the machines.

    3. Create a serialization executable using AAMEE. Run this executable on all the machines where trial package was deployed. This will serialize the product. Remember to run the serialization executable to all the machines after deploying the trial package.(Do not run it on the image itself).

    Thanks,
    Saransh Katariya | Member of technical staff | Adobe Systems

    • saransh katariya says:

      hi Jeff,

      Just a small clarification for the second point above. When I asked you to deploy the trial package, I meant to deploy the trial package on a machine and create an image of it. Then use this image to roll out on other machines.

      Thanks,
      Saransh Katariya | Member of technical staff | Adobe Systems

  27. Daniel says:

    When I run the Serialization Executable I get “Return Code = 0″. What does this mean? Is there a directory of what the return code mean? thanks

  28. Jim Kirkum says:

    Is it possible to combine a bunch of prov.xml files into one master prov.xml file? I just have like 6 different ones, and it would be nice if I could run the AdobeSerialization executable against just one file, if it can work that way.

    • Rahul says:

      Hi Jim,

      I understand that combining the prov.xml file and running AdobeSerialization with just one file with ease maintenance of these files, but that will not work. Prov.xml file has certain structure and AdobeSerialization understand particular structure only.

      thanks,
      Rahul | Lead Software Engineer | Adobe System

  29. Very happy to have stumbled on this de facto help forum. I have nearly gleaned what we, completely new to AAMEE, might have to do. But I hope for some hints to build our plan.

    We have a classroom of Macs, on which we run Windows via Bootcamp (I hope to switch to VMWare Fusion this year if performance is adequate). Students like not having to adjust to a different OS when they’re learning Adobe software. The Mac side is imaged with System Image Utility and deployed with ARD–mostly good and easy-ish. Windows we clone with Winclone, and we move that image to client machines also with ARD. Never have used SCCM.

    We rebuild machines from the images we make after every class.

    Trying to come up with a procedure for creating the Windows MSI, deploying it without a Windows server, and getting it installed on our Win side so we can clone ‘em. Whether we’re talking Virtualization of Bootcamp, I’d love advice or being pointed at the right resource.

    Thank you.

    • kagibson says:

      Steve,
      I am glad the forum has been of use to you. Regarding your current workflow, I am not sure if you already seen it on the forum but with CS6 there is now a relationship between the client and the license and so using Winclone or SIU to clone the machines will cause a problem if performed in the normal way. What you would have to do is either build standard packages with AAMEE and on the MAC just push out through ARD. On Windows if you do not have a deployment tool perhaps you could leverage AD or login scripts ? if you need to continue cloning then you should use AAMEE to create a trial package, install it on the master machine, configure and clone the master while still in trial and then push it out to your clients. You can then create a serialization package with AAMEE to change the clients into serialized mode, again by leveraging ARD or scripts.

      Also please check out the Enterprise Deployment Forum for additional resources and to ask questions

      Cheers
      Karl

  30. John says:

    This is just one more reason that I absolutely loath using Adobe products and recommend open-source alternatives whenever possible.

  31. James says:

    For a Mac volume license, can’t we just have users download and install the correct trial version and then send them a script or the like to run to strip the activation, serialize it and remove all nag screens? This would help tremendously with home installs.

    • James says:

      Can’t we also run the same script/command via ARD to trial installs onsite?

    • kagibson says:

      James,
      You can use AAMEE 3.0 to create a serialization package that will change the trial into full mode and remove the requirement for the Adobe ID and activation. The serialization package can be deployed via ARD or another 3rd party deployment tool. Alternatively you could change it into a double click executable that user’s could run.

      Cheers
      Karl

  32. Brandon says:

    I’m trying to create a package via AAMEE, version 6.0.335.0, to push out CS6 Master Collection to all of our Macs, but I’m not able to get AAMEE to accept the serial number. I keep getting a “The serial number you entered is invalid. Please try again. If the proflem persists, contact Customer Support.” I can install the software just fine manually so the serial number works, but AAMEE doesn’t accept it. I called and I keep getting bounced around from group to group, hung up on three times now. Who do I call for support with this issue?

  33. sk says:

    Is this “AAMEE” product a cousin of the crazed and defective robot in the movie “‘Red Planet?” I think so. You have to install Adobe Acrobat first…? Oh…thanks I just figured since it showed up as part of what was being packaged that it would actually install.

  34. sk says:

    My license key which I used to create the CS6 package in AMEE doesn’t work with the Adobe Acrobat product when I try to install that…from the same disk…..any thoughts?

    • kagibson says:

      SK,
      Can you provide a bit more detail ? So you have created a CS6 package with AAMEE that contains Acrobat ? and when it is deployed it is not working ?

      Cheers
      Karl
      CS Enterprise Systems Engineer

  35. Hi all,

    Just some tips on my deployment:

    I updated to CS6 and haven’t had too many problems – CS6 used my existing Adobe Update Server (for CS5x).
    I created two Windows Packages, a 32bit and 64bit with our serial number. (AAMEE 3.0.166.0) – probably old now.
    I also created a Mac Package. (AAMEE 3.0.168.0)

    The first stumble is that I had to create the Windows package on a Windows, and a Mac on the Mac (the Windows AAMEE wouldn’t let me create a mac package)

    For the windows machines I placed the package on a URL share and scripted the command: “\\URL\sharename\package.msi /quiet” to install the package silently in the background. (fortunately I have remote access to all our clients so it looked like it installed locally)
    The Mac I just single clicked the package manually as these are wireless and take forever to download the package – so some where installed via USB stick.

    I have also now installed SCCM and have windows update deployment working, however the manual listed here is for 2007 and I am using 2012….
    At some stage can a manual be written for SCCM 2012 deployment? as it is quite a bit different from 2007.

    I will test some deployments via SSCM, but a manual in 2012 would also help.

  36. john KC says:

    hi,
    i’m running a lab of 400 diskless desktops, where each PC OS is streamed from datacenter upon each reboot. The OS is refreshed upon each reboot to golden state.

    Q1) if i proceed with AAMEE3.0 method, where trial version of CS6 is installed in the golden image. all clients will obtain the golden image with CS6 trial installed.
    Q2) during the bootup of the clients, i can let it run the serialization file. however, as the OS is always refreshed to golden state upon each reboot, it will always go into trial mode
    Q3) is there a file/folder directory that CS6 store the license detais. I believe if i were to keep it persistent it will solve this issue

    • john KC says:

      hi,
      we have tested deloying using aamee 3.0 and it works.
      however, i am wondering does the CAL/client License wll be reduced (-1) everytime the diskless pc reboots?

      imagine 400pc reboot twice a day, it would use up our license in half a day.

  37. pcamis2 says:

    Jody, et al… thanks for all of the information presented here. One item that I believe is missing from the AAMEE deployment method is the ability to customize settings (such as possible in deployments from Autodesk for their architectural products). Specifically, I’m looking to be able to change the default color suite settings (as I currently have to do manually in Bridge for each user). Might this be incorporated into a future AAMEE release (or is there a way to do this now via registry setting, GPO, etc.)? Thanks again!

    • Jody Rodgers says:

      Hello. That is indeed missing from AAMEE and it is missing from our Enterprise Deployment documentation on how/where to find those prefs and package them up through an alternative method, like JAMF Composer. This has been something that has been in conversation for awhile now and your comment is a good reminder that this would be a valuable addition to AAMEE or at least to our documentation to start with! Many things for bringing this up.

      Cheers,

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media

      • pcamis2 says:

        Much obliged, Jody – thanks for the reply! Two items I found while searching for info have proven helpful…

        Photoshop Preference File Locations:
        http://helpx.adobe.com/photoshop/kb/preference-file-names-locations-photoshop.html

        CS6 Color Preference File location (Win7):
        C:\Users\%username%\AppData\Roaming\Adobe\Color\ACEConfigCache2.lst

        Doesn’t seem as though the latter filename/location is documented anywhere, and it is exactly what I was looking for. Another user in the forums (cserban3) has written a script to push this and other preference files out to workstations. Could be a good place to start.

        Again – thanks for the great info!

  38. Joe says:

    Thanks, adobe, for acting like you’re doing us a favor by coming up with a work around for a problem adobe created. Honestly – like we dont have enough problems with adobe products. I swear acrobat 5 ran with less issues than todays programs. No, you had to throw this on top. As if MS didnt mess up with needing /re arms all the time, now we have to worry about coming up with scripts to serialize an already prepped enterprise install? Everytime? Killing me, especially on xendesktop prepping. Cant wait for CS6.5 and AAMEE 3.1 and 3.2 and 3.3….. Why doesnt adobe focus on fixing issues instead of creating more? Can you still not even work on a network file in 5.5? Who’s running the show at adobe?

    • Joe says:

      Oh – and why not just include AAMEE with the enterprise downloads? Why make us try all this (which lets face it – IT ppl try before they read), then realize it doesnt work, then go searching for a solution, to find out – we’re just going to have to uninstall or redo the image completely. You’d think adobe would put its enterprise (volume) customers first. Not act like we should be happy about this – that just adds insult to injury.

      • Jody Rodgers says:

        Joe,

        Good honest feedback. Regarding: why not just include AAMEE with the enterprise downloads?
        AAMEE is available as part of the CS downloads in Adobe’s Licensing Website (LWS.) Did you not see it when you downloaded your copy of CS?

        Jody Rodgers | Senior Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

        • Jim says:

          It’s often someone in Purchasing, not IT who downloads the installers!

          • Jody Rodgers says:

            Indeed. We’ve identified this an ongoing issue in the purchase lifecycle. We are definitely open to suggestions on how to make the process better so the IT admin get this info they need to start deploying.

            Jody Rodgers | Senior Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

  39. Jim says:

    Sorry… Adobe Help is the BIG puffer fish this time around! Installing it using the supplied instructions just flat doesn’t work!

  40. Thomas says:

    So I was loving this thing until I got the case to install two editions of CS6 on a image and then use the serialization to activate them once deployment is finished. But it seems that with the activation script the only edition that gets serialized is the last one the scrip runs. So the command to activate the edition using the AdobeSerialization.exe and the prov.xml both created with this new tool only works with the last of them run.

    Will this be fixed in some later version, so that people who have both Design and Web Premium and Production Premium can deploy both edition together on the same system without worrying about activation not working on both?

  41. Shell says:

    Just installed the Master Collection CS6 on a PC using AAMEE. Acrobat X was not installed. I looked at the package again and the option was checked when I created the original package. How can I install Acrobat X? Do I need to run the package again? This new process is so tedious.

  42. Shell says:

    Never mind. I contacted Support. Acrobat X needs to be installed from the Exceptions folder, using a script.
    It would be nice of Adobe to send install instructions and Xanax, or similar.

  43. Karthikeyan M says:

    Hi,

    When I launch Illustrator CS6, Bridge CS6, Media Encoder CS6 in other user accounts, it crashes while launching. These apps works only in user who installed the AAMEE 3.1 created CS6 package. When I installed manually through Adobe Setup from DMG, it works fine. Am I doing any mistake or suggest me any work around.

    Regards,
    Karthikeyan

  44. Tim says:

    We need to create a deployment of CS6 on systems with no internet connection… I don’t want to get each team member to grab the license key, and then go online (on separate internet machines) to get an activation code that works for 72hours.

    I simply want to say to my team, ‘go and double-click the deploy package’ and it will silently install exactly like the Autodesk stuff does… complete with license key entered for them.

    It seems the adobe help centre can’t help me AT ALL… or even know what I’m talking about. So, currently, the AAMEE tool will ONLY work with a machine that has the internet… how can I get round this? Why can’t I do an offline activation to make my deployment???

    Any help would be more than awesome!

    Tim

    • Jody Rodgers says:

      AAMEE 3.1 is the answer to your needs. However, the individual who packages the software has to be online. There is no offline usage state for AAMEE. You have to be online to validate the Adobe ID and the volume serial number. The double-clickable installer that AAMEE 3.1 produces and the products themselves will be able to run offline.

      Hope that helps.

      Note, in the future you might want to post to the Enterprise Deployment Forum:
      http://forums.adobe.com/community/download_install_setup/creative_suite_enterprise_deployment

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

  45. Derek says:

    I am trying to install a CS6 package and I am getting the following Error I am using the Casper Suite to install this as part of their FirstRun process:


    Mar 28 11:27:33 dbrost installd[2128]: PackageKit: ----- Begin install -----
    Mar 28 11:27:33 dbrost installd[2128]: PackageKit: request=PKInstallRequest
    Mar 28 11:27:33 dbrost installd[2128]: PackageKit: packages=(
    "PKJaguarPackage "
    )
    Mar 28 11:27:33 dbrost installd[2128]: PackageKit: Extracting file://localhost/Library/Application%20Support/JAMF/FirstRun/PostInstall/Resources/Test%20DW%20Prem_Install_CS6.pkg (destination=/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandboxManager/1.sandbox/Root, uid=0)
    Mar 28 11:27:33 dbrost installd[2128]: PackageKit: prevent user idle system sleep
    Mar 28 11:27:33 dbrost installd[2128]: PackageKit: suspending backupd
    Mar 28 11:27:33 dbrost installd[2128]: PackageKit: Executing script "./preinstall" in /Library/Application Support/JAMF/FirstRun/PostInstall/Resources/Test DW Prem_Install_CS6.pkg/Contents/Resources
    Mar 28 11:27:33 dbrost install_monitor[2184]: Temporarily excluding: /Applications, /Library, /System, /bin, /private, /sbin, /usr
    Mar 28 11:27:33 dbrost installd[2128]: ./preinstall: AAMEE Installer : preinstall launched...
    Mar 28 11:27:33 dbrost installd[2128]: ./preinstall: AAMEE Installer : Working directory is /Library/Application Support/JAMF/FirstRun/PostInstall/Resources/Test DW Prem_Install_CS6.pkg/Contents/Resources
    Mar 28 11:27:33 dbrost installd[2128]: ./preinstall: AAMEE Installer : Launching AdobeDeploymentManager...
    Mar 28 11:28:46 dbrost installd[2128]: ./preinstall: AAMEE Installer : Exit code of AdobeDeploymentManager is (79)
    Mar 28 11:28:46 dbrost installd[2128]: ./preinstall: AAMEE Installer : Exit ...
    Mar 28 11:28:46 dbrost install_monitor[2184]: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr
    Mar 28 11:28:46 dbrost installd[2128]: PackageKit: releasing backupd
    Mar 28 11:28:46 dbrost installd[2128]: PackageKit: allow user idle system sleep
    Mar 28 11:28:46 dbrost installd[2128]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “Test DW Prem_Install_CS6.pkg”." UserInfo=0x7fa8749013b0 {NSFilePath=./preinstall, NSURL=file://localhost/Library/Application%20Support/JAMF/FirstRun/PostInstall/Resources/Test%20DW%20Prem_Install_CS6.pkg, PKInstallPackageIdentifier=com.adobe.Enterprise.install.16E39691-8195-4009-92A3-9858A31A0FE9, NSLocalizedDescription=An error occurred while running scripts from the package “Test DW Prem_Install_CS6.pkg”.} {
    NSFilePath = "./preinstall";
    NSLocalizedDescription = "An error occurred while running scripts from the package \U201cTest DW Prem_Install_CS6.pkg\U201d.";
    NSURL = "file://localhost/Library/Application%20Support/JAMF/FirstRun/PostInstall/Resources/Test%20DW%20Prem_Install_CS6.pkg";
    PKInstallPackageIdentifier = "com.adobe.Enterprise.install.16E39691-8195-4009-92A3-9858A31A0FE9";
    }
    Mar 28 11:28:46 dbrost installer[2165]: install:didFailWithError:Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “Test DW Prem_Install_CS6.pkg”." UserInfo=0x7fd211823380 {NSFilePath=./preinstall, NSURL=file://localhost/Library/Application%20Support/JAMF/FirstRun/PostInstall/Resources/Test%20DW%20Prem_Install_CS6.pkg, PKInstallPackageIdentifier=com.adobe.Enterprise.install.16E39691-8195-4009-92A3-9858A31A0FE9, NSLocalizedDescription=An error occurred while running scripts from the package “Test DW Prem_Install_CS6.pkg”.}
    Mar 28 11:28:47 dbrost installer[2165]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
    Mar 28 11:29:06 dbrost installd[2128]: installd: Exiting.

Leave a Reply

Your email address will not be published. Required fields are marked *


five − 3 =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>