discoveryhoogl.blogg.se

Jamf pro tools
Jamf pro tools












jamf pro tools
  1. #Jamf pro tools update#
  2. #Jamf pro tools Patch#
  3. #Jamf pro tools password#
  4. #Jamf pro tools mac#

Only 'top-level' dependencies are checked. They'll be listed with a format of: policy name (ID)Īlso, policies may have their dependencies checked/migrated using the Migrate Dependencies button. Note: Policies are listed along with the their ID.

jamf pro tools

For example you might only want to transfer 4 new scripts from a larger pool of existing scripts. The 'Selective' tab provides the ability to select a subset of items within a category. 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.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.

jamf pro tools

#Jamf pro tools update#

  • Policies - The Software Update payload does not migrate.
  • They may appear to migrate but fail when being deployed.
  • System Extensions do not migrate properly.
  • Display nanes are dropped and additional keys/values are added by the Jamf API that results in a corrupt profle and failure in profile deployment.
  • Approved 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.
  • #Jamf pro tools Patch#

    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.

    #Jamf pro tools mac#

    Icons associated with Mac App Store apps are not migrated (can't be migrated).Certificate used for LDAPS does not migrate.

    jamf pro tools

    #Jamf pro tools password#

    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 tools