First, there is no CM 2016. The next version of ConfigMgr have not been branded.
Next, A CAS and/or multiple primary sites have absolutely no part in availability or redundancy. Multiple primary sites are about scalability in terms of managed client count *only*. The statement “the secondary sites are just DPs”, makes no sense. Secondary sites must also be MPs. If they are just DPs, then they are not secondary sites. Finally, There are new HA options most likely coming in the next version of ConfigMgr so planning now is fairly useless because nothing specific have been announced. J From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Monday, October 5, 2015 11:47 AM 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]<mailto:[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
