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