What's New

Correction—Updated 26 July 2018

InnoDB Storage Engine for MySQL

Important: If installing or upgrading to Jamf Pro 10.6.0, you must change the default MySQL settings to avoid performance issues. See the "Configure MySQL" section of the Creating the Jamf Pro Database Knowledge Base article for instructions.

Active Directory Certificate Services (AD CS) Integration

You can now add Active Directory Certificate Services (AD CS) as a PKI Provider in Jamf Pro. This allows you to use AD CS as the certificate authority (CA) for distributing certificates to computers and mobile devices via configuration profiles. Integrating with AD CS involves installing the Jamf AD CS Connector before configuring settings in Jamf Pro to enable communication between Jamf Pro and AD CS using the Jamf AD CS Connector.

After communication has been established, you can use Jamf Pro to distribute certificates via configuration profiles using AD CS as the CA. In addition, you can distribute in-house apps developed with the Jamf Certificate SDK to establish identities to support certificate-based authentication to perform Single Sign-On (SSO) or other actions specific to your environment. Jamf Pro also allows you to apply a Managed App Configuration to the app during distribution to enable the app to request the necessary certificates.

For more information about integrating with AD CS, see the Integrating with Active Directory Certificate Services (AD CS) Using Jamf Pro technical paper.

For more information about the Jamf Certificate SDK, see the following website:

InnoDB Storage Engine for MySQL

InnoDB is now the default storage engine for fresh installs of the MySQL database and any new database tables. InnoDB provides a number of benefits over MyISAM, including:

  • Improved stability

  • Support for transactions

  • Better performance

  • Improved data management for large deployments

InnoDB will be required in an upcoming version of Jamf Pro, however, you can convert your database from MyISAM to InnoDB any time before then.

For questions or assistance converting your database to InnoDB, contact your Jamf account representative.

For more information about InnoDB, see the following website:

Jamf Pro API Changes and Enhancements

The Jamf Pro API (formerly the Universal API) beta is open for user testing. The base URL for the Jamf Pro API is /uapi. To access the Jamf Pro API documentation, append "/uapi/doc" to your Jamf Pro URL. For example:


Note: As the Jamf Pro API continues to be developed, changes will be made in future releases that may impact or break functionality. We strongly recommend that you test existing workflows using the Jamf Pro API before upgrading your production environment.

The following changes have been made to the Jamf Pro API:

  • The priority key in the Script model now only accepts the following enumerations: BEFORE, AFTER, and AT_REBOOT.

  • The following endpoints now accept the page, pagesize, and sort query parameters:

    • GET /settings/obj/buildings

    • GET /settings/obj/enrollment/languages

    • GET /settings/obj/enrollment/accessGroups

    • GET /settings/scripts

In addition, the response model for these endpoints now includes the totalCount key and results key. The results key displays the page results.

  • The following endpoints have been removed:

    • POST /settings/searchBuildings

    • POST /settings/scripts/search

Jamf Self Service for iOS

Jamf Self Service for iOS 10.5.1 includes the following enhancements:

  • Localization Support—Jamf Self Service for iOS can now be viewed in Chinese, French, German, and Japanese.

  • Accessibility Improvements—VoiceOver support in Jamf Self Service for iOS has been improved.

  • Category Sorting—The “All” category in Jamf Self Service for iOS now sorts content alphanumerically.

Note: Jamf Self Service for iOS 10.5.1 is the latest version of the Self Service app. It will be available in the App Store when it is approved by Apple.

Other Changes and Enhancements

  • Due to the requirement for App Store apps to support 64-bit on mobile devices with iOS 11 or later, a compatibility warning displays in Jamf Pro when a 32-bit app is being configured.

  • Improved the handling of Managed App Configuration with the Install App MDM command.

  • Improved the handling of computer configuration profiles with an Approved Kernel Extensions payload after User Approved MDM is enabled.

  • The ability to upload and deploy provisioning profiles using Jamf Pro has been reinstated.

  • Renamed the "Microsoft Intune Integration" global setting to "Conditional Access".

  • Renamed the "Microsoft Intune Integration" tab to "macOS Intune Integration".

  • Early access feature: The Jamf Pro iOS Azure AD Integration is an early access feature now available for testing. By integrating Jamf Pro with Azure AD, organizations can support conditional access policies configured in Azure AD for iOS devices.
    Warning: The Jamf Pro iOS Azure AD Integration early access feature should not be used in production environments. For information about testing this feature in a non-production environment, contact your Jamf account representative.

Further Considerations

  • Privileges associated with new features in Jamf Pro are disabled by default.

  • It is recommended that you clear your browser's cache after upgrading Jamf Pro to ensure that the Jamf Pro interface displays correctly.

Copyright     Privacy Policy     Terms of Use     Security
© copyright 2002-2018 Jamf. All rights reserved.