#Jamf pro mac install

ReEnroller will now create a new enrolment invitation on the destination server and enrol to it.If this fails too, ReEnroller will revert the enrolment back to the source server.This runs an unmanage command – the only way to remove a DEP un-removable MDM Profile If this fails, it’ll try and call the MDM API removal policy on the source server.If MDM enrolled, it will now try a local removal of the MDM Profile.ReEnroller will now move the current Jamf enrolment pieces to one side.ReEnroller will now launch and start doing its thing:.Due to this, I’d suggest added a ‘policy completion’ message to the policy to let users know the rest will run in the background.

#Jamf pro mac install

The policy will install the ReEnroller package and “Completes”.User triggers the ReEnroller package installation workflow.With the configuration I’ve talked through, the process that the ReEnroller will carry out is: So if you followed my guide from last time, you should hopefully have a working migration process. This part will look to cover the process and some basic troubleshooting, as well as some post migration tasks. Part 1 can be found here and covers the initial setup. So this is part 2 of my mini series on using ReEnroller. Migrating macOS Devi… on Migrating macOS Devices from o…ĭazwallace on Moving devices from Adobe Shar… Richard Glaser on Changes to Docker Desktop for… Stephan Peterson on Submit Jamf inventory update o… Jamf Pro, Intune* and the Jamf Cloud Connectorĭeploying Docker Des… on Changes to Docker Desktop for….Recommended workflow to deploy Adobe software with Jamf Pro.Submit Jamf inventory update on OS changes.