Sneak Peek of AAMEE 3.0

Adobe unveiled our new Creative Suite 6 and Creative Cloud offering today. And with that news, you as an IT admin probably have one question in mind: Why me? That’s right, the burden is square on your shoulders to package and get this new set of products into the hands of your users. But don’t worry, we’ve got you covered. Got your back. We are there for you. Would we leave you hanging? Okay, historically you could say that we have in fact, left you hanging. So to speak.  But let’s not dwell on history. In fact let’s not even dwell on the present. Let’s talk about the future. Far, far into the future. Imagine a time where people can communicate to anyone in the world or by the use of a computer that fits in their pants pocket. That’s right, I am talking about the year 2012. Imagine it is a week after CS6 is available for download on the Adobe Licensing Website and now imagine another blog post from me where I spend a long first paragraph not exactly getting to the point and eventually tell you that AAMEE 3.0 is available to download.

What is this AAMEE 3.0 that you speak of that will be out a week after CS6 ships? It is the third major release of the packaging tool called the Adobe Application Manager Enterprise Edition, but we call it AAMEE because we are risk of getting carpal tunnel for typing the whole name out. AAMEE 3.0 was made specifically to handle the CS6 media to prepare it for deployment by outputting it as a customized MSI or PKG. A special version of the product has been developed for the new licensing features of CS6 because we are trying really, really hard not to make your job harder than it is or impact your users. If you got the CS6 media and tried to deploy it without the use of AAMEE 3.0 then things will not go smoothly for you. You see, we have specifically designed this release so that your deployment of CS6 is enterprise friendly and so you don’t write me nasty emails or post mean spirited comments. Using traditional methods of packaging CS without AAMEE, doing manual installs, or creating images without the use of AAMEE 3.0 will lead to an excessive amount of unnecessary cursing. You don’t want that. We don’t want that. Are you seeing how you and this AAMEE 3.0 tool need each other?

We will go into the details of the AAMEE 3.0 release in the next couple of weeks in different posts, specifics about the new licensing and activation, and we will discuss and preview two new command line tools that will make your life easier. But for today, I just wanted to show you a quick sneak at the welcome screen of AAMEE 3.0. It has a simple and clean interface and is laser focused on doing one thing: packaging and licensing CS6. But wait, what about support for older versions of CS or other suites like Technical Communication Suite? What about support for packaging updates? What about the support for updating an exiting AAMEE package? Oh. Did you notice that? Would we do that? Would we take functionality OUT of a product? Would we do that to you? Um. Look over there! Is that an ice cream truck I hear? Okay, look, I have been straight with this community from day one. So let me say Y-E-S! I’ve broken the first rule of Product Management which is to not take features out that people like and use.

Now before you get your rotten tomatoes out let me tell you we already have a section of the AAMEE engineering working on a 3.1 release that will add some of the missing functionality. AAMEE 3.0 will meet the basic needs of IT admins supporting early adopters of CS6. In fact, it rocks at that. It straightforward and quick. In the second half of 2012 we will have a 3.1 release that will add some of the lost features. Well “lost” sounds like we simply misplaced them. That would not be accurate as we know where we left them, in AAMEE 2.1. Ha. That made me laugh. So, my work is done here.

Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite & Creative Cloud | Adobe Systems

