Sami TCE 1 Reputation point

We use this command to install the agent on the clients of secondary site using Group Policy

CCMSetup.exe SMSSITECODE=PRI FSP=SCCM-Primary.local MP= SCCM-Primary.local
Primary Server : SCCM-Primary.local
Site Code : PRI

In this case, the clients are available (420 number) on the secondary site (Child Domain) to receive the contents of the CCM and CCMSetup folders (280 MB) to use the Primary server, this consumes 100% of the WANLINK bandwidth between the root domain and Child Domain
In this case, what command can be used to receive the contents of CCM and CCMSetup folders by the client from the secondary server in the child domain?

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,759 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Leon Laude 85,641 Reputation points

    Hi @Sami TCE ,

    You have posted in the System Center Service Manager forum, since your issue is related to SCCM / MECM I suggest you ask over at the dedicated SCCM / MECM forum over here:


    (If the reply was helpful please don't forget to upvote or accept as answer, thank you)

    Best regards,

    1 person found this answer helpful.
    0 comments No comments

  2. Fiona Yan-MSFT 2,311 Reputation points

    @Sami TCE

    It is recommended that we could use the command line like this"CCMSetup.exe SMSSITECODE=PRI FSP=SCCM-secondary.local MP= SCCM-secondary.local"
    Maybe we need to point the parameters to the secondary site and then add the command line in the following image:

    For more details,please refer to this artilcle:
    Note: This is non-official Microsoft article just for your reference.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  3. Jason Sandys 31,146 Reputation points Microsoft Employee

    Clients and ccmsetup automatically use configured boundaries and boundary groups to locate content. For ccmsetup, this includes all necessary prerequisite items so ultimately, there's nothing specific to do here if your boundaries and boundary groups are configured correctly.

    Two side notes though:

    1. using a startup script is generally preferred by most experienced admins as it enables many additional features and overcomes many of the shortcomings of group policy based software installation (if that worked well in the first place, many orgs wouldn't need ConfigMgr at all).
    2. The product is simply called Configuration Manager (ConfigMgr or MEMCM), it is no longer part of the System Center suite (it was moved to the new Microsoft Endpoint Manager suite about 12 months ago) and there has never been nor will there ever be a 2019 version. 2006 is the latest production version.
    0 comments No comments