Upcoming changes to Patch Management definitions in Jamf App Catalog

JustinC
Contributor II
Contributor II
Retirement of selected ‘Legacy’ definitions.
 
Back in February of 2021 we announced that we would be marking a number of Patch Management definitions as deprecated. This was quickly changed to adding the text of (Legacy Definition) in the publisher column of Patch Management due to the unintended consequence of the ‘Deprecated’ tag. Since that time we had been maintaining the Legacy Definitions in sync with new new replacement definitions, though we have recommended that customers use the ‘newer’ definitions in their Patch Management policies.
We have now made the decision to formally deprecate a number of the legacy titles and remove them from the list of available Patch Management titles in Jamf App Catalog.
 
This removal of legacy definitions will happen over time. The first step will be to change the text in the publisher column from ‘Legacy Definition’ to ‘Deprecated Definition’. Whilst the definitions will still be available for a short period of time in Jamf App Catalog, they will no longer be updated. 
 
The list of titles that will be deprecated are:
Publisher
Name
Adobe (Legacy Definition)
Adobe Acrobat Pro DC
Adobe (Legacy Definition)
Adobe Acrobat Pro XI
Adobe (Legacy Definition)
Adobe Acrobat Reader DC
Adobe (Legacy Definition)
Adobe Acrobat Reader XI
Adobe (Legacy Definition)
Adobe AIR
Adobe (Legacy Definition)
Adobe Core Components CC
Adobe (Legacy Definition)
Adobe Fireworks CS6
Adobe (Legacy Definition)
Adobe Flash Player
Adobe (Legacy Definition)
Adobe Lightroom CC
Adobe (Legacy Definition)
Adobe Lightroom Classic CC
Adobe (Legacy Definition)
Adobe Photoshop Lightroom CC
Adobe (Legacy Definition)
Adobe Shockwave Player
Apple Inc. (Legacy Definition)
macOS 10.13 Build
Apple Inc. (Legacy Definition)
macOS 10.14 Build
Apple Inc. (Legacy Definition)
macOS 10.15 Build
Box Inc (Legacy Definition)
Box Drive
Citrix Systems, Inc (Legacy Definition)
Citrix Workspace
Citrix Systems, Inc (Legacy Definition)
Citrix Workspace
Google (Legacy Definition)
Google Chrome
Google LLC (Legacy Definition)
Backup and Sync
Microsoft (Legacy Definition)
Microsoft AutoUpdate
Microsoft (Legacy Definition)
Microsoft Excel
Microsoft (Legacy Definition)
Microsoft Excel 2016 Track
Microsoft (Legacy Definition)
Microsoft Intune Company Portal
Microsoft (Legacy Definition)
Microsoft OneNote
Microsoft (Legacy Definition)
Microsoft OneNote 2016 Track
Microsoft (Legacy Definition)
Microsoft Outlook
Microsoft (Legacy Definition)
Microsoft Outlook 2016 Track
Microsoft (Legacy Definition)
Microsoft PowerPoint
Microsoft (Legacy Definition)
Microsoft PowerPoint 2016 Track
Microsoft (Legacy Definition)
Microsoft Silverlight
Microsoft (Legacy Definition)
Microsoft Teams
Microsoft (Legacy Definition)
Microsoft Word
Microsoft (Legacy Definition)
Microsoft Word 2016 Track
Microsoft (Legacy Definition)
OneDrive
Microsoft (Legacy Definition)
Skype
Microsoft (Legacy Definition)
Skype for Business
Mozilla (Legacy Definition)
Mozilla Firefox
Mozilla (Legacy Definition)
Mozilla Firefox Extended Support Release (ESR)
Slack Technologies, Inc (Legacy Definition)
Slack
VideoLAN (Legacy Definition)
VLC media player
Zoom Video Communications, Inc. (Legacy Definition)
zoom.us
 
On the 3rd of April 2023 these definitions will be completely removed from Jamf App Catalog.
 
New Consolidated definitions.
 
The usual format of a Patch Management software title is to have the definitions separated by major versions. e.g. Photoshop 2021, Photoshop 2022 and Photoshop 2023 all appear as seperate titles with the minor patch versions being contained within each definition. Due to technical requirements, we have had a number of software titles in Patch Management that haven’t followed this structure and instead have had to be separated out by the ‘dot’ releases. Wireshark is an example of a definition that has been separated this way.
 
wireshark_example.png
 
