Below you will find the Steps to migrate to from the legacy Jamf Pro integration to the current integration. This is only required if you have previously configured using the legacy Jamf Pro integration. This article assumes that you are familiar with the steps required to configure Jamf and Carousel:
In Carousel: Create a new external authentication for “jamf Pro”, it looks the same as the “jamf Pro (Legacy)” authentication, but under the hood it is using the new bearer authentication available in Jamf Pro 10.35 and newer. Do not delete the “jamf Pro (Legacy)” authentication yet, to make the next few steps easier.
In Jamf Pro: Create new static device groups with descriptive names like “Carousel <channel/zone> - Single App Mode” or “Carousel <channel/zone> - Disable AirPlay”. This may not be necessary if you’ve already got appropriate static device groups available. It’s recommended you create a new group for each full alert zone you configure in Carousel, and name the group with the full alert zone name or the channel name so it is easy to find.
In Jamf Pro: Under Configuration Profiles, go into each profile you were previously targeting in Carousel and scope them to the groups from Step 2. (Configuration Profiles → <select a profile> → Scope → Targets → Edit → + Add → Mobile Device Groups → select “Add” on the row for the desired group). If you have a lot of full alert zones in Carousel, you may need to create additional configuration profiles to be targeted appropriately by the static device groups.
In Carousel: Go to each full alert zone and change select the group from Step 2 appropriate for each zone. If you have a lot of zones, this will be the most time consuming step. You should also remove the selected configuration profile at this point because you won’t be able to complete step 5 until the profiles are no longer referenced. NOTE: until you complete step 5, any configuration profiles removed in this step will no longer apply if full screen alert bulletins are active, it is recommended you set aside enough time to complete steps 4 and 5 as quickly as possible so you have minimal downtime during non-critical hours.
In Carousel: Once you’re satisfied the configuration matches the old integration, you can delete the “jamf Pro (Legacy)” external authentication from Carousel. NOTE: until this point Carousel will continue to trigger through this legacy integration, this is the step which will roll over to the new integration and new authentication model. Once you delete the legacy external authentication, the new integration will be used.
In Jamf Pro: Cleanup: once the legacy integration is deleted from Carousel, now is the step where you can do what we previously told you not to do: go to Static Device Groups and then select each one that are named like “Carousel-<site name>-DO_NOT_DELETE-<numbers>-<more numbers>” and delete them. If the are still scoped by a configuration profile you may have to remove that first. With the new integration, these groups are no longer needed and can be cleaned up so you don’t have a mess on your Jamf Pro instance.