Resolved Issues

[PI107846] [PI-002765] Deleting a device record while that device is actively communicating with the Jamf Pro server now functions as expected and no longer creates orphaned device records in the database.

[PI112293] During registration with Microsoft device compliance, users will no longer see the "No Azure tenant set up" error.

[PI115210] After editing an API client in API Roles and Clients settings, the Rotate Client Secret button no longer unexpectedly changes to a Generate Client Secret button.

[PI117129] When using an API workflow to add or remove devices to a static group, profiles that are scoped to "All Devices" are now sent once instead of multiple times.

[PI118037] API client secrets no longer need to be regenerated after a role is added in order for the changes to take effect.

[PI119885] Upgrades and new installations of Jamf Pro on Windows now initialize as expected when Jamf Pro is not installed on the C:\ drive.

[PI120318] "Item Failed" notifications now clear as expected from Self Service classic for macOS.

[PI122408] The Jamf Pro server log no longer displays "401" errors when Jamf Engage is enabled.

[PI122416] When creating or modifying a configuration profile with a VPN payload that uses "Password" for the User Authentication type, Jamf Pro now correctly creates the profile with a valid AuthenticationMethod key.

This resolved issue is also included in Jamf Pro 11.12.1 or later.

[PI123933] Jamf Pro no longer fails to display the scope for newly created deployable objects and saves scoping changes for existing objects as expected.

This resolved issue is also included in Jamf Pro 11.12.1 or later.

[PI124225] Upgrading Jamf Pro no longer unexpectedly alters the required privileges necessary for the Jamf Parent and Jamf Teacher apps to function.

This resolved issue is also included in Jamf Pro 11.12.1 or later.