Clients only hit the SUP to check what patches they need. Then they pull the patches from the distribution points. However, given how spread out your company is geographically it may benefit from a SUP in each region.
Nick Gailfus Computer Technician p. 602.953.2933 f. 602.953.0831 [email protected] <[email protected]>| www.leonagroup.com On Wed, Jan 28, 2015 at 8:07 AM, Sean Pomeroy <[email protected]> wrote: > We are in the process of planning and testing patch deployment via SCCM. > > A high level overview of our infrastructure is as follows: > Primary in EMEA (MP, SUP, ACWP, DP, RSP, AISP) > Secondary in Americas (MP, SUP, DP) > Secondary in APAC (MP, SUP, DP) > > ~17,000 Clients (35% EMEA, 40% Americas, 20% APAC) > ~2,000 Servers (45% EMEA, 45% Americas, 10% APAC) > > At first we will only be patching clients. But servers will follow. > > Right now we are only testing patching on about ~500 PCs and all is going > smoothly. > > Once we move all clients to patching via SCCM, I am concerned our Primary > is going to be over loaded. > > I know MS documentation suggests SUP can handle 25,000 clients when it > co-exists with another role... But our Primary essentially has all roles. > > Should I push to stand up a separate server as a SUP in each region? > Or at least in place of the SUP on our primary? > > Thanks, > Sean > >
