locked
SCCM Management Point Explanation RRS feed

  • Question

  • All

    We have the following setup in our environment

    One Site Name/Code
    10 Collections each relating to an Active Directory Site
    2 Distribution Point Servers in our Main Datacentre
    Distribution Point in each 10 Sites

    One thing i notice however is that if i expand Site based collections and go into a site to see the clients Listed, if i click on a Client in particular i notice from the client details at the bottom that the Management Point states one of the Distribution Points we have in the datacentre.

    i would of thought the management point for the client in Site A should be the Distribution Point in Site A? and not a DP ni the Datacentre

    In the Boundary Group for say Site A, the System Site Name is the Distribution Point for Site A

    Is anyone able to advise that this is by design for the client management point to be a distribution point outside the site? i am hoping that updates and client rollouts etc do not have to travel across the network when they should be getting the info form the onsite DP

    hope this makes sense and that it can be clarified

    Barrie

    Wednesday, November 25, 2015 9:56 AM

Answers

All replies

  • Is each DP also a MP? If not: how many MPs are there?

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, November 25, 2015 10:39 AM
  • Hi Torsten

    Thanks for Replying

    Just navigated to Server and System Roles and realised the following:

    10 x DP's all configured as Site System and Distribution Point

    2 Additional Server configured as Site System, Distribution point, Management Point and Component Server

    1 x Primary Server configured with Component Server, Site Server and Site System

    1 x WSUS Server with Software Update Point, Site System, Component Server

    1 x SQL Server Site System, Component Server, Reporting Services point, Site Database Server

    Therefore the clients are probably reporting the name of the nearest Management Point as the onsite DP's are only Site System and DP's (highlighted Bold)I should of researched this beforehand, i have inherited the management of SCCM since taking it from the original external contractors who Installed and Configured it

    I presume the above layout doesn't cause any issues

    Thanks Again

    Barrie

    Wednesday, November 25, 2015 10:56 AM
  • Hi Barrie,

    Your understanding is correct. When the SCCM agent looks for a Management Point, it will query the Active Directory and use the MPURL string to find the list of Management points and register with the closest one. If they do not find an MP in their site, then they will skip to the next one. With that said, it can be concluded that a client cannot be bound to a Management Point but can be bound to a Distribution Point which can be tagged under Boundary group settings.

    https://technet.microsoft.com/en-in/library/gg682055.aspx

    Regards,

    Anuj


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All. Regards, AJ (MSFT)

    Wednesday, November 25, 2015 11:14 AM
  • Hi Anuj

    Thanks for the clarification, the Boundary Group contains the boundary that obtains clients from Site A in Active Directory Sites and Services - These clients appear as i would expect in the correct Collection

    The Distribution Point for Site A is Tagged with the Boundary group for Site A

    Initially i thought the Distribution Point would deal with all client rollouts and other things, but it appears that the clients locate a Management Point to deal with Client Communications and the Distirbution Point is basically a local onsite area where deployed packages are held for distribution, by default clients in Site A will have the Packages deployed form their onsite DP but the client comms are with the MP it locates

    Thanks again for your time, im getting there slowly! :-)

    Barrie

    Wednesday, November 25, 2015 11:46 AM
  • "and register with the closest one"

    This is not correct. By default, MP selection is completely random.

    You can assign MPs based on boundary group starting with R2 SP1/SP2 though (this is not enabled by default though).


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

    Wednesday, November 25, 2015 2:43 PM
  • You can assign MPs based on boundary group starting with R2 SP1/SP2 though (this is not enabled by default though).


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

    As an addition to Jason's statement, this is referenced as Prefered Management Point :

    http://www.systemcenterdudes.com/sccm-2012-r2-sp1-new-features/


    Benoit Lecours | Blog: System Center Dudes

    Wednesday, November 25, 2015 2:55 PM
  • Hi Barrie,

    Please review the following for further clarification.

    http://blogs.technet.com/b/jchalfant/archive/2014/09/22/management-point-affinity-added-in-configmgr-2012-r2-cu3.aspx

    Anuj


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All. Regards, AJ (MSFT)

    Wednesday, November 25, 2015 3:01 PM
  • Jason / Benoit

    Many thanks for this, i note we have SP2 and have the options mentioned in the SystemCenterDudes website

    Great Stuff!!

    Barrie

    Wednesday, November 25, 2015 3:06 PM