We are creating installation packages for the new Creative Cloud 2015 release, for use by our higher-education faculty and staff. We have the appropriate volume license; an ETLA, I believe. We use Creative Cloud Packager (CCP) to produce Mac OS X installer packages, which we then distribute using a software management solution, like JAMF Casper. We build one package for each application (Photoshop.pkg, FlashPro.pkg, PremierePro.pkg, etc.), and three "bundles" that roughly resembled the CS6 bundles - Master Collection.pkg, Design and Web Premium.pkg, and Production Premium.pkg. When creating the package, we disable the Creative Cloud application and the use of Adobe Update Manager to manage updates. We use RemoteUpdateManager behind the scenes to update the software. AdobeID's created by our faculty and staff are not associated with our volume license, so the Creative Cloud application is of little use, since (to the best of my knowledge, at least) the application requires a Creative Cloud subscription in order to run.
With the new release, any Mac OS X package we build that contains InDesign or InCopy 2015, and installed on a Mac OS X 10.10.x system (I will be testing on 10.9.x tonight and tomorrow) will display the following error message:
"Adobe Creative Cloud is need to resolve this problem. However, it is missing or damaged. Please download and install a new copy of the Creative Cloud from 'http://www.adobe.com/go/adobecreativecloudapp'."
The package was rebuilt from scratch in CCP to make sure the Creative Cloud application was disabled; when this new package was installed, the system restarted, and either application started, the application still prompted for installation of the Creative Cloud app. The prompt would not be displayed if InDesign or InCopy is quit and is started again during the same login session. However, the first time either application is started after restarting, the Adobe Creative Cloud missing prompt is redisplayed. Other applications start normally without displaying the prompt.
No other package that we've built for the Creative Cloud 2015 releases exhibits this behavior.
Packages built for the original and 2014 Creative Cloud releases do not exhibit this behavior.
Please advise. Is this a bug in the InDesign and InCopy applications?