We understand that this kind of separation has affected a number of customer workflows. You couldn’t easily use Patch Management to upgrade an end user computer from Wireshark 2.2.13 to 3.6.11 for example. To address this we have developed a new mechanism that will allow us to combine these seperate definitions into a new definition format that we will be marking as a ‘Consolidated Definition’. Continuing with the Wireshark example, these separate definitions for version 3 of Wireshark will be combined into one Wireshark 3.0 patch definition.
 
In addition to this, selected Legacy Definitions will be renamed and also become Consolidated Definitions, so that these titles will remain available to admins, without the need to re-create Patch Management policies.
 
New Extension Attributes.
 
The other significant change that will be rolling out across the Patch Management definitions is to standardise the code as much as possible for any definitions that require the use of an Extension Attribute to determine the version of software on an end user computer. The definitions will remain, it is just the code used in the Extension Attribute that will be updated.
As this is a code change, you will be required to review the new Extension Attribute code and accept the change from within the ‘Extension Attribute’ tab of the affected patch definition. See the Mozilla Firefox example below.
 

firefox_example.png

 
New extension attributes will be implemented on the 6th of March 2023.
The full list of titles that will be receiving changes to their Extension Attributes are:
Publisher
Name
3CX
3CXPhone
ActiveState Software
Komodo Edit 8
ActiveState Software
Komodo Edit 9
ActiveState Software
Komodo Edit 10
ActiveState Software
Komodo Edit 11
ActiveState Software
Komodo Edit 12
Adobe
Adobe Flash Player
Adobe
Adobe Gaming SDK
Adobe
Adobe Photoshop Camera Raw CC
AdoptOpenJDK
AdoptOpenJDK (Hotspot, JRE) 8
AdoptOpenJDK
AdoptOpenJDK (Hotspot, JRE) 11
AdoptOpenJDK
AdoptOpenJDK (Hotspot, JRE) 14
AdoptOpenJDK
AdoptOpenJDK (Hotspot, JRE) 15
AdoptOpenJDK
AdoptOpenJDK (Hotspot, JRE) 16
AdoptOpenJDK
AdoptOpenJDK (Hotspot) 8
AdoptOpenJDK
AdoptOpenJDK (Hotspot) 11
AdoptOpenJDK
AdoptOpenJDK (Hotspot) 14
AdoptOpenJDK
AdoptOpenJDK (Hotspot) 15
AdoptOpenJDK
AdoptOpenJDK (Hotspot) 16
AdoptOpenJDK
AdoptOpenJDK (OpenJ9, JRE) 8
AdoptOpenJDK
AdoptOpenJDK (OpenJ9, JRE) 11
AdoptOpenJDK
AdoptOpenJDK (OpenJ9, JRE) 14
AdoptOpenJDK
AdoptOpenJDK (OpenJ9, JRE) 15
AdoptOpenJDK
AdoptOpenJDK (OpenJ9, JRE) 16
AdoptOpenJDK
AdoptOpenJDK (OpenJ9) 8
AdoptOpenJDK
AdoptOpenJDK (OpenJ9) 11
AdoptOpenJDK
AdoptOpenJDK (OpenJ9) 14
AdoptOpenJDK
AdoptOpenJDK (OpenJ9) 15
AdoptOpenJDK
AdoptOpenJDK (OpenJ9) 16
Airtame
Airtame
Amaris Consulting
Octory
Amazon
Amazon Corretto 8
Amazon
Amazon Corretto 11
Amazon
Amazon Corretto 15
Amazon
Amazon Corretto 16
Amazon
Amazon Corretto 17
Amazon
Amazon Corretto 18
Amazon
Amazon Corretto 19
Axure
Axure RP 9
Axure
Axure RP 10
Azul
Zulu OpenJDK 8 (LTS)
Azul
Zulu OpenJDK 9
Azul
Zulu OpenJDK 10
Azul
Zulu OpenJDK 11 (LTS)
Azul
Zulu OpenJDK 12
Azul
Zulu OpenJDK 13 (MTS)
Azul
Zulu OpenJDK 14
Azul
Zulu OpenJDK 15 (MTS)
Azul
Zulu OpenJDK 16 (STS)
Azul
Zulu OpenJDK 17 (LTS)
Azul
Zulu OpenJDK 18 (STS)
Azul
Zulu OpenJDK 19 (STS)
Bart Reardon
swiftDialog
Docker
Docker Kitematic
Eclipse Foundation
Eclipse IDE for C and C++ Developers
Eclipse Foundation
Eclipse IDE for Eclipse Committers
Eclipse Foundation
Eclipse IDE for Embedded C and C++ Developers
Eclipse Foundation
Eclipse IDE for Enterprise Java Developers
Eclipse Foundation
Eclipse IDE for Java and DSL Developers
Eclipse Foundation
Eclipse IDE for Java Developers
Eclipse Foundation
Eclipse IDE for PHP Developers
Eclipse Foundation
Eclipse IDE for RCP and RAP Developers
Eclipse Foundation
Eclipse IDE for Rust Developers
Eclipse Foundation
Eclipse IDE for Scientific Computing
Eclipse Foundation
Eclipse IDE for Scout Developers
Eclipse Foundation
Eclipse IDE for Testers
Eclipse Foundation
Eclipse IDE for Web and JavaScript Developers
Eclipse Foundation
Eclipse Modeling Tools
Eclipse Foundation
Eclipse Temurin (JRE) 8
Eclipse Foundation
Eclipse Temurin (JRE) 11
Eclipse Foundation
Eclipse Temurin (JRE) 17
Eclipse Foundation
Eclipse Temurin 8
Eclipse Foundation
Eclipse Temurin 11
Eclipse Foundation
Eclipse Temurin 16
Eclipse Foundation
Eclipse Temurin 17
Eclipse Foundation
Eclipse Temurin 18
Eclipse Foundation
Eclipse Temurin 19
Google
Google Android Studio
Google
Google Backup and Sync
Google
Google Drive
HashiCorp
Vagrant
IBM
IBM Semeru Runtime (OpenJ9, JRE) 8
IBM
IBM Semeru Runtime (OpenJ9, JRE) 11
IBM
IBM Semeru Runtime (OpenJ9, JRE) 16
IBM
IBM Semeru Runtime (OpenJ9, JRE) 17
IBM
IBM Semeru Runtime (OpenJ9, JRE) 18
IBM
IBM Semeru Runtime (OpenJ9) 8
IBM
IBM Semeru Runtime (OpenJ9) 11
IBM
IBM Semeru Runtime (OpenJ9) 16
IBM
IBM Semeru Runtime (OpenJ9) 17
IBM
IBM Semeru Runtime (OpenJ9) 18
IntelliScape Solutions
Caffeine
Jamf
Jamf Connect Login
Jamf
Jamf Protect
JetBrains
JetBrains DataSpell
JetBrains
JetBrains PyCharm Community
JetBrains
JetBrains PyCharm Professional
Luxion
KeyShot 9
Luxion
KeyShot 9 Network Rendering
Luxion
KeyShot 9 Viewer
Luxion
KeyShot 10
Luxion
KeyShot 10 Network Rendering
Luxion
KeyShot 10 Viewer
Luxion
KeyShot 11
Luxion
KeyShot 11 Network Rendering
Luxion
KeyShot 11 Viewer
Malwarebytes
Malwarebytes 4
McNeel
Rhinoceros 6
McNeel
Rhino 7
Microsoft
Microsoft .NET Runtime 2.0
Microsoft
Microsoft .NET Runtime 2.1
Microsoft
Microsoft .NET Runtime 2.2
Microsoft
Microsoft .NET Runtime 3.0
Microsoft
Microsoft .NET Runtime 3.1
Microsoft
Microsoft .NET Runtime 5.0
Microsoft
Microsoft .NET Runtime 6.0
Microsoft
Microsoft .NET Runtime 7.0
Microsoft
Microsoft .NET SDK 2.0
Microsoft
Microsoft .NET SDK 2.1
Microsoft
Microsoft .NET SDK 2.2
Microsoft
Microsoft .NET SDK 3.0
Microsoft
Microsoft .NET SDK 3.1
Microsoft
Microsoft .NET SDK 5.0
Microsoft
Microsoft .NET SDK 6.0
Microsoft
Microsoft .NET SDK 7.0
Microsoft
Microsoft OneDrive
Microsoft
Microsoft Skype
Mozilla
Mozilla Firefox
Mozilla
Mozilla Firefox ESR
Mozilla
Mozilla Firefox Developer Edition
Node.js Foundation
Node.js 4
Node.js Foundation
Node.js 5
Node.js Foundation
Node.js 6
Node.js Foundation
Node.js 7
Node.js Foundation
Node.js 8
Node.js Foundation
Node.js 9
Node.js Foundation
Node.js 10
Node.js Foundation
Node.js 11
Node.js Foundation
Node.js 12
Node.js Foundation
Node.js 13
Node.js Foundation
Node.js 14
Node.js Foundation
Node.js 15
Node.js Foundation
Node.js 16
Node.js Foundation
Node.js 17
Node.js Foundation
Node.js 18
Node.js Foundation
Node.js 19
OpenMedia
4K Video Downloader
Opera Software
Opera
Oracle
Oracle Java SE Development Kit 7
Oracle
Oracle Java SE Development Kit 8
Oracle
Oracle Java SE Development Kit 8 (CPU)
Oracle
Oracle Java SE Development Kit 9
Oracle
Oracle Java SE Development Kit 10
Oracle
Oracle Java SE Development Kit 11
Oracle
Oracle Java SE Development Kit 12
Oracle
Oracle Java SE Development Kit 13
Oracle
Oracle Java SE Development Kit 14
Oracle
Oracle Java SE Development Kit 15
Oracle
Oracle Java SE Development Kit 16
Oracle
Oracle Java SE Development Kit 17
Oracle
Oracle Java SE Development Kit 18
Oracle
Oracle Java SE Development Kit 19
Oracle
Oracle Java SE Runtime Environment JRE 7
Oracle
Oracle Java SE Runtime Environment JRE 8
Oracle
Oracle Java SE Runtime Environment JRE 8 (CPU)
Oracle
Oracle Java SE Runtime Environment JRE 9
Oracle
Oracle Java SE Runtime Environment JRE 10
Oracle
Oracle SQLDeveloper
Progress
Chef Workstation
Progress
ChefDK
Python Software Foundation
Python 2
Python Software Foundation
Python 3
Royal Apps GmbH
Royal TSX
Squared 5
MPEG Streamclip
Trimble
Trimble SketchUp 2016
Trimble
Trimble SketchUp 2021
Ultimaker BV
Ultimaker Cura
YourKit
YourKit Java Profiler
 
