If you’re not sure which console you have, see this kb., with the “old” console on the left & the “new” console on the right. However, if you currently have the following Admin Console experience, you cannot use CCP or the Admin Console to package CC 2019 apps and deploy these for your end usersĪfter reaching out to Adobe, all accounts on the “old” Admin Console will be transitioned by end of Jan 2019.

For more information, see the Packaging user guide.īut, if you have a Teams license, you might not see the above option due to: We are transitioning to a redesigned Admin Console. For help on creating packages, see Package apps in the Admin Console. However, there is a solution: To create packages for CC 2019 apps, go to the Packages tab in the Admin Console. This means that when creating a package, the Creative Cloud Packager Applications and Updates screen will not display CC 2019 apps This new kb, Apps not available in Creative Cloud Packager | CC 2019, details that: You cannot use Creative Cloud Packager to create packages that include CC 2019 apps or later. H/t pexner in #adobe in MacAdmins Slack /co7ebGKBP3 This later became the adobe-ccp-recipes repo, of which I am happy to have contributed to.Īpps not available in Creative Cloud Packager | CC 2019 Soon after, both mosen & tvsutton started to experiment in leveraging this automation. Love it or loathe it, Creative Cloud Packager (CCP) has been around since mid-2013, & has been a helpful tool for us Admins to create PKG’s for the various Creative Cloud releases.Īround mid 2016, Adobe published a KB on automating CCP using some specially crafted XML. MacRumors has a decent little writeup listing some of the app changes & updates included within Creative Cloud 2019.Īdobe Announces Creative Cloud Updates for Photoshop, Lightroom, Illustrator and Launches Premiere Rush by /8fYgg6rEPS

Adobe creative pakager for mac