Skip to main content
Jamf Nation, hosted by Jamf, is the largest Apple IT management community in the world. Dialog with your fellow IT professionals, gain insight about Apple device deployments, share best practices and bounce ideas off each other. Join the conversation.

Changing JDS Hierarchy

Disclaimer: This article is no longer being updated. The Jamf Distribution Server was discontinued at the end of 2017.

Overview

The JSS allows you to modify your JDS hierarchy by changing which JDS instance is the root and changing the parent for non-root JDS instances. Before changing your JDS hierarchy, it is important to understand the way JDS instances and the files on them are affected by the change.

Versions Affected

Casper Suite v9.0 or later

Changing the Root JDS Instance

The root JDS instance is at the top of the JDS hierarchy. Other JDS instances use the root as the authoritative source for all files.

By default, the first JDS instance you install is the root. You can make a different instance the root at any time. You may want to ensure that a JDS instance has all files before making it the root. If the root instance is missing files, other instances will fail to replicate the missing files.

The following diagrams show how the changing the root instance affects the JDS hierarchy. Diagram 1 shows a JDS hierarchy in which "A" is the root. Diagram 2 shows how the hierarchy changes after making "B" the root.

external image link

Changing the Parent of a Non-Root JDS Instance

The following diagrams show how changing the parent of a non-root JDS instance affects the JDS hierarchy. Diagram 3 shows a JDS hierarchy in which the parent of "F" is "D". Diagram 4 shows how the hierarchy changes after changing the parent of "F" to "E".

external image link

If the JDS instance whose parent is changing ("F") and all of its child JDS instances ("G" and "H") are configured to replicate the contents of their parents, files will be added and/or removed as needed so that they continue to match their parents.

For example, if "F", "G", and "H" are all configured to replicate the entire contents of their parents:

  • Files that are on "D" but not on "E" are removed from "F".
  • Files that are on "E" but not on "D" are added to "F".

If the JDS instance whose parent is changing ("F") or any of its child JDS instances ("G" and "H") are configured to replicate specific files, files that are on the old parent but not on the new parent will be added where necessary so that none of the specified files are removed.

For example, if "F" is configured to replicate specific files, and one of the specified files is not on "E", the file will be added to "E" and "C".

Like Comment