locked
Multiple Distribution Ponts in same VLan RRS feed

  • Question

  • Hello,

    In our school environment we have one network divided in multiple vlans

    The school buildings are wireless connected to each other.  First we tried to set up one SCCM server to deploy OS and software in the whole school.  Nevertheless the TFTP was to slow for the wireless connections.  So we had to set up distribution points on the locations to speed up the work.

    The DHCP server is in VLAN 10.  So to connect to the distibutionpoint we had to set the option 66 and 67 in DHCP to connect to the DP in an other VLAN.

    So far so good.

    In one Vlan we have about 4 locations wireless connected.  So we will place a distributionpoint in each location.

    How wil can we set how the clients go to the correct DP?

    SCCM server is located in VLAN 10 : 10.10.250.250

    Distribution points in VLAN 26

    DP1: 10.26.250.250

    DP2: 10.26.250.251

    DP3 : 10.26.250.252

    DP4 : 10.26.250.253

     

    DHCP option 66 for is set to 10.26.250.250

     

    Thanks

    Manuel

     

    Sunday, January 22, 2017 2:46 PM

All replies

  • You are not going to like this answer but How exactly does a wireless client know that the DP is local to them? Based on you network designed there is absolutely no way for a wireless client to know which DP is closest to them. So they will randomly pick one and 3 times out of 4 they will pick one in another building.  In order to fix this you need to fix you wireless network so that each building has its own subnet.


    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    • Proposed as answer by Garth JonesMVP Saturday, February 4, 2017 4:48 PM
    Sunday, January 22, 2017 5:04 PM
  • Also, TFTP and DHCP have *nothing* to do with content distribution and distribution points. Are you actually wanting to know about PXE instead?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Sunday, January 22, 2017 10:14 PM
  • Hello,

    Thx for your answer.  The clients are all wired, not wireless as you mention in your reply.  Does that make a difference?

    Manuel

    Monday, January 23, 2017 8:38 AM
  • Hello,

    Thx for your answer.  The clients are all wired, not wireless as you mention in your reply.  Does that make a difference?

    Manue


    sorry no it doesn't. If that all share the same subnet, how exactly will they know which dp is the closest to them?

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Monday, January 23, 2017 12:55 PM
  • To accomplish what you want would require each Dp to be pxe enabled and set the DHCP option 66 as a scope option for each client Vlan to the IP of the DP you want them to use. But if all your clients are on one vlan\subnet then Garth is correct.

    Friday, February 3, 2017 2:36 AM
  • 1. Depending on the subnets or IP ranges for your clients, create boundaries (IP subnet or IP range based),

    2. Create four boundary groups representing each of your four locations.

    3. Now assign boundaries to their respective boundary groups based on locations

    4. Finally assign respective DPs based on their locations and expected preferred DPs to those boundary groups.

    Any client from a specific boundary (based on IP subnet or IP range would always look for a preferred DP from it's assigned boundary group.

    Saturday, February 4, 2017 5:04 AM
  • How does any of that help? Please read the OP. His locations do not have their own IP spaces so not of what you wrote above helps.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, February 4, 2017 5:33 AM
  • I apologize if I'm mistaken reading the original post. As long as the clients are on network, and can communicate to a site server and site systems, my above proposed solution should help clients finding their respective preferred clients. Since Manuel confirmed the clients are wired connected, and even if the clients are on a same subnet, we could always create boundaries based on IP ranges to resolve the issue.
    Saturday, February 4, 2017 6:44 AM
  • Thanks everyone for your help.

    We solved this problem by setting another vlan for each location.  We placed a DP for each location.  Everything works perfect now

    • Proposed as answer by Garth JonesMVP Saturday, February 4, 2017 4:48 PM
    Saturday, February 4, 2017 1:28 PM
  • It's not about wired vs. wireless necessarily, it's about, as noted, shared ip spaces between the locations so no, once again, there is no way to distinguish as Garth has already pointed out.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, February 4, 2017 2:39 PM