CS 5.5 and AAMEE 2.0 on LWS

Although it is a slow process apparently, email notifications are starting to go out to our enterprise customers who have access to CS 5.5 through LWS this week. If you are unfamiliar with LWS, it is our Licensing Web Site for Adobe Volume Licensing (AVL) customers. It is also where order history, serials, and downloads of our electronic media reside. How about that name LWS though? Nothing says “relic of a bygone era” like a site with the name Web Site in it. Let’s just pretend the WS in LWS stands for Walking Shoes or Western Saddle. How about Worcestershire Sauce? I am fully aware that Licensing Worcestershire Sauce makes no sense, but I am somehow more okay with an absurd name than an overtly redundant one.

I just got word this morning that Adobe Application Manager Enterprise Edition (AAMEE) 2.0 has also made its way up to LWS as well! This is a whole week ahead of our scheduled release to the public website. How awesome is that? On the Scale of Awesomeness I would give it a 7 out of 10. Why not higher? Well I would give it a 9 of 10 if we were able to have AAMEE 2.0 available on our public DevNet site today as well, but we’ll have it up this time next week and I will post when this occurs with the link. How could it be a 10 out of 10 on the Scale of Awesomeness? This would involve simultaneous availability AND free candy. The free candy bit would bump it up. Don’t underestimate the power of free candy. They made a whole holiday based on it.

Related links:

Adobe Licensing Website (LWS)
https://licensing.adobe.com/

Adobe Volume Licensing (AVL) FAQ
http://kb2.adobe.com/cps/100/1003400.html

Jody Rodgers | Senior Product Manager | Enterprise & Volume | Creative Suite

3 Responses to CS 5.5 and AAMEE 2.0 on LWS

  1. Thanks Jody. The gathering of updates works great. Saves a lot of time and missed updates.

    One small issue I think I found on the Windows version: when browsing for the source directory, it does not show mapped drives. But If I map a new drive while the browse window is open it will show up. But then on the next package I create, the mapped drives won’t show up again unless I map a NEW drive.

    • Jody Rodgers says:

      That is actually a new issue we have not seen but have been able to verify. The team has logged a bug on this.

      Rahul Baiswar on our team wrote the following:
      there is workaround to this – user can manually browse to this location and copy paste the path to “product install folder path” input box. He will be able to package the media present at any network location.
      _________

      Thanks for sharing this with us, much appreciated!

      Jody Rodgers | Senior Product Manager | Enterprise & Volume | Creative Suite

  2. Dave Castelletti says:

    The feature to slipstream current updates into the deployment packages is great, but why isn’t it checking against my local update server? I’m creating deployment packages with the Overrides file in-place (and it works with my actual CS applications). Would it be hard to apply the Overrides file to AAMEE as well?

Leave a Reply

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


nine − 9 =

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>