Posted on 03-26-2015 10:06 AM
We have network segments setup and have specified the distribution point for each segment. Each DP has a failover setup just in case. I'm noticing that for whatever reason when running policies through the command line using "sudo jamf policy" that it mounts a DP that it shouldn't be mounting (the old master DP). I've confirmed that the laptop does indeed have an IP address that falls within the proper network segment and so it should get the local DP, but it isn't.
Has anyone seen this before? Is there a way to determine and change the default distribution point on the client specifically?
EDIT: Just wanted the add that the policy does not specify a specific DP. It is set to run of each computer's default DP.
Posted on 03-27-2015 10:50 AM
@bpavlov Which IPs are you using for your network segments?
We have this working by creating are network segments based the "Reported IP" (the outgoing, public IP) as far as specifying which distribution point it should be using. If the network segments that you created are relying on the actual IP (i.e. the one handed out by your internal DHCP server), the default distribution point mapping won't work.
To do this, I've literally broken up the entire Internet spectrum from 1.1.1.1 to 255.255.255.255 into as many segments as required. For any public IP ranges that correspond to our office locations, I've specified the local DP to that location.
Hope that helps!
Posted on 06-30-2015 03:32 PM
OP - did you ever get a fix on this? We are finding identical issues in our environment starting only now. It used to work...
Posted on 07-01-2015 12:20 AM
https://macmule.com/2014/05/14/jss-using-wrong-distribution-points-after-v8-v9-upgrade/
Posted on 10-14-2016 10:54 AM
@Chris Even though this post is over a year old I just wanted to say THANKS! The instructions on Macmule fixed my issues.
Posted on 10-15-2016 12:38 AM
Awesome. :)