Resolved Issues - Jamf Pro Release Notes 11.29.0

Jamf Pro Release Notes 11.29.0

Solution
Application
Content Type
Technical Documentation
Release Notes
Utilities & Services
version
11.29.0
ft:locale
en-US
vrm_version
11.29.0

Note:

Some resolved issues in this release may have been addressed in a previous maintenance release.

Jamf Pro Server: Security Issues

Jamf provides the CVE-ID for security issues with high or critical severity when possible.

[PI169587] Fixed: Site assignment changes made via mass action in Jamf Pro are not logged in Change Management.

Jamf Pro Server

  • [PI-92] [PI103038] Fixed: Jamf Pro does not display a detailed error message when EDU profiles fail to install because a device user is assigned both a leader and member role.

  • [PI-126] [PI103404] Fixed: When attempting to configure enrollment customization settings, if a Jamf Pro user has permissions to do so via group membership, Jamf Pro sometimes fails to display the interface with the configured language settings and does not allow saving changes.

  • [PI-232] [PI110772] Fixed: If the Collect unmanaged apps option in Settings > Device management > Inventory collection is deselected, apps deployed via App Installers will fail to report deployment status correctly.

  • [PI-250] [PI111682] Fixed: A Shared iPad device enrolled via a PreStage enrollment for a temporary session displays low disk space in inventory. This can prevent the installation of additional apps.

  • [PI-335] [PI119873] Fixed: In Jamf Pro 11.6.0 or later, MDM and Jamf management framework managed local administrator accounts (LAPS) are created but not enabled on 2019 Intel iMac computers with macOS Sonoma.

  • [PI-338] Fixed: Using an extension attribute in the Proxy PAC URL field for the Global HTTP Proxy payload in a mobile device configuration profile causes an "invalid value" error or causes the command to remain in a pending status.

  • [PI-903] Fixed: Jamf Pro does not send an MDM command to remove in-house iOS apps when a user cancels an available app update and the device is then moved to the app's exclusion scope, leaving the older app version installed.

  • [PI-907] Fixed: When Platform SSO is enabled in computer configuration profiles with a Single Sign-on Extensions payload, inclusion of the AuthenticationMethod key causes authentication to fail on computers with macOS 14 or later.

  • [PI-1217] Fixed: When a new in-house iOS app is uploaded to Jamf Pro, install commands are sent to devices before the IPA file finishes distributing to the Jamf Cloud Distribution Service, causing "file not found" errors and stuck pending commands.

  • [PI-1261] Fixed: When viewing computer or mobile device inventory records in Jamf Pro, the static group membership pane does not display any data.

  • [PI-1263] Fixed: The VPP license monitor cycle time increased from its normal processing time to roughly 40 minutes, significantly delaying volume purchase app delivery (including Self Service) to newly enrolled devices.

  • [PI-1268] Fixed: Device lookup errors potentially cause devices to incorrectly become unmanaged.

  • [PI-1282] Fixed: The Jamf Pro interface does not reflect changes to script categories until the browser is refreshed.

  • [PI-1294] Fixed: If the Jamf Pro enrollment signing certificate was renewed while Jamf Pro was on version 11.26.x, macOS enrollments fail with that signing certificate, regardless of the current Jamf Pro version.

  • [PI-1306] Fixed: When using the SSO setup assistant, the Set up in Jamf Account button redirects to an incorrect URL.

  • [PI-1311] Fixed: When attempting to configure a webhook with a "Hash Signature" authentication type, the Jamf Pro interface displays raw code instead of localized text for some field names.

  • [PI-1365] Fixed: Jamf Pro queues unnecessary requests every five minutes for devices with a pending inventory update, degrading push notification performance.

  • [PI173795] Fixed: Out-of-memory conditions can occur when many MDM commands are sent simultaneously while debug mode is enabled in Jamf Pro.

  • [PI184437] Fixed: The OrphanIconCleanupTask may run concurrently with other scheduled tasks, causing failures and allowing orphan icons to consume disk space on the server.