Creating a pkg for Creative Cloud - Anyone have experience with this

If you're on CC for Teams or CC for Enterprise, then you can use the Creative Cloud Packager to build a .pkg file for deployment. That app also lets you set some options for updates or custom install directories as part of the packaging process, as well as pick and choose the apps you want to package (depending on what you have available).

Creative Cloud Packager will be your friend. Try a search in the forums as there are different approaches you can take with this.

Some people generate a big CC package with Creative Cloud Packager and then use the method described there: https://jamfnation.jamfsoftware.com/article.html?id=161

I personally like to create a package for each individual app so that I can get a single installer and uninstaller generated. I can then cache all the installers in 1 policy and then in a second policy run all the cached installers. I also "re-package" (with Packages.app) the generated installers so that it's a part of Additional Resources and install using a postinstall script. This makes it completely flat and portable. No having to deal with DMGs (which I personally avoid).

thanks, I am trying to make a pkg using the Creative Cloud Packager. Will see if it works like I want

I found that by zipping the package locally, Then uploading it to the Distribution point directly, rather than via CasperAdmin, Installation was much better. When re starting CasperAdmin, The B.O.M's was created at that point.
Also, Deployed as 'cached' then 'installed cached'

@jamest we create separate packages to include the specific Adobe software that a particular group of computers needs. There's a checkbox prior to selecting the Adobe software to package up to include the Creative Cloud application. You can also choose whether app updates are visible / allowed in the Creative Cloud app.

Packaging each Adobe Application separately seemed to work for me. It took a bunch of times for the CC Packager to work but once it did I just packaged them all up while it worked. Was able to test a policy once I created a pkg in Composer and it worked as it should

the easiest way I found is to package each individual apps, as each can be removed individually if needed and less network bandwidth needed instead of deploying a huge bundled app, and easier to cache.

additionally if you disable user interaction or upgrades, you can create a specific update package and deploy those individually or package together.