Karl Gibson's team just announced Creative Cloud Packager

[donmontalvo]

https://jamfnation.jamfsoftware.com/viewProduct.html?id=238

[rickgmac]

Quiet a few bugs to be aware of.
http://helpx.adobe.com/creative-cloud/packager/ccp-readme.html

[tkimpton]

lets hope they dont screw up the licensing with a dodgy update again!!!

[donmontalvo]

Well, not exactly what we had hoped for...please see my post to the AAMEE forum. I also sent an email to Jody Rodgers, Karl Gibson and Victoria Selwyn (our saviors):

http://forums.adobe.com/message/5343600#5343600

Hi Karl, It's a logistical issue in many large environments where IT has to vet all software requests. In order to vet Creative Cloud, IT has to be able to test. In order to test, we need to have access to the tools, source and appropriate dev licensing. Vetting includes functionality (does it do what our users, groups, departments and subsidiaries need), vulnerability (does it run properly with our anti-virus solutions; does it REALLY need to call home, some environments have restrictions against just that, etc.), packaging (does your tool create a proper zero-touch deployable package meaning can it be pushed to logged off Macs), deployment (we need to test deployment to the different department build configurations, OS'es, etc.), license management (are we able to manage licensing internally, as some environments have strict bans on applications "calling home")...the list goes on.... At the current time IT is "locked out", unable to properly vet Creative Cloud, so it is on the "not approved" list, as per corporate policies and procedures. Many of us in IT have been involved with AAMEE (APTEE, RUM, etc.) from their inception, however it appears Creative Cloud was conceived, designed and released without our involvement. With that said, there is no way for us to proceed, so our Firms are in a holding pattern. Hopefully Adobe can resolve this IT access issue so enterprise firms that have these mandatory controls in place can properly vet and deploy software in our environments. Thanks, Don

[tkimpton]

Well said Don. Until this is addressed properly I'm advising management to not invest in to it. Push all you like Adobe but at the moment it's not gonna get you anywhere.

[donmontalvo]

@tkimpton Karl's reponse addressed all my concerns...

http://forums.adobe.com/message/5345601#5345601

Hi All, I spoke with Don on the phone yesterday and hopefully resolved some of his fears, which I believe many share. What I would like to make clear is that Creative Cloud Packager as of right now is for Creative Cloud Team customers not Enterprise. Team is based on smaller deployments and requires users to sign in to license applications and be online every so often to validate. This is not scalable for enterprise. I believe the majority of you are IT admins for Enterprise and not Team and so this is why I have not reached out to provide access to Creative Cloud Packager. Our Creative Cloud Enterprise customers at this moment in time still use AAMEE which everyone has access to. Information has not been terribly forthcoming lately and so I understand the confusion and the feelings that we are "locking out" the very IT admins that have always helped the AAMEE team, however this is not the case. Over the next few weeks I will be providing more information on the Blog which should give a better understanding of the direction of the IT Tools. Cheers Karl Product Manager | Enterprise IT Tools

[donmontalvo]

Version 1.3 was just released...

http://blogs.adobe.com/oobe/2013/10/creative-cloud-packager-1-3-is-live.html