When you click one of these packages, you’re able to see more details of which options have been used to create them:Īfter reviewing these settings, I recommended to document these options first. In the list below you see packages which I’ve created before:

This particular account has licenses for Acrobat Pro DC, InDesign and Photoshop products only:īut Adobe Creative Cloud has many more products to choose from:Ĭlick the ‘Packages’ tab to create a deployment package. How? I don’t know.Īfter logging in with an enterprise account, this is the dashboard where we have to start from: Apparently individual customers or SMB’s have to do things different. I’ve tried using this with an Adobe account which holds a subscription for Adobe Acrobat Pro DC:īut this fails without telling me that the Adobe Admin Console is only available for Enterprise customers. Using it only is an option when you have a subscription for Adobe Creative Cloud for Enterprise or Adobe Document Cloud for enterprise. The new option is web based and is called Adobe Admin Console. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Our first Adobe Creative Cloud KB article still refers to using that technology, based on a Windows utility which needed to be installed by the one who wanted to create packages for Creative Cloud.īut Creative Cloud Packager is no longer in development and no updates will be provided. In this blog I will describe what’s needed to use the Adobe Admin Console to create a package to deliver Adobe Acrobat DC using Liquit Workspace.Īdobe used to have what was called Creative Cloud Packager. You definitely need patience for this one, a coffee machine standing by, smiles from your dear colleagues and time to read and learn from others who have dealt with deployment. Like AutoCAD, Adobe Creative Suite is probably one of the most time consuming applications when it comes to preparation and testing for a successful deployment.

Adobe cloud download user agent osx