locked
Resident Management Point RRS feed

  • Question

  • Hi,

    I have a set of clients which are using the resident management point instead of the assigned management point. The resident MP is incorrect and the clients shouldn't be using it because they cannot get to it.

    Now I have read up about resident MP's and from what I understand clients use resident MP if they are in boundary group of another site, which defines that MP for the site.

    I have double checked all my boundaries and cannot find any overlapping boundary which is causing this problem. I have recreated the boundary which hosts these clients in SCCM 2012 and reinstalled the clients on the server but it still points to the resident MP.

    Any help will be much appreciated.

    Friday, November 15, 2013 11:50 AM

Answers

  • Yes that's fine I understand that. The problem is that the client is a MP from a different site altogether as its resident MP.

    Anyway after checking all my boundaries etc I couldn't find what was wrong. So I disabled AD Forest Discovery and deleted the AD sites boundaries. I think this has fixed my problem, I am going to test all clients shortly but so far so good.

    So it seems that the AD site was causing the issue. Should have listened in the first instance and used IP range to begin with.

    Thanks

    • Proposed as answer by Joyce L Monday, November 18, 2013 1:39 AM
    • Marked as answer by Joyce L Friday, December 6, 2013 9:19 AM
    Friday, November 15, 2013 12:29 PM

All replies

  • You cannot control which MP will be used if there are multiple ones per site.

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

    Friday, November 15, 2013 12:02 PM
  • Yes that's fine I understand that. The problem is that the client is a MP from a different site altogether as its resident MP.

    Anyway after checking all my boundaries etc I couldn't find what was wrong. So I disabled AD Forest Discovery and deleted the AD sites boundaries. I think this has fixed my problem, I am going to test all clients shortly but so far so good.

    So it seems that the AD site was causing the issue. Should have listened in the first instance and used IP range to begin with.

    Thanks

    • Proposed as answer by Joyce L Monday, November 18, 2013 1:39 AM
    • Marked as answer by Joyce L Friday, December 6, 2013 9:19 AM
    Friday, November 15, 2013 12:29 PM
  • Forest discovery is totally unrelated.
    Overlapping boundary/groups for site assignment might lead to that behavior.

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

    • Proposed as answer by Joyce L Monday, November 18, 2013 1:39 AM
    Friday, November 15, 2013 12:35 PM
  • MP's do not adhere to boundaries.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Friday, November 15, 2013 1:58 PM
  • Did you make any other changes? How has it panned out since?

    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    Tuesday, November 19, 2013 5:30 PM
  • I am facing the same issue? How it was solved?
    Tuesday, February 16, 2016 9:02 PM
  • What problem? You really should start a new thread and provide actual details.

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

    Tuesday, February 16, 2016 9:07 PM