The DP role would just require a file server configured to support a 2007 DP role.
This should give the prereqs your looking for: http://technet.microsoft.com/en-us/library/bb680335.aspx Here is a little more detail on the DP and Branch DP roles: http://technet.microsoft.com/en-us/library/bb932184.aspx Installing the DP role is pretty simple. It's just a matter of targeting a new system from the console and deploying that role out to the system. Here some information on how to set the Role up for a new system: http://technet.microsoft.com/en-us/library/bb681012.aspx Jerry From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Monday, May 13, 2013 12:09 PM To: [email protected] Subject: RE: [mssms] SCCM 2007 Secondary Site question Thanks for the note Trevor. Can you point me to do documentation on how to setup a remote DP in SCCM 2007? I know how to configure a DP, but I am looking for pre-reqs, step by step instructions. Does this mean I need to install a site server that would include the DP role? Again, I'm only using SCCM 2007 for a small number of packages I will be using for Software Distribution. So, what would happen if I attempted to install the SCCM client at these locations from my primary site? Obviously, this wouldn't work. But why? Brian ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] SCCM 2007 Secondary Site question Date: Mon, 13 May 2013 10:48:40 -0500 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 [WordPress Logo 32px]<http://trevorsullivan.net/> [Twitter Logo 32px] <http://twitter.com/pcgeek86> [Facebook Logo 32px] <http://facebook.com/trevor.sullivan> [Google+ Icon 32px] <https://plus.google.com/106658223083457664096> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Monday, May 13, 2013 10:40 AM To: [email protected]<mailto:[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
<<inline: image001.gif>>
<<inline: image002.gif>>
<<inline: image003.gif>>
<<inline: image004.gif>>
