#JAMF PRO CLOUD UPDATE#

Institutional disk encryptions that contain the private key cannot be migrated.Migrating groups several times should allow all the nested groups to migrate before the parent group. Migrating smart/static groups with criteria containing groups will fail if the parent group tries to migrate before the group in the criteria.As each item is migrited it will overwrite the previous item with the same name.

#JAMF PRO CLOUD UPDATE#

If endpoints (computers, policies, configuration profiles.) have duplicate names on the source server issues will arise if the app is used to update those items from the source to destination server.Patch management is not available through the API impacting smart groups dependent on patch management extension attributes.Only AFP and SMB shares can be migrated.Icons associated with Mac App Store apps are not migrated as the API does not support it.Certificate used for LDAPS does not migrate.A password can be supplied for each service account, but credentials may need to be reset on the destination server for more complex configurations. Passwords can not be extracted through the API which impacts migrating distribution points, computer management account, account used for LDAP.For example a script migrated but the category it was associated with on the source server is missing on the destination server. This is an indication some dependency was missing. You may see a difference between the color of the text and the progress bar.

Groups, Policies, and Configuration Profiles can be targeted to a particular site.įeedback in the GUI gives a simplistic overview of the success of a transfer: If an item (based on name) within a category exists on both source and destination, the destination item will be updated with values from the source server. Migrate items from one Jamf server, or XML file(s), to another. A tool to migrate data granularly between Jamf Pro servers

Jamf pro cloud