I hadn't been on the list all day. This made my Monday :) Thanks Ryan! From: [email protected] To: [email protected] Subject: RE: [mssms] SCCM Redundancy Best Practices Date: Mon, 5 Oct 2015 17:55:38 +0000
X 150,000 J From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Monday, October 5, 2015 1:16 PM To: [email protected] Subject: RE: [mssms] SCCM Redundancy Best Practices +150,000 From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Sent: Monday, October 5, 2015 12:12 PM To: [email protected] Subject: Re: [mssms] SCCM Redundancy Best Practices On Mon, Oct 5, 2015 at 12:01 PM, Charles Hiland <[email protected]> wrote: The end result is redundancy in our primary server and SQL database. From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Monday, October 05, 2015 12:47 PM To: [email protected] Subject: Re: [mssms] SCCM Redundancy Best Practices Nooooooo! How many clients do you have? In CM16 you can have 200,000 clients. What do you expect to see from your new design? On 5 Oct 2015, at 17:41, Charles Hiland <[email protected]> wrote: We will be upgrading to SCCM 2016 next year, and I’m trying to figure out an ideal redundancy setup. At the moment we have one primary and 7 secondary sites (the secondary sites are just DPs). Does anyone have any ideas for best practice when it comes to redundancy? Currently we are thinking an off-site CAS with two primary servers. Do any common-place rules stand out that I am overlooking? Thanks in advance, Charlie
