What's New

Updated 1 August 2019

The following endpoints were added to the Jamf Pro API Changes and Enhancements section:

  • POST /system/initialize-database-connection

  • GET /startup-status

Java 11 Requirement

Beginning with Jamf Pro 10.14.0, Java 11 is required for Jamf Pro server environments. Before upgrading to Jamf Pro 10.14.0, you must migrate to one of the following distributions of Java 11:

  • OpenJDK 11 (recommended)

  • Oracle Java 11 (minimum)

For more information, see the Migrating to Java 11 Knowledge Base article. See What's Changed for additional information to consider before upgrading.

Disable a Computer Extension Attribute with the Script Input Type

You can now disable computer extension attributes with the script input type. Disabling extension attributes can help when troubleshooting processes. To disable an extension attribute, deselect the Enabled (script input type only) checkbox for the extension attribute you want to disable. You also have the option of retaining or deleting data collected by the extension attribute before disabling it.

For more information, see the Computer Extension Attributes section in the Jamf Pro Administrator's Guide.

Integration with the Jamf Parent App

Jamf Parent, when integrated with Jamf Pro, allows parents to have limited management of their students' school-issued mobile devices. Parents can download the free Jamf Parent app from the App Store on iOS devices. Using Jamf Parent, parents can restrict or allow apps and websites on students' devices. Parents can add students' devices to Jamf Parent by scanning a QR code in Self Service. Administrators can limit management by Jamf Parent by configuring days and times to restrict Jamf Parent usage. You can also remove restrictions set by Jamf Parent or Jamf Parent management capabilities from one or more student devices by using a mass action.

For more information, see the Integrating Jamf Parent with Jamf Pro section in the Jamf Pro Administrator's Guide.

Jamf Self Service for iOS Enhancement

App Request

You can now enable a select group of users to request iPad apps directly from Jamf Self Service for iOS. This feature is useful for environments such as schools, where you may want to empower teachers to request educational apps on behalf of the students in their classrooms.

Using the App Request settings, you can customize how the request form displays in Self Service, who can submit requests, and who gets notified once a request is submitted. To access this feature in Jamf Pro, navigate to Settings > Self Service > App Request.

Note: Requesters must be using an iPad with Self Service 10.9.0 or later to access the App Request feature. Self Service 10.9.0 will be available in the App Store once it is approved by Apple.

For more information, see the Enabling App Request section in the Jamf Pro Administrator's Guide.

PreStage Enrollment Enhancements

Additional Skip Steps

You can now select the following skip steps for computer and mobile device PreStage enrollments:

  • Screen Time (macOS only)
    This feature requires macOS 10.15, which is currently in beta and subject to general availability from Apple.

  • Get Started (iOS only)
    This feature requires iOS 13, which is currently in beta and subject to general availability from Apple.

  • Express Language (iOS only)
    This feature requires iOS 13, which is currently in beta and subject to general availability from Apple.

  • Preferred Language (iOS only)
    This feature requires iOS 13, which is currently in beta and subject to general availability from Apple.

  • Appearance (iOS only)
    This feature requires iOS 13, which is currently in beta and subject to general availability from Apple.

Multiple Values LDAP Extension Attribute Mapping

When the inventory collection settings in Jamf Pro are configured to collect user and location information from LDAP, you can now map an LDAP server attribute that is defined with multiple values, for example memberOf, to a new extension attribute. The values will be displayed in the inventory for a computer or mobile device after it checks with Jamf Pro. The multiple values can be used when creating smart groups and advanced searches with the extension attribute criteria and the “has" and "does not have” operators.

This feature is available only for newly added extension attributes. If the existing LDAP server configuration returns multiple values for the mapped parameter, you must define a new extension attribute and update your groups and searches.

Important: For the LDAP multi-value extension attribute to work correctly, the LDAP server configuration cannot contain the sequence of repeating vertical-bar characters (ASCII code 124, HTML entity = |).

Added Criteria for Smart Groups and Advanced Searches

You can now create a smart group or advanced search for computers or mobile devices with the Certificate Issuer criteria.

You can use the Certificate Issuer criteria to determine which certificate authority is issuing certificates to devices in your environment. To view the value of this setting, navigate to the Certificates category of a device’s inventory information, and then click on the certificate. The certificate issuer is displayed under the CA Configuration heading.

Jamf Pro Server Tools 2.4.3

The Jamf Pro 10.14.0 installers include Jamf Pro Server Tools 2.4.3. The Jamf Pro Server Tools GUI now requires Java 11.

Inventory Preload Enhancement

Extension attributes are now displayed in the CSV file downloaded from Inventory Preload active data.

Jamf Pro API Changes and Enhancements

The Jamf Pro 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: https://jss.instancename.com:8443/uapi/doc

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 encourage that you test existing workflows using the Jamf Pro API before upgrading your production environment.

  • The following endpoints were added:

    • GET /v1/advanced-user-content-searches

    • POST /v1/advanced-user-content-searches

    • GET /v1/advanced-user-content-searches/{id}

    • DELETE /v1/advanced-user-content-searches/{id}

    • PUT /v1/advanced-user-content-searches

    • GET /v1/app-request/settings

    • PUT /v1/app-request/settings

    • GET /v1/app-request/settings/form-input-fields

    • POST /v1/app-request/settings/form-input-fields

    • GET /v1/app-request/settings/form-input-fields/{id}

    • PUT /v1/app-request/settings/form-input-fields/{id}

    • DELETE /v1/app-request/settings/form-input-fields/{id}

    • GET /v1/computer-prestages

    • POST /v1/computer-prestages

    • GET /v1/computer-prestages/{id}

    • PUT /v1/computer-prestages/{id}

    • DELETE /v1/computer-prestages/{id}

    • GET /v1/computer-prestages/scope

    • GET /v1/computer-prestages/{id}/scope

    • PUT /v1/computer-prestages/{id}/scope

    • POST /v1/computer-prestages/{id}/scope

    • DELETE /v1/computer-prestages/{id}/scope

    • POST /system/initialize-database-connection

    • POST /v1/mobile-device-prestages/{id}/attachments

    • DELETE /v1/mobile-device-prestages/{id}/attachments

    • GET /v1/mobile-device-prestages/{id}/scope

    • PUT /v1/mobile-device-prestages/{id}/scope

    • POST /v1/mobile-device-prestages/{id}/scope

    • DELETE /v1/mobile-device-prestages/{id}/scope

    • POST /v1/smart-mobile-device-groups/{id}/recalculate

    • POST /v1/mobile-devices/{id}/recalculate-smart-groups

    • GET /v1/parent-app

    • PUT /v1/parent-app

    • GET /v1/parent-app/history

    • POST /v1/parent-app/history

    • GET /startup-status

  • The following endpoints are marked as deprecated:

    • POST /mobileDevice/obj/smartgroup/{id}/recalculate

    • POST /mobileDevice/obj/mobileDevice/{id}/recalculateSmartGroups

For more information, see the Jamf Pro API documentation and the Jamf Pro Developer Portal.

Other Changes and Enhancements

  • Improvements to restricted software cause restricted processes to be detected faster.

  • The Jamf AAD now caches the Azure Active Directory ID so users must only provide a password to sign in.

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-2019 Jamf. All rights reserved.