Skip to main content

My team is in the midst of migrating machines from our current Jamf Pro Server (ver 10.7) which is on a physical machine to our new Jamf Pro Server (ver 10.22.1) which is a VM in our data centre. We have tried using Jamf Migrator but we realized that only the data gets migrated but the machine is not installed with the new MDM from the Jamf Pro Server (ver 10.22.1). While researching on the ways to migrate, we chance upon the following guide from Jamf (https://www.jamf.com/jamf-nation/articles/122/migrating-to-another-server) but all three choices are not applicable to us as we are setting up from scratch.



Another method that we are trying to figure out is to push out a script which removes the current MDM, profile, etc. and within the same script, route the machine to enrol it to the new Jamf Pro. However, we are not sure on how to do this or if it is possible at all.



If we would like to enrol these machines (approximately 1100) to the new Jamf with none or little user intervention, can anyone kindly advise the best way to do this?

I don't quite see why you think that Method 3 is not applicable? This is the method I would use in your situation.

I think our team started the migration on a wrong path. We only came to know of this migration method much later after we have setup the new environment and started using it. Therefore our new server's DB has been populated and new machines got enrolled onto the new Jamf server while those that have been enrolled to our current Jamf server maintains. However, what we are trying to do is to migrate all the current machines to the new Jamf server.



Based on method 3, we would probably faced a 'which DB to use' issue. As well as step 8 in method 3 requires us to change the record on our DNS server. But since both server has its own IP and hostname, it will be an easy swap. Moreover, my team is not in charge of the DNS server. Hence, we foresee an issue here.



Anyway, our current Jamf Pro resides on a Mac Mini running MacOS while our new Jamf Pro is on a Windows VM. Although I would assume the difference in OS won't be an issue.

Hi



In this situation you have two things to do:



Migrate objects (policies, profiles etc.)



This you can do with the Jamf Migrator: https://github.com/jamf/JamfMigrator



Migrate computers (Reenroll)



This you can do with the ReEnroller tool: https://github.com/jamf/ReEnroller. You have to be careful with the UAMDM state. You'll have to approve the MDM profile after the reenrollment (System Preferences → Profiles → MDM Profile).



Hope this helps.

This looks like what I am looking for. Thank you anverhousseini :)

Terms & ConditionsCookie settings