locked
Clients downloading from wrong Distribution Point RRS feed

  • Question

  • So I have networks configured in AD Sites and Services.  They are pulled into SCCM correctly.  I have assigned the networks to boundary groups and associated those boundary groups with a distribution point.  This was all done in SCCM 2012.  We have since upgraded that site to Current branch 1702 with hotfix KB4019926.  I have a single primary with 10 or so remote Distribution Points. 

    I have a larger piece of software 16+ GB configured as an Application.  When I start installing it is not going to the DP that is in its network based boundary group.  But rather it is falling back to the main SCCM primary server.  I do have application configured to allow for this just in case of DP being down it can still be installed by falling back to the primary site server.  But when the actual DP for the network boundary is present and running, I don't want it going to main primary site server

    Any help is appreciated.  I thought I read something about boundary groups way back when I upgraded, but then I haven't been able to find it.


    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.



    • Edited by Chase Roth Monday, August 21, 2017 3:02 PM
    Monday, August 21, 2017 2:56 PM

Answers

    1. Where did the "Default-Site-Boundary-Group<PS1>" come from?
    2. Where can I see how SCCM is determining which Boundary I am in/using?
    3. Can I delete the "Domain AD Site" AD boundary group and just use network ones? Is it needed?  Is it recommended to get rid of it?
    4. Were there issues with Boundaries in any of the upgrades from SCCM current branch?

    So this issue really reared its head this month (and we now realize previous months, but didn't know it was happening) when deploying Software Updates.  Our core WAN port at the main office was running 98% utilization because of all the traffic coming back and not using building DPs.  Last school year we did not have this issue. 

    So, as I mentioned in #3 above and in previous post, there was a Boundary Group left over from SCCM 2012 for my Default-First-Site-Name in Active Directory that I was asking if it was ok to delete.  Since no responses really helped, I ended up DELETING that Boundary Group to test since things were so bad.  Within minutes I began seeing traffic on the DPs (Task Manager -> Performance -> Ethernet) located out in the buildings where there was previously essentially no traffic.  Additionally, the utilization on the main Primary Site DP dropped significantly!

    I think that AD Boundary group was the issue.  I guess it caused an overlap so then it was just luck of the draw as to which DP it started talking with.  Maybe there is some priority that pointed to the Primary Site DP instead of Network based Boundary, I don't know.  Long story short it seems to be working.  Going to monitor a bit more before calling this fixed.


    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

    • Proposed as answer by Richard.Knight Tuesday, October 31, 2017 8:39 PM
    • Marked as answer by Chase Roth Thursday, November 2, 2017 3:34 PM
    Tuesday, October 31, 2017 8:33 PM

All replies

  • Hi, I have seen similar issues. Please try to delete and re-create the boundary group to see if this makes any difference.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    • Edited by Frank Dong Tuesday, August 22, 2017 2:30 AM
    Tuesday, August 22, 2017 2:29 AM
  • Hi, I have seen similar issues. Please try to delete and re-create the boundary group to see if this makes any difference.

    I deleted the boundary group and recreated it.  Tested downloading the large file again and it came from Primary site again and not the DP.  So I went and recreated ALL of my boundary groups just in case.  I noticed there is now a "Default-Site-Boundary-Group<PS1>" which connects to my primary site.  This was only created 2/16/2017 (and wasn't made by me), which may be when I went to current branch?  I also see my original "Domain AD Site" boundary group which has "Default-First-Site-Name" as the boundary and it pointing to the primary site.

    Could this be the reason it isn't working, as all networks are on the same Active Directory domain and site, "Default-First-Site-Name".  Would this take priority over the network ip base boundary groups?

    1. Where did the "Default-Site-Boundary-Group<PS1>" come from?
    2. Where can I see how SCCM is determining which Boundary I am in/using?
    3. Can I delete the "Domain AD Site" AD boundary group and just use network ones? Is it needed?  Is it recommended to get rid of it?
    4. Were there issues with Boundaries in any of the upgrades from SCCM current branch?
     

    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

    Tuesday, August 22, 2017 3:34 PM
  • Bump.

    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

    Wednesday, August 30, 2017 12:48 PM
  • The default site boundary group is introduced in current branch 1610. Mostly it's used by clients which is not in managed by any boundary/boundary group to locate site servers. Details information please read below:

    https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/boundary-groups


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 7, 2017 11:35 AM
  • I have a question here, which Sub-net your DP'S are in, I have a feeling that your machines are trying to get the content from the near by DP by any chance your Site is the nearest DP for your location Machines?

    What would I do remove the content from the SCCM dp and let it available only on the remote DP and see whether the machine get content only from there?


    Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

    Thursday, September 7, 2017 11:23 PM
  • I have a question here, which Sub-net your DP'S are in, I have a feeling that your machines are trying to get the content from the near by DP by any chance your Site is the nearest DP for your location Machines?

    What would I do remove the content from the SCCM dp and let it available only on the remote DP and see whether the machine get content only from there?


    Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

    Sorry for very delayed response.  First off, this appears to still be an issue.  I am having trouble even figuring where the clients are downloading from.  What log would I check to see where the Software Updates are being downloaded from?  Today we killed the network interface for our WAN releasing Software Updates even though I have a DP in every building that should be serving the content. 

    The DPs are located in the building with the client machines.  In many cases even on the same subnet. 

    Removing the content from main server DP is good idea, however, I do think I may have left a network or two using that server as default, so I'd need to be careful there.


    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

    Monday, October 30, 2017 8:09 PM
    1. Where did the "Default-Site-Boundary-Group<PS1>" come from?
    2. Where can I see how SCCM is determining which Boundary I am in/using?
    3. Can I delete the "Domain AD Site" AD boundary group and just use network ones? Is it needed?  Is it recommended to get rid of it?
    4. Were there issues with Boundaries in any of the upgrades from SCCM current branch?

    So this issue really reared its head this month (and we now realize previous months, but didn't know it was happening) when deploying Software Updates.  Our core WAN port at the main office was running 98% utilization because of all the traffic coming back and not using building DPs.  Last school year we did not have this issue. 

    So, as I mentioned in #3 above and in previous post, there was a Boundary Group left over from SCCM 2012 for my Default-First-Site-Name in Active Directory that I was asking if it was ok to delete.  Since no responses really helped, I ended up DELETING that Boundary Group to test since things were so bad.  Within minutes I began seeing traffic on the DPs (Task Manager -> Performance -> Ethernet) located out in the buildings where there was previously essentially no traffic.  Additionally, the utilization on the main Primary Site DP dropped significantly!

    I think that AD Boundary group was the issue.  I guess it caused an overlap so then it was just luck of the draw as to which DP it started talking with.  Maybe there is some priority that pointed to the Primary Site DP instead of Network based Boundary, I don't know.  Long story short it seems to be working.  Going to monitor a bit more before calling this fixed.


    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

    • Proposed as answer by Richard.Knight Tuesday, October 31, 2017 8:39 PM
    • Marked as answer by Chase Roth Thursday, November 2, 2017 3:34 PM
    Tuesday, October 31, 2017 8:33 PM
  • It definitely seems to be spreading the load again.  I am going to call this for now!

    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

    Thursday, November 2, 2017 3:34 PM