Apple Changes & Release Notes

Jamf Pro Release Notes 11.24.0

OIDC-based SSO Through Jamf Account Enabled by Default for New Jamf Pro Instances

Automatic Jamf Protect Tenant Registration

Configuration Profiles

Mobile Device Configuration Profiles

Improved Declarative Device Management for Migrated Instances

A "Federated" user account type has been added to Jamf Pro, designed for use with OIDC-based SSO through Jamf Account. This addition supports improvements to the Jamf Pro setup experience. Federated user accounts do not have a password and cannot be used for local login, Self Service login, or enrollments.

The resource center has been relocated to the sidebar in the Jamf Pro interface.

Jamf Pro API Changes and Enhancements

Change Request 509999 [Upgrading Jamf Pro from 11.21.1 to 11.24].

Description: [Copied from change 400463]

Details of maintenance: Upgrading Jamf Pro Server from 11.21.1 to 11.24. Note: This upgrade is performed by the UEM Team.

Benefit of change: This upgrade provides the following feature enhancements, bug fixes, and critical CVE vulnerability patches. (https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-11.24.0/page/New_Features_and_Enhancements.html)

Impact to customers: Jamf Pro console access and device enrollment capabilities for IT support teams may not be available during the upgrade.

Resolved Issues

[PI138122] Fixed: Configurations using passthrough authentication cause a password mismatch if a user's password is reset by a local administrator prior to logging in with Jamf Connect.

[PI143260] Fixed: Importing a configuration profile into Jamf Connect Configuration with the User Promotion Choices (UserPromotionChoices) setting in use causes the array for the setting to be replaced by the following text: (.

[PI143263, PI144134] Fixed: Jamf Connect presents the following one-time prompt on computers with macOS Tahoe 26.1 beta, both on the login window and on the desktop: "Self Service+ wants to use your confidential information stored in "Jamf Connect" in your keychain."

[PI143435] Fixed: When RapidIdentity is the identity provider, the Jamf Connect login window requests the local account password during the password verification workflow instead of the identity provider password.

Change Request 493421 Jamf Pro - Upgrading Jamf Connect to 3.5.0 for Athletics.

Description: Details of maintenance: Jamf Connect will be upgraded to 3.5.0 for Athletics devices.

Benefit of change: Jamf Connect will be on the latest supported version. This change will fix the "Jamf Connect Wants to access key "Jamf Connect" in your keychain" popup that many users have been receiving. Athletics was exempted from the previous change due to the need to test if their Entra tenant would still work with this change.

Impact to customers: Customers will see UI changes in the Jamf Connect login screen which does contain UI changes. These changes are outlined in this Knowledge Base article: Apple Device Management – MacOS Login with Jamf Connect

Change Request 460657 Jamf Pro - Upgrading Jamf Connect/Self-Service to 3.5.0/Self Service+.

Description: Details of maintenance: Jamf Connect will be upgraded to 3.5.0 and Self-Service will be upgraded to Self Service+.

Benefit of change: Jamf Connect and Self Service will be on the latest supported version. This change will fix the "Jamf Connect Wants to access key "Jamf Connect" in your keychain" popup that many users have been receiving.

Impact to customers: Customers will see UI changes in the Jamf Connect login screen and will have Self-Service replaced with Self Service+ which does contain UI changes. These changes are outlined in these two Knowledge Base articles: Apple Device Management – MacOS Login with Jamf Connect Apple Device Management – Using Apple Self Service+

Change Request 453104 Jamf Pro - Making Updated Code Maroon Version Available on Self-Service.

Description: Details of maintenance: The new version of Code Maroon will be made available in Self-Service replacing the older, out of date version. An Uninstaller named "Code Maroon - Uninstall" will also be made available. When Code Maroon is run, users will be presented with a list of locations. When a location is selected, the installer/script for that location will run. The installers are assigned to 11 different policies that only run via custom event triggers. These policies will be set to global but will not run unless a corresponding location is selected via Code Maroon.  These 11 location policies that will be set to global are: Coder Maroon - BCS Coder Maroon - College Station Coder Maroon - Corpus Christi Coder Maroon - Dallas Coder Maroon - HECM Coder Maroon - Houston Coder Maroon - Kingsville Coder Maroon -  Law Coder Maroon - McAllen Coder Maroon - RoundRock Coder Maroon - Temple

After installation the user will be asked for an optional restart to successfully complete the installation. This is made clear before and after the installation.

Benefit of change: The older version of Code Maroon is out of date and this new version will ensure that users will continue to receive alerts in the future. The uninstaller will also make it easier to uninstall the application if the user chooses to do so.

Impact to customers: None. The application will just be an optional download on the Self-Service Hub.

Change Request 445985 Jamf Pro - Deploying Proofpoint Version 4.4.2.76.

Description: Details of maintenance: The Proofpoint agent has been upgraded from 3.8 to 4.4.2.76. This change will be upgrading the version for targeted devices.

Benefit of Change: This will get devices on the latest version of proofpoint that contains proper macOS Tahoe compatibility.

Impact to customers: No impact to customers.

Change Request 440803 Stale Device Removal - Jamf devices.

Description: This change is to remove stale devices that have not been in communication with the Jamf Pro management server, or any other sensor. Devices that meet the criteria "Have not checked in since 1/1/2025" will be removed from the server. These devices will be cross-verified in Axonius to ensure no other service has detected these devices in use to rule out an issue with Jamf Pro communication.

--Benefit of Change: this will remove devices that may be included in reports unless specifically accounted for, skewing report numbers. It will also free up Jamf Pro licensing and allow for more accurate numbers for billing and reconcilliation.

Change Request 436896 Site and Prestage Deployment for Bush, Architecture, and Mays - JAMF.

Description: This change introduces new Jamf sites, Automated Device Enrollments, and prestage configurations for the Bush, Architecture, and Mays schools. By separating these colleges into their own managed environments, we can streamline deployments and improve scoping accuracy. This structure reduces manual effort for IT and supports more reliable, consistent device onboarding across all three groups.

Change Request 433317 Implement New Recast Management Server [MECM-1P-RCST-W1.auth.tamu.edu].

Description: Details of maintenance: This change consists of the implementation of a new Recast Management Server [MECM-1P-RCST-W1.auth.tamu.edu] and upgrade of existing Recast Console Extension agents on MECM Jump Servers and Recast Agents on workstations.

Degraded Recast Management Servers: mecm-1p-rcst-c1.auth.tamu.edu cm2-recast.as.tamu.edu

MECM Jump Servers: mgmt-3p-cst.auth.tamu.edu batcave.it.tamu.edu mgmt-2p-cst.ads.tamu.edu cm2.as.tamu.edu

Benefit of change: This change addresses issues with both former Recast Management Servers that were both in different states of degradation and could not be reverted to a functional state since no backup snapshot existed.

By implementing a new sever, its database is now on the primary sql.it.tamu.edu SQL server and the old servers may now be decommissioned.  The new server is on the latest Recast version 5.11.2511.1804, and agents and Recast Console Extensions will be upgraded on each MECM Jump Server. This brings alignment of each application version in accordance with the vendors specification for a properly configured environment.

The latest version includes several bug fixes and Right-Click Tools features outlined in the following release notes: https://docs.recastsoftware.com/help/recast-software-version-5-11-releases#recast-version-51125111804.

Impact to customers: There is no impact on campus faculty, staff, or students as it is a tool used by MECM admins. Recast Agents for OAL workstations will be upgraded and Unit Admins may deploy the new Recast Agent at their earliest convenience.