Jerry - awesome - thanks! Data speeds up/down: Primary Site has a 12 M (8xT1) 2 Locations have a 3M (2 xT1) All other locations have a 3M (2xT1)
This should be good enough? Brian From: [email protected] To: [email protected] Subject: RE: [mssms] SCCM 2007 Secondary Site question Date: Mon, 13 May 2013 17:18:14 +0000 Brian, These do not need to be SCCM Site Servers. The DP role can reside on a remote system. There are also ways to use Branch Distribution Points on Windows 7 systems. If you have a small office or location with 5-10 clients, that could also be an option for you. Read up on the difference between standard and branch DPs. Correct, once the server is ready from an OS standpoint, you just need to deploy the DP role to them from the console. Nothing else “SCCM Related” needs to be on the target DP, just be sure to go through the PreReqs and make sure the systems are running a supported Operating Systems and meet the other DP role specifications. Make sure to account for disk space on the DP as well. The space required will all depend on how many packages you’ll be sending to them and how large they are. As far as clients go, if the link back to the primary is very slow, then you’ll want to consider a Secondary site so you can host a management point at those locations. Besides that, for a well-connected site, the clients could use the MP at the primary. Jerry Jerry Bradnan | Solution Architect | Blue Chip Consulting Group | e: [email protected] | m: 440.679.8204 | f: 440.348.2390 | http://www.bluechip-llc.com From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Monday, May 13, 2013 12:48 PM To: [email protected] Subject: RE: [mssms] SCCM 2007 Secondary Site question Jerry, Thanks! So, basically I need a Server OS at each location (like Windows Server 2008 R2) that is joined to the domain. For each of my locations, I would want to find a server that we would essentially use as a DP to distribute our client packages to our client PCs. This seems pretty simple and straight forward. So, once I determine/locate the server at these locations, I essentially use the 3rd link you've provided below and walk through the wizard to configure this. Does it matter that these servers I'll be using aren't an SCCM site server? Is there anything SCCM related that needs to be installed on the DP, such as the SCCM client? One last question, will my clients at these locations report back to my Primary site? Anything from a client configuration standpoint I should consider? Thanks, Brian From: [email protected] To: [email protected] Subject: RE: [mssms] SCCM 2007 Secondary Site question Date: Mon, 13 May 2013 16:26:35 +0000 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] To: [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 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
<<inline: image001.gif>>
<<inline: image002.gif>>
<<inline: image003.gif>>
<<inline: image004.gif>>