59 Responses to Sneak Peek of AAMEE 3.0

  1. Don Montalvo says:

    …..droooollll….

  2. Jeff Bernstein says:

    I guess this would be less of an issue if we were able to have 2.1 and 3.0 installed at the same time. Hint clue.

    • Jody Rodgers says:

      Hey Jeff! You’ve been surprisingly quiet of late. So I can tell you that it is not possible to have 2.1 and 3.0 installed on the same machine. If you need to package both CS 5.x and CS6 then I recommend putting it on different systems/partitions/VMs. Hard to say how high that is on the lameness meter.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite & Creative Cloud | Adobe Systems

  3. Dan says:

    You feel better after going to confession, don’t you?

  4. Dan Zimmerli says:

    Can you comment on wether it will work with Mac image creation tools such as InstaDMG?

    • Jody Rodgers says:

      Pretty much… no, at least for a straightforward InstaDMG workflow. If you put an AAMEE 3.0 produced package into an InstaDMG workflow it will indeed fail. I worked with Joe Chilcote in Adobe’s Desktop Support (who knows InstaDMG fairly well) to verify it and I saw it fail with my own two, well four, eyes. Now there is probably ways in which you could get a monolithic image to work. But you would probably have to deploy it out unserialized (in Trial mode) and then you serialize it with the new Serialization Executable workflow or using APTEE.

      Just to be upfront as possible, we do not include image creation in our Quality Engineering (QE) process. We only do our QE work currently through deployment tools. Nothing against InstaDMG. At all, in fact I even had a beverage with Allister Banks the other day. Nice guy and a hero in the community for taking on the stewardship of that project.

      Once you have CS6 and AAMEE 3.0 in your hands we would love to work with you and find out your results and work with you to find a solution. And there may be some significant hurdles because there is a connection between the machine and the licensing. So a serialized CS6 install on one system can not be block copied to a dmg and then dumped onto another machine. Another solution would have to be put in place. We are more than happy to work and share workflows with the community around imaging as they emerge. This release will involve some change in workflows and we will work with the community on making this as smooth as possible and sharing what we find.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

      • Doug Lawhead says:

        A clarification, please, on this in your reply… “Just to be upfront as possible, we do not include image creation in our Quality Engineering (QE) process.” So are you saying, if I use AAMEE 3.0 to deploy CS6 to a lab’s model computer, image that computer, and then push the image to the lab I will have issues with CS6?

        • Jody Rodgers says:

          Yes, if you serialize it you will have issues because the CS6 licensing has a machine-specific relationship. This is new with CS6. So the advice we are proposing is that the image be created in an unserialized/trial state and the serialization should occur after the image is applied to the machine. Does that make sense?

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Don Montalvo says:

            The provisioning tool should allow you to script serialization, no?

          • Jody Rodgers says:

            Yes indeed Don. Same for the new Serialization executable.

            Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Doug Lawhead says:

            No, it makes no sense. How do I serialize it on each machine afterwards? Do I have to do touch every one of my 300 Macs? How will this affect concurrent licensing (a ton of us, including my campus) uses Keyserver.

  5. Guillermo Saint Lary says:

    Saw CS6 was available today via our enterprise portal and am downloading the Suite installers now. Was hoping to play with this over the weekend. I understand this does not work in AAMEE 2.x. When can we expect to see AAMEE 3.0?

    Also we us Munki and DeployStudio here. Do you know if AAMEE 3.0 generated packages are compatible with those?

    • Jody Rodgers says:

      AAMEE 3.0 will be posted on our DevNet and CS IT Resources page on 5/14. If we are able to make them available earlier on the Adobe Licensing Web Site we will post something on this blog and our our @Adobe_ITToolkit Twitter account.

      Munki and DeployStudio workflows have not been tested by our team for this release. As stated in the previous comment above, we are more than willing to work with the community that supports and uses those tools to find best practices and recommendations that we can share with everyone either here on this blog or through shared documentation.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

      • Guillermo Saint Lary says:

        Thanks for the fast reply. Will look forward to AAMEE on 5/14.

        Will the Adobe ID also need to be embedded within packages created with AAMEE 3? I just ran an install test using the standalone Prod Premium dmg and it requires an Adobe ID to be entered within 7 days. The difficulty in our department is that only IT can have access to that info since we don’t want the users having access to serials. Can we create a dummy Adobe ID be created for inclusion in the package if needed. We don’t want users to be able to login with our official company ID.

        • Jody Rodgers says:

          Yes, AAMEE 3.0 will require the IT admin to create or use an Adobe ID on behalf of their organization, one that specifically states their organization’s name. So no “dummy” Adobe IDs please as there may be repercussions down the road, especially if you end up using that Adobe ID to manage subscriptions within your organizations. We understand fully that many organizations do not want Adobe IDs to be used for their end-users. So with AAMEE 3.0, the IT admin is doing this on their organization’s behalf. We also realize that your end-users may behind a secure firewall or might even be offline. That is why using AAMEE 3.0 automatically grants that install package the ability to be used offline sans-activation. Keep in mind that although AAMEE 3.0 packages are granting this exception to online activation, the licensing of CS6 is still tied to the machine it is installed on. This means traditional monolithic imaging will not work. We have tested this using the basic clone features of Disk Utility on the Mac OS and sure enough it does not work. The ideal situation is to push out the AAMEE 3.0 package as a post-imaging solution.

          Hope this makes sense. It is late on Friday afternoon and it has been a long week. ;-)

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Art Vandelay says:

            What about having a monolithic image with an AAMEE 3.0 install on it and then running the Serialization execution workflow as a post-imaging step to “fix” the licensing for other Macs?

          • Jody Rodgers says:

            If you have an unserialized/trial install created from an AAMEE 3.0 package in the image and then run the Serialization executable as a post imaging script or post deployment step…that should work. I’ll try and get Joe Chilcote to help out verifying that. Joe is our Mac imaging guru in Adobe’s IT department. Joe? Are you cool with that?

            Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Doug Lawhead says:

            Sounds like you are assuming all organizations have ONE and only one IT manager. This will be a nightmare on our campus.

          • Jody Rodgers says:

            No, we know that many organizations have decentralized and even autonomous IT groups in different areas of campuses/schools within colleges. And in the corporate enterprise side of things it is very common to have IT groups for each regional office. This is the case to some degree with Adobe’s own IT which I came from. Please elaborate how having to serialize after the image is applied will be a “nightmare” for your campus. I am more than happy to give you a call today as well to learn more.

            Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Steven says:

            Jody,
            Would it be possible to get a blog post or some other going into a bit more detail how the Adobe ID piece would work with AAMEE so that I don’t need my individual AdobeID tied to each machine (in case I’m not always the one creating the packages)?
            Thanks for the updates!
            — Steven

          • Jody Rodgers says:

            Great idea Steven. We should have a post just about the CS6 licensing changes. But to quickly address your question, one suggestion is to create a joint email account for your IT organization and use that. Let’s say you are Joe Admin and you work for a company called Example in their Desktop Support group in Kentucky. Example buys 50 copies of CS6 Master Collection. Joe has to manage the PC training labs but his co-worker Mark has to create images for the Mac marketing folks. They both have access to the Adobe Licensing Website but have different reasons to be using AAMEE 3.0 to package CS6. They could create an email account called dts_kentucky@example. com and then use a password like whi$k3y$0uR for use in their Adobe ID and would indicate Example as their company. This way, Mark and Joe could both use the same login credentials and create packages in unison and harmony. Until Joe becomes the manager and then asks Mark to manage the training labs AND do the imaging while Joe plays Call of Duty with his buddies.

            Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Joe Chilcote says:

            Jody – I can help test the serialization-after-monolithic imaging approach. Can also try out the DeployStudio scenario. One question for the commenters: for DS are you using the deferred package method, or something else? I don’t have a Munki environment to test but with the brain trust behind that open source project I would be surprised if there is no patch forthcoming.

            Hit me up this afternoon or tomorrow. And bring your orange drive. Also I don’t appreciate the COD comment. I mean, I would *never* give Mark access to our corporate ID.

          • Jody Rodgers says:

            That was a HYPOTHETICAL scenario. I was not talking about you Joe Chilcote in that scenario, but Joe Admin. Besides, you guys never play COD.

            Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Doug Lawhead says:

            Here is my elaboration on how this will possibly be a nightmare on our campus. We use Keyserver and have concurrent licensing for our Adobe products (and several others). The way things have worked here is… The Keyserver admin is responsible for downloading the installers for all the software licensed via Keyserver. He puts images of those installers on a share that only authorized lab administrators and tech people have access. The lab admins go to that share and and get the installers they need and build the labs then work with the Keyserver admin to make sure licensing is correctly done. That Keyserver admin has the Adobe ID for the campus and it is not shared, so is he going to have to do the serialization on ever computer on campus that has an Adobe product installed? Now, it sounds like we can still follow our current installer distribution method only the Keyserver admin will need to use AAMEE to make the installers so the Adobe ID and licensing info is included. Fine, we can do that, but with CS5.5 I saw about a 15 percent failure rate of installers made with AAMEE and that concerns me.

      • D. Halz says:

        I’m attempting to use AAMEE v.3 to register machines prior to DeployStudio imaging. It doesn’t work. It appears that Adobe intends us to clone the machines and then deploy the AAMEE created package. This more than doubles the time of install for a single machine, and adds a whole new level of complexity to our imaging process.

        This is not reasonable. Ask Symantec what happens when the software aint worth the overhead… Hint: People find another piece of software.

        If there isn’t a major change in the licensing process for CS6, this will be the last iteration of the software we purchase. It’s not worth the headache.

  6. Constantin Serban says:

    So, when will it be available again? I only saw the “one week after …” note but about an exact date?

    • Jody Rodgers says:

      Sorry, we are targeting May 14 as the actual release date for CS6 was today. There was a newer blog post on Friday about it.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

  7. Benn Gardiner says:

    For those of us who solely use monolithic imaging – surely there must be SOME way to manage this for CS6?

    We require changing the scratch disk location for Photoshop and Illustrator which AAMEE does not seem to offer, as well as the location of start menu shortcuts, not to mention having to deploy a 5GB MSI to 250+ computers in addition to re-imaging them.

    Is there a solution for the likes of us?

    • Jody Rodgers says:

      Benn,

      Please see my comment above regarding the monolithic image.

      Preferences/settings are not configurable or able to be packaged using AAMEE. Preferences could be written via scripts as a post-installation or imaging step, but I am afraid I do not have specific guidance on this front. We are more than happy to promote solutions that the IT community find.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

      • Tim Kimpton says:

        Hi Jody

        We also use a seperate disk for the Photoshop and Illustrator scratch disk. Trying to get this as default is very difficult. Also if there ARE was to script this please can you share this? Also I agree every time a new CS come out we HAVE to reimage the machines. I understand what your saying about monolithic images but we talking about real works here!

  8. Amoreena Farrell says:

    Jody,

    Could you elaborate a bit more on machine authorization and how this will affect concurrent licensing? Will I still be able to install software on as many computers as I want and meter the concurrent licenses with KeyServer?

    • Jody Rodgers says:

      We are working with our partners at Sassafras and will provide more info on support for KeyServer once they are completed with their testing.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

      • Anthony Reimer says:

        I didn’t know that Creative Suite supported KeyServer! We’ve used it for passive licence management (e.g., to quit idle copies) but not authorization. Is it your intent with CS6 to let KeyServer users manage the authorization with KeyServer rather than the machine-specific serialization of which you speak (e.g., by use of a .lic file)? My licence is an education volume licence (CLP, I believe).

        I use a hybrid InstaDMG/DeployStudio image creation method to deliver the 110 GB payload we require (77 GB compressed). Package-by-package installation is just too slow. Since we have CS upgrade subscriptions, I will have the choice to install CS6, but right now it sounds like we would be better off staying with CS 5.5 unless KeyServer can let us skip the punitive individual serialization you have described.

        • Jody Rodgers says:

          If you go to Sassafras’s Technology Partner we are the first company listed! Okay, that is because the list is alphabetical. To be honest, I am not a Sassafras expert by any means and I recommend reaching out to your Sassafras account manager or contact for clarity around CS6 and KeyServer usage.

          I am not sure I understand what you mean by wanting to “skip the punitive individual serialization you have described.” First, machine specific licensing was not created to punish IT admins who wanted to image systems. Running a post install script with the new Serialization executable or APTEE should be a very minor thing to put in place and will take a second to execute.

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

          • Anthony Reimer says:

            All copy protection mechanisms are punitive towards legitimate users by definition, not just IT admins. Machine-specific ones are punitive towards educational labs and other volume licensees, as they require extra management (often including deauthorization before you redeploy or make hardware changes). It might be a small punishment, but it is a punishment nonetheless and one I do not have to endure if I stick with CS 5.5. You can trivialize how much work this new scheme is going to create for me, but in the end I have to do the work.

          • Tim Kimpton says:

            Please provide a detailed white paper on CS6 package creation and serialisation. Instead of sifting through a blog post.

            Thanks

          • Jody Rodgers says:

            Tim, the CS6/AAMEE 3.0 Enterprise Deployment Guide is a 150+ page document that is available on LWS at the moment in the same download area as AAMEE 3.0 and covers package creation and serialization in depth. It will be on the CS IT page and the DevNet page on 5/14 on the official release date of AAMEE 3.0.

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

  9. Ben Toms says:

    Hi Jody,

    Will the CS6 suite activate behind a proxy that requires authentication?

    Also, is there a limit on the amount of licenses an “Adobe ID” can be tied to?

    For those of us using a modular imaging workflow.. Can we install CS6 on 1st boot & silently activate using our businesses adobe ID?

    • Jody Rodgers says:

      Good questions Ben.

      re: Will the CS6 suite activate behind a proxy that requires authentication?
      If you use AAMEE 3.0, you, the IT admin, are the only one that needs to activate the software which is done from within AAMEE 3.0. If a proxy is encountered during the activation process a dialog comes up allowing you to authenticate. The end user’s systems do not need to activate because you have done it on behalf of your users.

      re: Also, is there a limit on the amount of licenses an “Adobe ID” can be tied to?
      No, an IT who is using their own Adobe ID or an Adobe ID on behalf of their organization can create a package that can be deployed to an infinite number of systems.

      re: Can we install CS6 on 1st boot & silently activate using our businesses adobe ID?
      Yes, via the new Serialization executable. So in that example, you would want to make sure the AAMEE 3.0 produced package was setup in trial mode.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

      • Ben Toms says:

        Thanks Jody.

        1) is the same for PKG’s & MSI’s?

        We do not do concurrent licensing & are looking at upgrading all our licenses to CS6 on all platforms for parity this year.

        Some are software assurance, others updates.

        So from what you’ve said @ 1. Not much has changed for us.

      • Tim Kimpton says:

        Hi Jody

        The proxy prompt authentication box is there but even after authenticating it doesn’t work!

        Please work on using system settings.

        We use a proxy pac file and i have tried manual settings.

        Luckily i have a seperate network i can plug in to but i shouldn’t have to do this.

  10. TGB says:

    Does AAMEE still generate PKGs that are 20 folders deep and filled with symlinks and/or aliases?

    Cos with CS5/5.5 and earlier AAMEEs, that usually goes badly and we need to re-wrap the Adobe PKG into our own PKG, use _our_ PKG to put _Adobe’s_ PKG somewhere (eg: /tmp) and then run “installer” on it via postflight/postinstall.

    • TGB says:

      By way of explanation, we use Casper with SMB and HTTP-based distribution points. Raw AAMEE PKGs take about 5 times longer to download all the loose, individual tiny files than a single large Archive.pax.gz (or whatever), and alias/symlinks copied up to the distribution point over SMB won’t download properly via HTTP to the client. Our users reported a bunch of broken InDesign plug-in errors as a result of this (since AAMEE just copied them loose into the overall PKG, rather than packing them up into an archive, DMG, zip file or anything else), so they were installed corrupted and incomplete without their correct structure.

    • Jody Rodgers says:

      Yes, still same levels of folders and symlinks which can be problematic on a few different fronts.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

  11. Don Montalvo says:

    For security/legal reasons it isn’t going to be possible to use a corporate email account:

    “But to quickly address your question, one suggestion is to create a joint email account for your IT organization and use that.”

    As long as it’s OK to use a Gmail account, shouldn’t be an issue.

    Don

    • Jody Rodgers says:

      The key is really to capture your organization’s name.

      Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Creative Suite + Creative Cloud | Adobe Systems

  12. Tim Kimpton says:

    First Impressions…not good

    Created pkg of CS6 Standard with AAMEE3.0 ignoring errors tick box selected.

    Pushed out through ARD with user logged in and failed.

    Pushed out through ARD with NO user logged in and failed.

    Point and click install is successful.

    Jody are we going backwards….

    • Jody Rodgers says:

      Tim, I am having a our lead Quality Engineer, Rahul Baiswar, send an email with a request for getting more info and your AAMEE log. Let’s get to the bottom of this and the proxy not working, straight away!

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

    • Jody Rodgers says:

      Tim, one thought, since you have a proxy in place that requires manual authentication, did you make sure to disable the AIR components? This will hang up the install process if not disabled in that scenario. Please see the Enterprise Deployment Guide for more details.

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

  13. Amir Bozorgzadeh says:

    How do I uninstall 3.0? I installed it and now need to go back to 2 and it is erroring out on the install. I figure a complete uninstall will alow me to do this. Thanks.

    • Rahul says:

      Hi Amir,

      Yes, AAMEE 2.1 cannot be installed over AAMEE 3.0. We are working on tool to uninstall AAMEE 3.0 (or later versions) which will help cleaning AAMEE from machine and allow installation of previous versions of AAMEE.

      For now please take backup (rename it) of “PDApp” folder in
      Win – Program Files\Common Files\Adobe\OOBE\
      Mac – /Library/Application Support/Adobe/OOBE/

      and then install AAMEE 2.1.

      But please ensure that you dont have any creative suite products installed on machine, else there functionality will break with this change.

      Hope this helps!

      thanks,
      Rahul Baiswar | Lead Software Engineer | Adobe System

  14. Oh my goodness! a tremendous article dude. Thanks Nevertheless I am experiencing issue with ur rss . Don’t know why Unable to subscribe to it. Is there anybody getting equivalent rss drawback? Anyone who is aware of kindly respond. Thnkx

  15. Karthikeyan M says:

    Installing the Exceptions like Adobe AIR, HELP and Dreamweaver in Mac using the ExceptionInfo.txt command line, CHC and Dreamweaver Widget prompts for proxy authentication. Is there any way to suppress it?

    • kagibson says:

      Hi Karthikeyan
      Yes this is expected behaviour and is one of he reasons we advise disabling these components in the main package if you have a proxy server. The components by default look to connect to the Internet there is no way to tell them not to. If you wish to install them then you will need to enter the proxy formation. This is something we are looking a providing a solution to but nothing exists at the moment.
       
      Cheers
      Karl Gibson
      CS Enterprise Systems Engineer

  16. Stebo says:

    I am having alot of trouble building a Cs6 package to deploy in our environment. I have used AAMEE to build the msi. I have wrapped the msi in our deployment tool and used this comman lind to launch the mis msiexec.exe /i “Adobe Cs6.mse” /quiet REBOOT=ReallySuppress. The deployment tool we use here is owned by flexera called managesoft. When i lauch / deploy the package it runs , stages the files and launches the msi. It starts and just goes away. I looked at the PDapp.log and it has [FATAL] Setup – Administrative Privileges required to continue 10/14/2012 16:06:52 [FATAL] Setup – End Adobe Setup. Exit code: -10

    Problem is that the deployment tools runs all the packages as “system” that is the highest privlege on a windows computer. (this is windows 7 by the way) . Can you please help!!!

  17. Stebo says:

    Thank you Jody for your responce :) but when i click on that link i get -> The Adobe Community Forums are being updated check back later

Leave a Reply

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


six + = 14

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>