creating single app deployment packages for Adobe CC single apps???

[tcandela]

is anyone creating adobe cc single app deployment packages from your adobe team account for single apps such as Photoshop and Adobe Acrobat Pro DC? using AAMEE?

currently we just assign the user in the admin portal and they get an email and we assist with the installation.

is it working with AAMEE?
how is it tied to a specific user?
what happens with application has an update?

[dlondon]

I'm just creating them in the web interface for our Campus Subscription. The All Apps package was just too ridiculous a size to consider.

For staff I'm not even installing the Apps - just the Creative Cloud App itself and I let them choose what they need via the App. That gives them some control and doesn't fill their machine with software they don't need.

[mschroder]

We also just assign the users, and they fetch the products they need. No more worries about building packages and keeping them up-to-date.

[geoff_widdowson]

Stopped using AAMEE since we can not longer package an enterprise serial number into the package. I jus use the create package feature of the adobe admin console. I created them all as single apps, so I can make each available in Self Service, so the user can install what they want, or all using a policy that includes all the packages. The users have to sign-in to use the apps so have to have an account either personal or managed by us again in the adobe admin portal. I also packaged the CC Desktop Self service, which means the user can update the app themselfs without admin rights.

[tcandela]

@geoff.widdowson i see the creative cloud packager but where is the DD desktop self service?

[geoff_widdowson]

@tcandela From the Packages page, Press the blue 'Create a Package' button then you should see

[tcandela]

@geoff.widdowson so if you have for examps 5 adobe all apps cc licenses and 5 adobe photoshop cc licenses you still have to add those users to the admin portal for whatever product the user will be assigned to use? if you don't add a person they can install the app but not use it since they have to login with an account?

is this CC Self Service you use so updates can be installed separate from the single install apps you have in self service?

It's that easy? I just went to create package gave it a name of 'CC TEST' and it created the .zip so if I add that pkg to Self Service and the person installs it, what is exactly being installed? i was not given any choice to choose an adobe application. It just installs the Adobe Creative Cloud Desktop App?

I see 2 options when i click Create Package 1 -- Self Service Package --- so i created a package here and gave it a name but was given no apps to choose. so what will it install on the mac client computer when user runs installs this from Self Service? 2 -- Managed Package --- this gives me adobe applications to choose from

[geoff_widdowson]

@tcandela Correct. The Self Service will allow updates from the CC desktop app, without the user needing admin rights or a license to use it. I package all the apps to make available in the Jamf Self Service for each major release like CC2020, as it is easier if they don’t have anything installed already (one button with Install All), but to do updates I want them to do it from the Adobe CC Desktop app. When you package the Adobe Self Service you can include the CC Desktop app. If you want you can just send out the CC Desktop to all your computers, then the user can install or update any of the Adobe apps, without the need for you to package any of them. From their point of view it is how they would install on their own computer so it's what they are used to and for us it reduces the need to remote on to do updates with admin rights.

On Managed Package, pick the Apps the next step Options, it gives yout the option to add the Self Service and allow non-admins to do updates. I choose to do both 'Self Service package' and 'Managed package' so I can deploy just the ability for the user to install from the desktop app or from Jamf Self Service.

The need to sign-in is useful if you have shared devices where one person has a license but others don't. Also useful if you have freelance workers you don't want to give a licenses but they have a personal account (you provide the software they provide the license).

[tcandela]

@geoff.widdowson so basically you use the Self Service Package to create a pkg just for user to run updates on whatever Adobe CC application is installed on the computer?

then you also make individual packages using the Managed Package option? which does not give the user control of running updates?

Whats this other thing called 'CREATIVE CLOUD PACKAGER' in the 'Tools' section? I read it, looks like a third option to create pkgs.

[geoff_widdowson]

@tcandela You can use the Managed Package to include the option to allow updates by users also. I use the Self Service package to cover all options, as that on it's own means users can install and update without using the jamf self service. Some of my users will have older version of CC anyway and are happy to just update from the Desktop app, but if they had been deployed without a package that allowed updates they would be prompted for admin rights when using the Desktop app. Sending out the Self Service app gives them the right to now update without admin rights.

The Creative Cloud Packager was the Creative Cloude replacement for AAEEE (used for CS6). That allowed you to package your eneterprise serial number into the package and any computer with one of it's packages did not require the user to sign in. Adobe have mostly stopped it now and want 'named users' ie those with a user license. I think some companies can still use Creative Cloud Packager for CC but my last two employers have had to move to named users so can't use it anymore. It depend on what agreement you have with Adobe, some orgs had longer multi year contracts, so could continue to use the CC packager, but I think it will ends for everyone by 2021 (I forget the exact year).

[snowfox]

Creative Cloud Packager and AMMEE can't be used any more since version CC 2018. CC 2019 / 2020 now require you to use the Adobe Admin Console within your Adobe management account. That's where you now generate installer packages for download to your admin machine. Note the service will give you a stub pkg to download (only a few Mb) and you must open and run it to download the real installer pkg from the Adobe AWS servers.
Lengthy discussion about Adobe CC packaging here:
https://www.jamf.com/jamf-nation/articles/593/deploying-adobe-creative-cloud-packages
Latest steps to follow are located towards the bottom of the thread.