locked
Site Code for SCCM Clients installed from Secondary Site Server RRS feed

  • Question

  • Hello,

    We have started the implementation of SCCM 2012 R2 at our network. We have setup a Primary site (JFO) server & pushed out the installation of SCCM clients to the local subnet. Things went fine.

    We have installed a Secondary site (ATC) at a remote network. We have tested client installation in the installation wizard we specify to install the client from the Secondary server. When SCCM client installed from the Secondary server, the site code that appears on the client in the control panel->Configuration Manager client settings is the site code of the primary site and not the secondary site.

    Is this behavior is normal

    Thursday, December 4, 2014 8:11 AM

Answers

  • Yes, that's normal behavior. A client can only be assigned to a primary site.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    • Proposed as answer by Daniel Engberg Thursday, December 4, 2014 8:14 AM
    • Marked as answer by Daniel JiSun Wednesday, December 17, 2014 10:45 AM
    Thursday, December 4, 2014 8:12 AM
  • Yes, when the client is installed the site code in the console will be the site code of the primary site and not of the secondary site that's in between.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Thursday, December 4, 2014 8:28 AM
  • Ultimately, secondary sites do *not* manage clients and so will never be assigned to the secondary site. However, do note that resources in the console that represent systems that do not have the client agent may show the site code of the secondary site if they fall within a boundary group associated with that secondary site. This is done so that client push can be initiated from the correct site. More gory details at http://blog.configmgrftw.com/secondary-sites-and-boundary-groups/

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

    Thursday, December 4, 2014 2:23 PM

All replies

  • Yes, that's normal behavior. A client can only be assigned to a primary site.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    • Proposed as answer by Daniel Engberg Thursday, December 4, 2014 8:14 AM
    • Marked as answer by Daniel JiSun Wednesday, December 17, 2014 10:45 AM
    Thursday, December 4, 2014 8:12 AM
  • So it is normal to see all the clients in the SCCM console have the same site code for the primary site, regardless of its location or the secondary SCCM server that manage those clients?

    Thursday, December 4, 2014 8:16 AM
  • Yes, when the client is installed the site code in the console will be the site code of the primary site and not of the secondary site that's in between.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Thursday, December 4, 2014 8:28 AM
  • Thank you.
    Thursday, December 4, 2014 8:30 AM
  • Ultimately, secondary sites do *not* manage clients and so will never be assigned to the secondary site. However, do note that resources in the console that represent systems that do not have the client agent may show the site code of the secondary site if they fall within a boundary group associated with that secondary site. This is done so that client push can be initiated from the correct site. More gory details at http://blog.configmgrftw.com/secondary-sites-and-boundary-groups/

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

    Thursday, December 4, 2014 2:23 PM