Share This Post

Is a Secondary Site the Answer?

We’re working on a side-by-side upgrade to SCCM 2007 from SMS 2003. We have less than 10,000 clients and currently have a primary site in each of three geographical regions to serve as the Management Point for the regional clients. One of the challenges we are facing is that we are without a server to complete the side-by-side process in one region. So, we’re trying to figure out the best way to address this situation:

1. In-place upgrade the current SMS 2003 site server to SCCM 2007
2. Move the clients to another location temporarily, rebuild the current server and move them back
3. See if we can setup a Secondary Site in region and eliminate the need for a full primary site

Option three sounds very appealing to us, however it is the most "uncertain" of our options. We have always used Primary Sites and have never considered Secondary Sites in the past. I’ve been doing a lot of reading and have found the following benefits to implementing a Secondary Site with a Proxy Management Point:

1. One less SCCM license to purchase
2. Less administration than a Primary Site server
3. Transfers information as Site-To-Site traffic using custom bandwidth limitations and compression

On the downside, we need to figure out if the Secondary Site and Proxy management Point can be installed on another application server. Additionally, we’d have to figure out who we would want the parent to be. And from an aesthetic perspective, we would then have two Primary children and one Secondary child. Why not go Secondary site all the way?

The following articles helped me get a little better grasp of the subject matter. Hopefully I’ll have this one figured out sooner rather than later.

Determine If a Proxy Management Point is Needed at a Secondary Site
Proxy Management Point: Benefits and Otherwise

Share This Post

1 Comment

  1. How about using some SCCM extension products like Adaptiva Onesite or 1E Nomad?

Leave a Reply