Aug 27, 2013 I downloded the Creative Cloud Packager (CCP) through the team portal and launched the CCPLauncher.dmg file. I then launch the CCPLauncher app in it and it just hangs. Activity Monitor reports Creative Cloud Packager (Not Responding). Mac OS: 10.7.5 Model: MacPro. Adobe`s Creative Cloud Packager (CCP) creates packages that contain Adobe Creative Cloud products and updates. These packages can then be deployed to the client machines in the organization. Windows and/or Mac Operating System (OS) packages, Microsoft Software Installer (MSI), or Package (PKG) files are created, then a user uses any deployment. Adobe Creative Cloud costs $20.99/month for a single app, or $52.99/month for the entire suite. Introducing Adobe Creative Cloud desktop applications, including Adobe Photoshop CC and Illustrator CC. They're the next generation of CS tools. Get hundreds of all-new features. Adobe Creative Cloud costs $20.99/month for a single app, or $52.99/month for the entire suite. Introducing Adobe Creative Cloud desktop applications, including Adobe Photoshop CC and Illustrator CC. They're the next generation of CS tools. Get hundreds of all-new features. Create new packages using the Creative Cloud Packager; Be sure to clear the cache in the Creative Cloud Packager Preferences to ensure you have the most recent builds of the installation files. See Step 5 under the 'Create Packages' section of this document for details: Creating packages. Lightroom 4 for Mac OS has been removed from Creative Cloud.
- Adobe Creative Cloud Packager For Mac Pro
- Creative Cloud Packager Mac
- Adobe Creative Cloud Packager For Mac Catalina
- Download Adobe Creative Cloud Mac
- Adobe Creative Cloud Packager For Mac Free
- Adobe Creative Cloud Packager For Mac Os
- Adobe Packager Download
In the previous post, we covered the scenarios in which you might want to deploy a Creative Cloud device license or serial number separate from the actual applications, as a “License File Package”. Although the Creative Cloud Packager app supports this as a workflow, the problem is that it doesn’t help you out much with regards to the files it outputs.
Adobe has had the APTEE tool around for a while, as a command-line interface to the Creative Suite licensing tools, to aid with deployment automation - it’s a single executable which confusingly does not include “APTEE” anywhere in the name of the binary: adobe_prtk.
This tool is still around, and has been updated for Creative Cloud. It’s also claimed to be installed as part of Creative Cloud Packager, which is true, but its location is not documented anywhere I could find, so I’ll save you the trouble looking for it: /Applications/Utilities/Adobe Application Manager/CCP/utilities/APTEE/adobe_prtk.
According to the official documentation for the “Create License File” option in CCP, that outputs four files:
Adobe Creative Cloud Packager For Mac Pro
- AdobeSerialization
- RemoveVolumeSerial
- helper.bin
- prov.xml
..there’s no adobe_prtk among those. But it turns out, if we take a look at the strings of AdobeSerialization - which the docs say we can run with “admin privileges” to license the software - some of the first strings found in the binary look an awful lot like flags to adobe_prtk:
AdobeSerialization seems to be a purpose-built version of adobe_prtk with options baked in. This tool loads your authenticated data and license details stored in an opaque format from the prov.xml file to perform a transaction with Adobe’s licensing servers and commit the results to the local machine’s Adobe licensing database.
Along with AdobeSerialization there’s the RemoveVolumeSerial tool. Unfortunately, as mentioned previously and in Adobe’s official CCP documentation this tool is supported for “Enterprise and EEA customers only” - which means it can’t be used to deactivate a machine that is using a Device license in a Teams-based agreement. In fact, it has an LEID baked in along with the adobe_prtk options: V7{}CreativeCloudEnt-1.0-Mac-GM. (For reference, the current LEID for the Creative Cloud Teams “Complete” product is V6{}CreativeCloudTeam-1.0-Mac-GM.)
We’ve got enough hints in these two binaries to figure out that we can pass flags to adobe_prtk. From my examination, these roughly boil down to using the --tool=GetPackagePools flag for a device (Teams) license (see references to “DBCS” throughout the code, ~/Library/Logs/oobelib.log file and the prov.xml file), and --tool=VolumeSerialize for a serial number (Enterprise) license.
Using the adobe_prtk tool and knowing the LEID of the product we want to deactivate, we can also do what the RemoveVolumeSerial tool cannot do: deactivate a teams-based device. The tool options don’t seem to be different depending on a device or serial license, the issue is simply that RemoveVolumeSerial has a hardcoded LEID, whereas we can know ours by looking up the list, or even better, retrieving this automatically from the prov.xml file.
Based on this examination, it looks like adobe_prtk can perform a superset of the functions these two special binaries output from CCP can do, using a single binary. So in order to build a “licensing package” that can be installed as a native OS X installer package (and deployed with Munki, Imagr, DeployStudio, Casper, etc.) we have our necessary ingredients: we need the adobe_prtk (or “APTEE”) tool, the prov.xml file corresponding to our license, and we know the commands to install and remove the license. Still, we need to know which command flags go with which license type, and we need to set the correct LEID if we want to ever be able to deactivate the license. Why not instead use the binaries that are output by CCP? As I described above, the removal tool will not work for all license agreements. I’d rather not have to keep track of multiple different binaries if one can do all the work.
Since investigating all this I decided this would be useful to encapsulate into a script that removes the guesswork from this, and so it has been put on GitHub here: make-adobe-cc-license-pkg.
It only requires a copy of adobe_prtk, which will be discovered automatically if you’ve already installed CCP on the system running the script, and your prov.xml file output from your “Create License File” workflow. Everything else should be figured out for you, and a package will be output given the package parameters you specify:
Since I use Munki, and this package can only really be properly “removed” using an uninstall script, this tool can also import the resultant package into Munki and set the appropriate uninstall_script key with an uninstall script that will be populated with the appropriate LEID. Either way the uninstall script will be saved to the package’s output directory for your own use in other systems.
See the repo’s GitHub page for more details and documentation about how the package is built.
One of the Mac sysadmin community’s biggest peeves with Adobe’s AAM installer framework is that when failures occur (and they happen a lot), useful error codes are rarely printed in the context in which one normally monitors package installations (for example /var/log/install.log). Adobe documents their error codes on their website, and so the install/uninstall scripts generated by this package actually report this info to standard output/error so you can at least immediately get a short description of why any failures might have occurred. There will always be full debug output in the various AAM logs, but the locations of these files are rarely easily discoverable or well-named (for example, ~/Library/Logs/oobelib.log).
This tool hasn’t been widely tested (thanks to Patrick Fergus again for his help testing the functionality with an Enterprise license), and it will probably be getting some tweaks or fixes over time.
Moving on, if you were using Munki or some other software management system (and hopefully you are using one of these), how would you “scope” how these licenses get deployed to machines? We’ll look at a short example using Munki in the next post.
- The Office for Mac 2016 Volume License Installer, Two Months Later –
- What's Wrong with the Office 2016 Volume License Installer? –
- Adobe Creative Cloud Deployment - Pushing Installers with Munki –
- Adobe Creative Cloud Deployment - Managing Licenses with Munki –
Adobe Creative Cloud Packager makes it easy for IT administrators to create packages that contain Creative Cloud products and updates, to deploy within their organizations.
About Adobe Creative Cloud Packager
Adobe® Creative Cloud™ Packager makes it easy for you to create packages that contain Adobe Creative Cloud products and updates. These packages can then be deployed to the client machines in your organization.
Creative Cloud Packager provides workflows for both Creative Cloud for teams and Creative Cloud for enterprise.
Deploying Creative Cloud for teams with Creative Cloud Packager
Watch Adobe Evangelist Andrew Trice as he speaks about deploying Creative Cloud for teams with Creative Cloud Packager.
Deploying Creative Cloud for enterprise with Creative Cloud Packager
Watch Adobe Evangelist Andrew Trice as he speaks about deploying Creative Cloud for enterprise with Creative Cloud Packager.
Download Creative Cloud Packager as follows:
- If you are a Creative Cloud for teams customer, download Adobe Creative Cloud Packager from the Team Admin Portal in Adobe Creative Cloud.
- If you are a Creative Cloud for Enterprise customer, download Adobe Creative Cloud Packager from the Adobe Licensing Website (LWS). You also get your enterprise license key from the LWS.
Using Creative Cloud Packager, you create Windows and/or Mac OS packages (MSI or PKG files) and then using any third-party deployment tool that supports the deployment of native installers (for example Microsoft SCCM, Apple ARD, or JAMF Casper Suite) deploy them to client machines.
Note:
It is recommended that Creative Cloud Packager should not be installed on a system where one or more Creative Suite products or Creative Cloud Manager products have been installed. Adobe Application Manager 3.1 and Creative Cloud Packager can be installed and used on the same machine. However, they should not be running simultaneously during package creation.
Advantages of deployment packages
Creative Cloud Packager Mac
Adobe Creative Cloud Packager provides several advantages when deploying the Creative Cloud applications across large organizations.
Silent and custom install. Deployment packages enable silent installs. A silent install requires no input from end users on the systems on which it is executed, meaning that all choices affecting what is installed and how it is installed are made before the install is performed. These choices are stored in the package.
Adobe Creative Cloud Packager For Mac Catalina
When creating a deployment package, you choose the applications and components you want to install from the product you are packaging. When packaging products for delivery on Windows, you can choose 32-bit or 64-bit versions of the applications. You can also easily choose install options that may not be available when users install applications directly. For example, you can direct the install program to ignore conflicting processes during installation.
Easy package creation. Package creation is easy with the Creative Cloud Packager—the Creative Cloud Packager has an easy-to-use GUI that makes it simple to create a deployment package
The packages created by the Creative Cloud Packager are in industry-standard formats (MSI in Windows, PKG in Mac OS) that are compatible with SCCM and ARD.
Modest system requirements: The system requirements for the Creative Cloud Packager are minimal.
Download Adobe Creative Cloud Mac
Packaging versus Installation
Creative Cloud Packager does not perform an install; it creates a deployment package that records the install decisions you make ahead of time. When you create a package using Creative Cloud Packager, you download the products and their updates, configure product options for enterprise scenarios, and generate an output in native installer formats (MSI or PKG). The packages created are optimized for deployment using enterprise deployment tools.
Creative Cloud Packager Guidelines
- Adobe deployment packages do not support snapshot installations.
- Adobe deployment packages cannot be used to deploy system or application configuration information other than what is explicitly described in this document. In particular, you cannot deploy application–specific preference settings.
- Do not edit the package file (MSI or PKG) created by the Application Manager. The only exception is when you want the user to specify the installation location in Mac OS. In this case, you must modify the Info.plist file in the generated PKG as described in the article Deploying Adobe Packages with ARD.
- You can use Creative Cloud Packager to package only the tools and services that are part of the Creative Cloud. You cannot use this tool to package to Creative Suite applications or the desktop versions of other suites.
- In Windows, if you want to install on both 32-bit and 64-bit systems, you must create both a 32-bit package and a 64-bit package.
- The Creative Cloud Packager does not support the Administrative install point.
- The Creative Cloud Packager does not support NFS or SMB.
Adobe Creative Cloud Packager For Mac Free
Caution: Do not attempt to use a PKG package to install on a Windows system.
Adobe Creative Cloud Packager For Mac Os
System Requirements
Adobe Packager Download
Posted by Alicia