locked
Clients cannot detect secondary site - SCCM 2012 r2 SP1 RRS feed

  • Question

  • Hi,

    I face a problem when trying to install SCCM client agent to devices in the secondary site. All devices are assigned to the primary site, even those in the secondary one. When I manually force the assignment to the secondary site (using ccmclient.msi parameters) and then check the Configuration Manager in the control panel, I found that all clients have no site assigned to and no management point either, and when I search for a site ("site" tab in the configuration manager), the primary site is the only one founded.

    Please help me because I've been looking for answers but nothing worked.

    thanks in advance.

    Monday, February 8, 2016 3:59 PM

Answers

  • Clients cannot be assigned to a secondary site. Secondary sites are simply extensions of a primary site and thus do not actually manage clients. The clients must be assigned to the primary site. Clients will then use content location boundary groups to use the site roles within a secondary site: http://blog.configmgrftw.com/secondary-sites-and-boundary-groups/

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

    • Marked as answer by iladoukh Tuesday, February 9, 2016 3:26 PM
    Monday, February 8, 2016 4:49 PM

All replies

  • Clients cannot be assigned to a secondary site. Secondary sites are simply extensions of a primary site and thus do not actually manage clients. The clients must be assigned to the primary site. Clients will then use content location boundary groups to use the site roles within a secondary site: http://blog.configmgrftw.com/secondary-sites-and-boundary-groups/

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

    • Marked as answer by iladoukh Tuesday, February 9, 2016 3:26 PM
    Monday, February 8, 2016 4:49 PM
  • thank you for the quick response. so if I want to create device collections to separate devices in the primary site from the ones in the secondary site, I cannot use SMS_R_System.SMSAssignedSites="BKP" (BKP is the secondary site code) and SMS_R_System.SMSAssignedSites="PRI" (PRI is the primary site code) because all clients will be assigned to the primary site. Please correct me if I'm wrong.

    thank you

    Tuesday, February 9, 2016 10:54 AM
  • Correct. You will need to use some other criteria. I think you can use assigned MP but have never tried so don't know off-hand. You can certainly build collections based on IP address or AD OUs and sites though which should be equivalent.

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

    Tuesday, February 9, 2016 2:27 PM
  • Thank you very much! After I added the parameter SMSSITECODE=PRI to ccmclient properties for the secondary site (like the one for the primary site), all clients in the secondary site are now assigned to the primary site, with other informations like MP proxy, Resident MP. I succeeded to create devices collections for each site using "AD site" in the criteria and like you said, we can also use subnets of each site to separate their devices. the problem is now resolved.

    Thanks a lot.

    Tuesday, February 9, 2016 3:25 PM