What do these changes mean for you?
 
If you have any Patch Management policies in use that still use one of the ‘Legacy Definition’ titles that are in the list above as being deprecated, please recreate your Patch Management policies using the newer replacement definitions.
 
If you have any Patch Management policies using a definition that will be affected by the Extension Attribute change then please review and accept the EA code change so that the Patch Management policy will continue to run as expected.
3 REPLIES 3

jmahlman
Valued Contributor

Thank you for finally addressing the non-consolidated versioning.

garybidwell
Contributor III

@JustinC Great work on fixing the consolidating versions problem.
Any closer to resolving the issue with application vendors now creating separate packages for x86 and ARM and Patch Management not being able to support this?

The workaround of adding the Jamf Patch Source again as secondary external source doesn't work when application title requires a extension attribute to function (as it doesn't allow a duplicate extension attribute with the same name to be added)

bradtchapman
Valued Contributor II

Customers with smart groups that refer to patch reporting software titles will be unable to delete either the new or the legacy title once both exist concurrently.

Steps to reproduce:

  1. Create a patch reporting software title for Adobe Lightroom CC (Legacy) — pretend this already existed in your environment for a while.
  2. Create a smart group with criteria: patch reporting software title: "Adobe Lightroom CC" and pick any version, doesn't matter.
  3. Create a patch reporting software title for Adobe Lightroom CC (the new one).
  4. Go back to the main patch management page.
  5. Access the Adobe Lightroom CC (Legacy Definition) title.
  6. Try to delete it.  You'll be blocked by "The following items are dependent..."
  7. Go back to the main patch management page and open the new definition for Lightroom.
  8. Try to delete it.  You'll be blocked by "The following items are dependent..."

Interestingly, if you go back to the smart group criteria, clear it out, and try to add the Patch Reporting Software Title, you will see two distinct listings for Adobe Lightroom CC.  Selecting either of these makes no difference on which patch policy is chosen, because Jamf's logic here uses name-based matching, instead of referring to the patch policy by its ID # and pulling the name as its attribute.  This name-based matching still exists for computer group lookups, too—a problem that has persisted since the Casper 8 days, at least.  Names are not unique.  ID numbers are.

I also tried deleting the patch policies via API to no avail.

The ONLY workaround in this case would be to delete the smart groups dependent on these patch titles, THEN delete the legacy patch title, and finally restore the Smart Group.