Adobe Systems Incorporated

Adobe Installation and Licensing

Blog to post all Installer and Licensing related info to users of Adobe products

Oct 1, 2015

CCP 1.9.2 is now live and I am trying to recover from MacSysAdmin

Hi All,

I have my feet firmly back on Irish soil after a few great days at MacSysAdmin in Gothenburg. I must say it is a very unique and engaging conference. The level of knowledge on display is quite impressive and that very much extended to working with Adobe products. After my presentation in which I requested for IT admins to continue to engage and work with us there was several very engaging discussions which will hopefully lead to new functionality and fixes.

While I was presenting and playing pool in Gothenburg the team was hard at work and we released CCP 1.9.2 yesterday. The main focus of this release was on proxy support. Previously while Pac was supported there was some issues and we also did not support WPAD. Both of which are now fully supported and from our preliminary tests with customers this build looks to have solved all of the issues customers were experiencing with these network topologies.

CCP 1.9.2 now also includes the option of Auto-updating. This can be set from the preference menu and when there is a new update of CCP you will also see a screen requesting your preference.

Finally with the introduction of El-Capitan we were required to change the location of RUM on the client system to conform with Apples new guidelines. As such, when we deploy RUM now from a CCP package it will be located in “/usr/local/bin”



Karl Gibson | Product Manager | Enterprise IT Tools

Creative Cloud


  • By John Welch - 4:09 AM on October 1, 2015   Reply

    Congrats, and thank you for the timely ElCap update!

  • By Shane Palmer - 3:33 PM on October 9, 2015   Reply

    So is there a way I can build a package to just update RUM as opposed to updating all 30 packages we just built a month ago with CCP? Not to mention I will need to update existing installations of RUM on all of the Macs that already have Creative Cloud 2015 installed before those users upgrade to OS X 10.11 and I would rather not have to push out large CC apps again just to do this.

    Also, when RUM gets installed in the new location is it smart enough to remove the executable from the old location?


  • By snovak - 9:52 AM on October 22, 2015   Reply

    I’ve discovered that yous can modify the ccp file (which is just an XML file) and modify the /usr/sbin entries to /usr/local/bin by hand, and then re-run the packaging process.

    You can also go into the PKG’s and modify the optionXML.xml file the same way and the installer respects it.

    So for those of you who don’t want to re-run all of the packaging processes, you can probably do
    find ./ -name “optionXML.xml” -exec sed -i ” ‘s/RUMDeployLocation\>\/usr\/sbin/RUMDeployLocation\>\/usr\/local\/bin/’ {} \;
    against the directory where all of your CCP packaging took place and that should go through and update them all. Then you’ll just have to copy them back up to your file distribution points so clients run the updated installers.
    You can also do the same thing while looking to *.ccp to update all of the creative cloud packger files.

  • By Brad Terhune - 9:54 AM on November 3, 2015   Reply

    So, should the new CCP run on El Capitan?
    I went up to and acquired the Macintosh CCP that is listed. It just tells me “Something has gone wrong, please try again.” I verified that I’m downloading 1.9.2.

  • By Don Montalvo - 12:38 AM on November 23, 2015   Reply

    I finally got my grubby paws on CCP 1.9.2 and am happy to report the first test was successful.
    InDesign CC 2015 with the latest update, but disabling Adobe DPS (used CCP default settings since they fit).
    The package installed fine via Casper 9.81, both via push to logged off Mac, as well as via Self Service.
    Nice job Karl Gibson (aka Adobe). 🙂

Add a comment