locked
ccmsetup.exe /mp:server1,server2,server3 doesn't work RRS feed

  • Question

  • Hello,

    On my SCCM 2012 SP1, I wanted to list multiple MPs on /mp: switch to make them fallback (especially for the clients that can see only one of the MPs)

    On http://technet.microsoft.com/en-ca/library/gg699356.aspx 

    It says

    You can use the /mp command-line property to specify multiple management points so that if the computer fails to connect to the first one, the next is tried, and so on. When you specify multiple management points, separate the values by using commas.

    How can I make this work?

    Thanks,

    Young-


    YPae

    Wednesday, March 6, 2013 6:54 PM

Answers

  • no need to do that in CM12. Clients will automatically fall back to another MP if needed and the clients files are now downloaded from a distribution point not a Management Point.

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    Wednesday, March 6, 2013 7:44 PM
  • Please re-read the documentation. /mp is *not* in any way for specifying an MP.

    And as Kent says below, there's no need to do this anyway because the MP specified on the command using the SMSMP property is just for initial client activities and not any type of permanent MP assignment.

    Also, why do you have multiple MPs? MP selection by clients is not location aware.


    Jason | http://blog.configmgrftw.com

    Wednesday, March 6, 2013 10:46 PM
  • IMO, you're overthinking this way too much. If AD is extended, the download location will be found automatically as will the other properties.

    And once again, if your MPs are behind firewalls and not reachable by clients, you've deployed your MPs incorrectly in the first place. Using multiple MPs is in no way meant for segregated networks because clients never select MPs based on location or proximity or any other factor -- they randomly select *any* MP in the forest. Using multiple MPs in a primary site is for availability only.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by YPae Friday, March 29, 2013 5:37 PM
    Friday, March 29, 2013 3:29 PM

All replies

  • Should it be /MP:Server1 /MP:Server2 /MP:Server3 ?

    If it is the case, is technet wrong?


    YPae

    Wednesday, March 6, 2013 7:24 PM
  • no need to do that in CM12. Clients will automatically fall back to another MP if needed and the clients files are now downloaded from a distribution point not a Management Point.

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    Wednesday, March 6, 2013 7:44 PM
  • I have not a sccm 2012 enviroment available so i have not tested but i guess it should be ccmsetup.exe /mp:SMSMP01, SMSMP02, SMSMP03

    You are aware that this is only used to find the closes source files of the client. Not to specify which mp the client will be assigned to.?

    Wednesday, March 6, 2013 7:47 PM
  • Please re-read the documentation. /mp is *not* in any way for specifying an MP.

    And as Kent says below, there's no need to do this anyway because the MP specified on the command using the SMSMP property is just for initial client activities and not any type of permanent MP assignment.

    Also, why do you have multiple MPs? MP selection by clients is not location aware.


    Jason | http://blog.configmgrftw.com

    Wednesday, March 6, 2013 10:46 PM
  • Thanks for your answers, everyone.

    Facts:

    • /MP:Server1 /MP:Server2 /MP:Server3 is proper way of setting
      - Yes, this is only to find the best Source file location. (Not to specify "ultimate" MP)
    • /MP:Server1,Server2,Server3 doesn't work
      - CCMSETUP think that we have a server name "Server1,Server2,Server3"
    • If any one of the specific MP server is not responding, it looks like ccmsetup "gives up on download from DP action" altogether and always download the source from MP directly
    • As long as all AD Forests have been extended, System\System Management will provide the possible MP to provide list of DPs to pull the source files from.

    My intention was to:

    • Come up with good "universal" ccmsetup parameter for Client Push, Manual install for multiple forests
    • Make the command line to work for any situation (even on workgroup joined machines, for unknown forest, etc.) by specifying top 3 MPs in sequence, etc. to fallback, etc.
    • Have set of manual installation network sharepoint and multiple batch files:
      - SilentInstall.bat - Same as Client push
      - SilentInstall_Force.bat - with /ForceInstall + /MP:Server1 /MP:Server2 /MP:Server3
      - SilentInstall_fromShareA.bat - with /ForceInstall + /Source:\\NetworkShare\ for ForestA
      - SilentInstall_fromShareB.bat - with /ForceInstall + /Source:\\NetworkShare\ for ForestB
    • But because of the finding that if Server3 is not pingable (behind the firewall), specifying all 3 with /MP make things worse, we decided to have:
      - SilentInstall.bat - Same as Client push
      - SilentInstall_Force_ForestA.bat - with /ForceInstall + /MP:Server1 /MP:Server2
      - SilentInstall_Force_ForestB.bat - with /ForceInstall + /MP:Server3
      - SilentInstall_fromShareA.bat - with /ForceInstall + /Source:\\NetworkShare\ for ForestA
      - SilentInstall_fromShareB.bat - with /ForceInstall + /Source:\\NetworkShare\ for ForestB

    Thanks again,

    Young-


    YPae


    • Edited by YPae Friday, March 22, 2013 3:54 AM
    Friday, March 22, 2013 3:54 AM
  • IMO, you're overthinking this way too much. If AD is extended, the download location will be found automatically as will the other properties.

    And once again, if your MPs are behind firewalls and not reachable by clients, you've deployed your MPs incorrectly in the first place. Using multiple MPs is in no way meant for segregated networks because clients never select MPs based on location or proximity or any other factor -- they randomly select *any* MP in the forest. Using multiple MPs in a primary site is for availability only.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by YPae Friday, March 29, 2013 5:37 PM
    Friday, March 29, 2013 3:29 PM
  • Thanks Jason,

    Yes, I have been overthinking because we now have 2 standalone primary (no CAS), 2 AD forests (1 way trust) with bunch of firewall restrictions, etc. over DMZ (and I could not afford any situation that doesn't work after the project)

    I finally got the approval to allow the SCCM server to have the 2nd AD Forest Site Publishing capability so my major concern about possible MP discovery issue via AD is now resolved and I can scale back my overthinking as you affirmed as above.

    I am using Neil's Cross Forest Support Part 3 Model and ready to implement MP, DP and ACWP on the "gateway" server at DMZ:

    http://blogs.technet.com/b/neilp/archive/2012/08/24/cross-forest-support-in-configmgr-2012-part-3-deploying-site-server-site-systems-in-an-untrusted-forest.aspx

    Thanks again,


    YPae

    Friday, March 29, 2013 5:48 PM