Some folks have mentioned some limitations of PullDPs in a few older threads.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Bradnan, Jerry Sent: Wednesday, November 20, 2013 1:34 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: SCCM 2012R2 upgrade planning Ryan, For your multiple-forest situation; From TechNet: System Center 2012 Configuration Manager [R2] supports installing most site system roles in untrusted forests, there is no requirement to have a separate site for this scenario, unless you have exceeded the maximum number of supported clients for a site. Check out this planning information: http://technet.microsoft.com/en-us/library/dd8eb74e-3490-446e-b328-e67f3e85c779#Plan_Com_X-Forest For your Secondary Sites that you would like to manage bandwidth; you can manage rate limits and throttle the DPs as you would in SCCM 2007 secondary sites. That functionality has moved to the DP. However, you may want to investigate using Pull-DPs. With a Pull-DP you can throttle BITs with SCCM client policies and manage your bandwidth usage from that perspective. There are several options for managing traffic to the DPs. Typically, I recommend SQL on the site server for performance reasons, but either a remote or local instance is supported. Keep in mind secondary sites require SQL in SCCM 2012 and it cannot be remote. A secondary will install SQL express if there is no local instance of SQL available. Hope that helps, Jerry From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Ryan Shugart Sent: Wednesday, November 20, 2013 1:07 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] SCCM 2012R2 upgrade planning Hi: I’m working on planning out our upgrade from SCCM 2007 to SCCM 2012R2, and just wanted to run a few things by the list before putting things in stone. 1. Currently, we have three different SCCM 2007 hierarchies. This is because we have three different forests in our environment, with no trusts between them. Our main domain has about 2000 clients that will be managed, the other two between 20 and 50. My understanding is we will not be able to consolidate these because there is no trust between the forests, so we’ll have to stick with three hierarchies. Am I also correct in that we can’t set up a CAS and then have each of the three report into that? 2. For our environment with 2000 clients, we have secondary sites at each location, we currently have 1 primary and 17 secondary sites. I’m looking at changing these to distribution points instead of secondaries of their own. I know I can do compression to secondaries, but can I do bandwidth throttling? Specifically, can I tell the primary to send nothing to the various distribution points between certain times? If I can’t do that, then I have to go with secondary sites at each location. 3. Finally, I know this is a controversial topic on this list, but SQL on or off box. Right now its on box for the two smaller environments, and on our SQL cluster for the larget 2000 client environment. To be completely honest, this has worked well for me, and I’m leaning towards just sticking with that. I know many SCCM admins tend not to trust their DBAs, but hey, I’m friendly with the DBA here, he’s a nice guy and knows what he’s doing. So, what advantage do I have in moving SQL on box for the larger environment instead of keeping it on the SQL cluster? Thanks in advance for your thoughts. Ryan Ryan Shugart LAN Administrator MiTek USA, MiTek Denver 314-851-7414 © COPYRIGHT, MITEK HOLDINGS, INC., 2011-2013, ALL RIGHTS RESERVED ________________________________ This communication (including any attachments) contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it.
