Hey all, this is a combination of a number of posts I kept meaning to write but never got around to. It feels like enough changes and new things have come out that it’s become more valuable to spread the news (along with a little plug or two!)
Changes to Adobe Shared Device Licensing
Since I gave my talk at Penn State, there have been a number of updates, tweaks and changes to Adobe’s SDL:
2019.08.23 – Removal of 90-minute popup
Adobe releases an update to CCDA that removes the often complained about 90-minute timeout / popup.
If you’re on the latest version of Adobe SDL (v1.5 at the time), you don’t have to do anything. However, if you’re on v1 you’ll need to redeploy the CCDA in order to take advantage (Source).
2019.08.02 – User Provisioning from SSO / SAML providers
In August, it was found that if you link your Adobe web console to an Azure AD or Google Federated service for SSO / SAML, it can also be used for user provisioning. This means you are no longer required to use the User Sync Tool, CSV, or the web interface to create Adobe IDs for your users (Source).
The bad news is if you already have Azure AD / Google setup for SSO / SAML you will not be able to take advantage of this.
- Configure Microsoft Azure for use with Adobe SSO
- Set up Google federation for SSO with Adobe
- Tutorial: Azure Active Directory integration with Adobe Creative Cloud
2019.10.XX – Dimension, Self Service and Sign in
In October, SDL saw 3 new features:
- Support for Adobe Dimension. Adobe Dimension is now fully supported for SDL licensed devices.
- You can now deploy SDL packages with support for Self Service installs and updates via the CCDA. Optionally you can also limit this to local admin users only.
- A new message is shown when SDL users log into the CCDA, asking them to logout and to ensure they save data off-device once they’re finished
2019.10.07 – 2019.10.28 – Venezuela and Executive Orders
In order to comply with a U.S. Government Executive Order, any customers registered in the country of Venezuela had their Adobe Apps licenses and cloud service access removed. Later on, Adobe was granted a license by the U.S. Government in order to continue providing their services.
TL;DR: Stuff changed for Venezuelans, then changed back (Source).
2019.10.24 – Adobe and Catalina
Shortly after Apple’s slightly surprising release of macOS Catalina, Adobe carried out some further testing and released a new KB outlining supportability and known issues. At the time I chucked up a post outlining the main information (Plug).
It took me way too long to find this nice, constantly updated KB article from Adobe on all the changes that have come to Shared Device Licensing:
This is something that will be worth bookmarking and checking in on periodically going forward.
Changes to the way Admin console packages are downloaded
At the end of October, Adobe admins who downloaded newly created packages from the Admin console found that instead of providing the built package, Adobe instead provided a download of a new Application; the Adobe Package Downloader (APD?).
An official reason isn’t provided, but it’s believed this may be to help with the “quarantine bits” that get added to the zipped, downloaded packages (detailed in the KB – Known issues with Creative Cloud packages on macOS 10.15 Catalina).
Either way, the new process is to:
- Build your package
- Download the downloader (APD)
- Use the downloader (APD) to download the zipped package
- Unzip the package
- Deploy / add to your deployment solution of choice.
You can run multiple APDs at the same time so there’s that… (source).
The release of Adobe (CC) 2020
Around November 7th, Adobe surprised us with a release of the latest instalment of their Creative Cloud Suite: 2020 (Source).
With this, all Apps and promotional material have dropped the “CC” from their titles. Helpful if you’re using Application titles to determine installs. Not so helpful if you’re managing Docks (although the path tends to change every year regardless).
As with prior major Adobe upgrades, Remote Update Manager (RUM) can’t be used to upgrade clients from CC201X to 2020 for most Apps. You’ll either need to install via CCDA, or create some new packages.
If you need to access the older Apps in the Admin console, you can use the “Show older versions” tick box as before.
Please Note: If you try to create an “Update Package” of your existing packages in the Admin console, they will be ‘updated’ to the 2020 version of Apps, so bear that in mind.
Updates to the dataJAR Adobe CC 2019 importer
During my Penn State talk earlier this year, we (dataJAR) shared the official release of a tool to import all the Adobe CC 2019 App packages correctly into both Munki and Jamf via AutoPKG (complete with corrected install arrays).
Deployment Issues with macOS Catalina
As alluded to in my last post, there were some reported issues trying to deploy any of the Adobe suite of Apps to any macOS Catalina devices. The #adobe channel on MacAdmins Slack was full of reports, however with the time difference between myself and my colleagues-from-another-employer, I found it tricky to follow.
Last weekend I went through 160 tests (of an originally planned 180+) covering various deployment techniques, scenarios, packages and both ‘current’ macOS versions (10.14.6 and 10.15.1) and documented the results. I’ll be writing that up shortly and plan to get it out by the end of the week.
Right, that’s all the current Adobe news I felt relevant all caught up. As always, if you have any questions, queries or comments, let me know below (or @daz_wallace on Mac Admins Slack) and I’ll try to respond to and delve into as many as I can.