Thanks folks. I was more curious about what the reasonable limit is for concurrent connections. In my neck of the woods we only have the 3 main DP’s and a few branch where slow links are and have never run into issues. That said, I usually BITS a week ahead of time if I can and network folks have never tried to lynch me.
From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Phil Wilcock Sent: May-04-16 5:27 PM To: ms...@lists.myitforum.com Subject: [mssms] RE: SCCM planning - DP's and clients per DP Just BranchCache it to spread the load – and/or plan for the new PeerCache that’s coming down the road (currently in TP) Then I would just have DPs depending on Geo or Network constraints From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Burke, John Sent: 04 May 2016 03:42 To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: [mssms] SCCM planning - DP's and clients per DP Hi Folks, We are talking about upgrading to the 15xx or 16xx. Some folks on the a planning session were talking about maximum concurrent connections from our clients to the dp’s for deploying software. We have a pretty quick network, and in my area we usually bits stuff down and have a few 1000 clients per DP. We have pushed some fairly large apps and scheduled them to go all at once but it’s been a while since we didn’t use the BITS option. The client count in the new environment will be 50000 ish. I’m wondering what folks think about say deploying a 500 MB package and running it from the DP’s – or how you folks figure out how many dp’s to deploy assuming you want to be able to deploy packages to large numbers of systems at once.
