![]() ![]() Enabled state of mobile device applications is not handled in the API, as a result all migrated mobile device applications will be enabled on the destination server whether it is enabled or disabled on the source.Saving of objects whos name contains a : (colon) will be saved using a (semi-colon).The Jamf Pro console prevents this as there should be a one to one mapping. The API allows for the creation of multiple packages, with different display names, to reference the same package file name.To migrate the actual package either use your browser, Jamf Admin, or ( ) Only package metadata (display name, file name, size.Users and usergroups used in policy limitations/exclusions do not migrate as the API does not provide that information.This causes issues re-migrating those objects as the names no longer match. ![]() Objects with trailing spaces in the name will migrate once but the process of uploading through the API removes those spaces.Also, within the packages payload, setting for the distribution point will not migrate. Policies - The Software Update payload does not migrate.Display names are dropped and additional keys/values are added by the Jamf API that results in a corrupt profile and failure in profile deployment. Approved System/Kernel Extension payloads do not migrate properly.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. 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.When migrating files be sure to open the 'raw' folder.ĭevices (computers and iOS), Groups, Policies, and Configuration Profiles can be targeted to a particular site. Username and password fields can be hidden/shown using the disclosure tringle on the left. 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 ![]()
0 Comments
Leave a Reply. |