Brian,
It depends on the size of the WAN links, as well as the type of content you're distributing to the remote sites. From a client policy and hardware/software inventory perspective, the Secondary Site is practically useless, except in extreme cases. Secondary Sites add the ability to control bandwidth consumption, but if your network pipes are large enough, this shouldn't be a problem. If the network pipe is larger than 20Mbit/sec, and the number of clients is less than 200, I would probably just put a Distribution Point there. In my opinion, it's best to reduce ConfigMgr infrastructure components as much as possible. Adding extra infrastructure unnecessarily is just adding more failure & monitoring points, but it depends on what you're working with. Cheers, Trevor Sullivan <http://trevorsullivan.net/> <http://twitter.com/pcgeek86> <http://facebook.com/trevor.sullivan> <https://plus.google.com/106658223083457664096> From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Monday, May 13, 2013 10:40 AM To: [email protected] Subject: [mssms] SCCM 2007 Secondary Site question Hi all, We have recently acquired a handful of new locations and have heard we might need to prepare another 5-6 additional locations in the very near future. These locations are, for the most part, located in different states than the Primary Site. Some have as few as 5-6 clients and as many as 35 clients. The features we will be leveraging at these locations are exclusively software distribution. Question is, should I install Secondary Sites for the new remote offices? What other factors/considerations should I thinking about? Thanks in advance! Brian
<<image001.gif>>
<<image002.gif>>
<<image003.gif>>
<<image004.gif>>
