locked
Deploying Client to a Secondary Site RRS feed

  • Question

  • I am in the process of deploying SCCM clients to PCs currently in our secondary site.  The first one I tested installed the client just fine, however, it had an issue finding the site code, it said it was invalid.  Once I manually opened the client, and selected to "Find Site", it successfully found the Primary site code.  I assume this is normal, from what I read the Secondary site codes no longer mean what the once did, is this correct?

    Now the question I have if the above assumption is correct, in the Client Push Properties for the secondary site, under Installation Properties, should the "SMSSITECODE" equal the Primary Site code or should it be the secondary site code? 

    Also for the boundary group for this site, I assume the assigned site should remain the Secondary site code?

    In case it matters, I am running SCCM 2012 R2.

    Monday, July 7, 2014 5:47 PM

Answers