+9I work at a large organization that has a tons of network zones. We are starting our deployment now and I am already tired of tracking down systems that are unable to connect to the distribution point because they are not assigned a distribution point.
Does anyone have a suggestion on the best way to identify machines that are reporting in from a new network segment and thus are not assigned to a Distribution Point.
Thank you
+16I sure wish there was an easy way to do this! I can't tell you how many times I'm NOT told about new locations and thus new network IP ranges that are set up somewhere, and all machines in that location start failing to download pkgs because they are seen as being "outside" the network and thus get bumped to our external DMZ sharepoint. But because they are in fact inside, they can't hit the share and the pkg download fails. It happens like every month at least. I would LOVE a way to track down internal IP ranges I'm not being told about so I can set them up in the Network Segments section, but I don't know of an effective way to do that.
The best advice I can give you is to make friends with someone on your network administration team and ask them if they would be so kind as to output a spreadsheet of all known IP ranges (start and end IPs) and what they correspond with for you to use.
+9A good suggestion, but sadly that won't work as I would have to make friends with about 20 people at different locations and I am not that likable. I went ahead and created a feature request instead.
https://www.jamf.com/jamf-nation/feature-requests/6864/identify-computers-that-do-not-have-an-assigned-distribution-point
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
