locked
Clients picking random Management Points instead of the local MP RRS feed

  • Question

  • We are having an issue where our clients are selecting MPs outside of their boundary. We have one primary site located at corporate with site servers at each local site (DP/MP/SMP) and AD Site boundaries set for each (no secondary sites). I've verified that none of the AD site subnets are overlapping and the clients correctly identify that they are located in the local site's AD site. When I go to http://localsiteserver/sms_mp/.sms_aut?mplist, I get the following:

    <MPList>
    - <MP Name="ATLMAGNAS2.US.ECC.ADS" FQDN="ATLMAGNAS2.us.ecc.ads">
    <Version>7711</Version>
    - <Capabilities SchemaVersion="1.0">
    <Property Name="SSLState" Value="0" />
    </Capabilities>
    </MP>
    - <MP Name="CORPAPSCCM.US.ECC.ADS" FQDN="CORPAPSCCM.us.ecc.ads">
    <Version>7711</Version>
    - <Capabilities SchemaVersion="1.0">
    <Property Name="SSLState" Value="0" />
    </Capabilities>
    </MP>
    - <MP Name="CORPNAS3.US.ECC.ADS" FQDN="CORPNAS3.us.ecc.ads">
    <Version>7711</Version>
    - <Capabilities SchemaVersion="1.0">
    <Property Name="SSLState" Value="0" />
    </Capabilities>
    </MP>
    - <MP Name="IMMAGNAS2.US.ECC.ADS" FQDN="immagnas2.us.ecc.ads">
    <Version>7711</Version>
    - <Capabilities SchemaVersion="1.0">
    <Property Name="SSLState" Value="0" />
    </Capabilities>
    </MP>
    - <MP Name="LARADNAS3.US.ECC.ADS" FQDN="LARADNAS3.us.ecc.ads">
    <Version>7711</Version>
    - <Capabilities SchemaVersion="1.0">
    <Property Name="SSLState" Value="0" />
    </Capabilities>
    </MP>
    </MPList>

    The client show that it is reporting into our corporate MP:

    The client properties show it's in the correct AD site:

    ><p>The client properties showing it is in the correct AD site:</p><p><img alt=

    The client logs show all MPs being accessible even though it's outside it's AD site boundary:

    Begin checking Alternate Network Configuration LocationServices 8/29/2012 11:15:37 AM 640 (0x0280)
    Finished checking Alternate Network Configuration LocationServices 8/29/2012 11:15:37 AM 640 (0x0280)
    Updating portal information. LocationServices 8/29/2012 11:15:37 AM 3596 (0x0E0C)
    Attempting to retrieve lookup MP(s) from AD LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    The MP name retrieved is 'CORPAPSCCM.us.ecc.ads' with version '7711' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    MP 'CORPAPSCCM.us.ecc.ads' is compatible LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    The MP name retrieved is 'CORPNAS3.us.ecc.ads' with version '7711' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    MP 'CORPNAS3.us.ecc.ads' is compatible LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    The MP name retrieved is 'ATLMAGNAS2.us.ecc.ads' with version '7711' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    MP 'ATLMAGNAS2.us.ecc.ads' is compatible LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    The MP name retrieved is 'LARADNAS3.us.ecc.ads' with version '7711' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    MP 'LARADNAS3.us.ecc.ads' is compatible LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    The MP name retrieved is 'immagnas2.us.ecc.ads' with version '7711' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    MP 'immagnas2.us.ecc.ads' is compatible LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Current AD forest name is ecc.ads, domain name is us.ecc.ads LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Lookup Management Points from AD: LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'CORPAPSCCM.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'LARADNAS3.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'CORPNAS3.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'immagnas2.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'ATLMAGNAS2.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Retrieved lookup MP(s) from AD LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Default Management Points from AD: LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'CORPAPSCCM.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'LARADNAS3.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'CORPNAS3.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'immagnas2.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Name: 'ATLMAGNAS2.us.ecc.ads' HTTPS: 'N' ForestTrust: 'N' LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Persisting the default management points in WMI LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Current AD forest name is ecc.ads, domain name is us.ecc.ads LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Current AD site of machine is ATLMAG LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Current AD forest name is ecc.ads, domain name is us.ecc.ads LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Begin checking Alternate Network Configuration LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)
    Finished checking Alternate Network Configuration LocationServices 8/29/2012 11:28:59 AM 676 (0x02A4)

    I've changed the boundary to a slow network, but I haven't seen any change in the behavior. Is there a way to force an AD site to only use the MP that is local?


    • Edited by JoelIClark Thursday, August 30, 2012 2:56 PM HTML Change
    Thursday, August 30, 2012 2:39 PM

Answers

All replies

  • You cannot control which MP is picked. They are used randomly if there are multiple MPs per site. That's by design.

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

    Thursday, August 30, 2012 3:38 PM
  • Can I manually edit the MP list that's presented to the clients? How should this be configured to restrict that traffic to the local site?
    Thursday, August 30, 2012 3:49 PM
  • You use secondary sites.

    Multiple MPs in 2012 are for availability and cross-forest support only and are not location aware so there is no way. As Torsten said, this is by design.


    Jason | http://blog.configmgrftw.com


    Thursday, August 30, 2012 3:52 PM
  • Can you point me to the documentation that mentions it randomly picking a MP inside the site?
    Thursday, August 30, 2012 4:03 PM
  • http://technet.microsoft.com/en-us/library/gg712701.aspx#BKMK_Plan_Service_Location

    The documentation is kind of sketchy and of course doesn't explicitly say random. The statement that best describes it is this one "The order of all equivalent management points is not set".

    Torsten and my statement's are based on first hand conversations with the product group.


    Jason | http://blog.configmgrftw.com

    Thursday, August 30, 2012 8:39 PM
  • And what do we do when client pick up MP from a WRONG site?
    Wednesday, May 4, 2016 9:04 AM
  • That thread is almost 4 years old. Things have changed in the meantime. You can control MP selection be using boundary groups now.

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

    Wednesday, May 4, 2016 9:16 AM