Switching distribution point master to JDS

UESCDurandal
Contributor II

We've recently upgraded from 8.73 to 9.3 and have setup a new JDS. Manually instructing Casper Remote and JSS Policies to install via the JDS have proved successful, so we're ready to set the JDS as the master distribution point.

However, since setting the JDS as the master in JSS I've found that all of our policies and remote sessions continue to use the classic file share distribution points. Logs show that it doesn't even try to use the JDS. None of these policies have manual distribution point settings.

Any ideas on what's wrong?

1 ACCEPTED SOLUTION

UESCDurandal
Contributor II

Turned out to be a problem with our MySQL tables resulting from the 9.3 upgrade. Worked with JAMF Support to resolve.

View solution in original post

5 REPLIES 5

JRM
Contributor

Clients have to update before they can even see the JDS. Once that is complete, you need to have a JDS set as the preferred DP in network settings. Check those first.

were_wulff
Valued Contributor II

Hey @UESCDurandal ,

Just seconding @JRM ’s suggestions!

If we go to the Gear Icon >> Network Organization >> Network Segments we’ll want to look at any network segments specified and make sure they’re not set to default to the old distribution point (unless you want devices in that IP range to default there, of course!).

Distribution point an also be overridden in policies as well.

If we open up a policy and go to the Packages payload, there is a drop down menu for Distribution Point.

If the file share distribution point is specifically selected there, computers running that policy will always use the file share distribution point as the policy’s setting overrides the default.

Even after those changes, we’ll still want to give it a bit of time so all the clients have a chance to check in and see that there is a new distribution point.

If we’ve checked those things and that doesn’t seem to be the issue, I’d recommend getting in touch with your Technical Account Manager to dig into it a little more.

Thanks!
Amanda Wulff
JAMF Software Support

UESCDurandal
Contributor II

Turned out to be a problem with our MySQL tables resulting from the 9.3 upgrade. Worked with JAMF Support to resolve.

bentoms
Esteemed Contributor
Esteemed Contributor

UESCDurandal
Contributor II

@bentoms, Aye. That it was. Well done for documenting the fix for others!