Endpoint Services, Munki, Updating Adobe Deployments

Endpoint Services-specific information about using Munki to keep Adobe Creative Cloud and Acrobat current.

Systems

Munki Mac Endpoint Management

Affected Customers

University of Illinois IT Pros leveraging Technology Services Endpoint Service Munki Mac Endpoint Management systems to deploy Adobe Acrobat and Creative Cloud.

Actions

General Information about Legacy Adobe Applications

In February 2020, the campus device license expired for pre-2019 versions of Creative Cloud applications as well as Adobe Acrobat DC. In order to ensure that Adobe installations continue to work properly, IT Pros must replace legacy Adobe applications with current versions.

These steps must be completed by October 15, 2020, when all legacy versions are scheduled to be retired from the Multi-Tenant Munki service.

Archiving legacy titles reclaims needed disk space and streamlines the MTM service, speeding up Munki runs and MunkiAdmin load times.

Note that once a title has been retired from the service, you will no longer be able to use Munki to uninstall it.

Due to the removal of support for 32-bit applications on macOS 10.15 (Catalina), using Munki to uninstall Adobe CC 2017 and older will not work on macOS 10.15. To uninstall these applications on 10.15, use the Creative Cloud Cleaner Tool, then delete the titles from your manifests so that they may be archived from the service. The Adobe Uninstall Unauthorized Versions tool can also be used to remove many, but not all, legacy Adobe applications. A final option is the Adobe CC 2017 Uninstaller package, which will perform a 'dirty' uninstall by deleting CC 2017 items from the Applications folder.

Searching Manifests with MunkiAdmin

MunkiAdmin can help you search through your unit Munki manifests to find legacy applications.

  • With your repo open in MunkiAdmin, select the Manifests tab (Command-3).
  • Click the Search button.
  • Configure a search for "Any installs item" "ends with", and enter the legacy name key you are searching for--for example, adobe_acrobat_reader_xi.
  • From the search results, open each unit manifest and make the changes outlined below for each legacy application.

Replacing Legacy Acrobat DC or Reader

  • Acrobat Pro DC has moved to the Named User (NUL)/Shared Device (SDL) license model. To update your Acrobat DC deployments:
    • Locate adobe_acrobat_dc in your unit manifests.
    • Replace it with either adobe_acrobat_dc_nul or adobe_acrobat_dc_sdl as appropriate.
    • This should not trigger any installs or uninstalls, but removing the old title from manifests will allow us to retire it.
  • Acrobat Reader XI has been replaced with Acrobat Reader DC. To update your Acrobat Reader deployments:
    • Locate adobe_acrobat_reader_xi in your unit manifests.
    • Move it from managed or optional installs to managed uninstalls, and delete it from managed_updates.
    • Add adobe_acrobat_reader_dc to managed or optional installs as appropriate.
    • Once Acrobat Reader XI has been uninstalled from all devices, delete adobe_acrobat_reader_xi from unit manifests.

Installing Creative Cloud 2020

For convenience, the EPS team has created the following included manifests for units to incorporate within their own unit manifest structure:

  • UofI_licensed_adobe_cc2020_nul_managed_installs (enforces the installation of all eighteen Creative Cloud 2020 applications for Named User sign-in)
  • UofI_licensed_adobe_cc2020_sdl_managed_installs (same as above but with the Shared Device License, which requires a campus IP address so is not recommended for laptop deployment)
  • UofI_licensed_adobe_cc2020_nul_optional_installs (offers all Named User applications for self-service installation under the Software tab in Managed Software Center)
  • UofI_licensed_adobe_cc2020_sdl_optional_install (same as above but with the Shared Device License, which requires a campus IP address so is not recommended for laptop deployment)

Best practice is to use one of the above in your unit's base_default manifest.

If there is a need to deploy Creative Cloud 2019, the following included manifests are also available:

  • UofI_licensed_adobe_cc2019_nul_managed_installs
  • UofI_licensed_adobe_cc2019_nul_optional_installs

Uninstalling Creative Cloud 2019

While CC 2019 is supported, we encourage IT Pros to transition to CC 2020 whenever possible. 

To uninstall 2019 Creative Cloud applications:

  • Locate all Creative Cloud 2019 items wherever they appear in any of your unit's manifests. This includes individual titles as well as included manifests such as UofI_licensed_adobe_cc2019_optional_installs or UofI_licensed_adobe_cc2019_managed_installs.
  • Change the above items from managed or optional installs to managed uninstalls wherever they appear.
  • Once CC 2019 apps have been uninstalled from all devices, delete them from unit manifests.

Uninstalling Creative Cloud 2018

To uninstall 2018 Creative Cloud applications:

  • Delete all Creative Cloud 2018 items wherever they appear in any of your unit's manifests. This includes individual titles as well as included manifests such as UofI_licensed_adobe_cc2018_managed_installs or UofI_licensed_adobe_cc2018_optional_installs.
  • Add the following included manifest to your unit's base_default manifest:
    • UofI_licensed_adobe_cc2018_managed_uninstalls
  • Once all CC 2018 apps have been uninstalled from devices, delete the included manifest from your base_default manifest.

Uninstalling Creative Cloud 2017 and older

On macOS 10.14.6 and below:

  • Delete all Creative Cloud 2017 items wherever they appear in any of your unit's manifests. This includes individual titles as well as included manifests such as UofI_licensed_adobe_cc2017_managed_installs or UofI_licensed_adobe_cc2017_optional_installs
  • Add the following included manifest to your unit's base_default manifest:
    • UofI_licensed_adobe_cc2017_managed_uninstalls
  • Move all pre-2017 items from managed or optional installs to managed uninstalls.
  • If Munki fails to successfully uninstall items, run the Creative Cloud Cleaner Tool.
  • Once all legacy apps have been uninstalled from devices, delete them from manifests.
  • On macOS 10.15.0 and up:
    • Run the Adobe Uninstall Unauthorized Versions tool, which will remove many, but not all, legacy CC applications.
    • If any legacy CC applications remain, use the Creative Cloud Cleaner Tool.
    • A final option is the adobe_cc_2017_uninstaller package, which will perform a 'dirty' uninstall by deleting CC 2017 items from the Applications folder. Add this as a managed install on any devices where the preceding tools have failed to remove CC 2017 apps.

    Modify Your Manifest Templates

    We recommend removing Adobe included manifests and other version-specific items (e.g. Office 2019) from your manifest templates, and instead put them in your base_default manifest for greater ease in updating your unit to current versions. See more information about manifest templates.



    Contact the EPS team




    Keywords:EPS Adobe CC mtm munki endpoint TechS-EPS-MTM Acrobat creative cloud   Doc ID:98564
    Owner:EPS Distribution List .Group:University of Illinois Technology Services
    Created:2020-03-09 13:51 CDTUpdated:2020-04-27 15:27 CDT
    Sites:University of Illinois Technology Services
    Feedback:  2   2