Uh oh. You are probably thinking to yourself, here comes another one of those incredibly long blog posts about sizing. Thankfully, it’s not. If you want to fully understand the sizing process for Exchange 2016, you are certainly welcome to read the previous post that I did for Exchange 2013, as the overall process is effectively the same with one major caveat. Since we have eliminated the CAS role in Exchange 2016, you must follow the process for multi-role deployment sizing. Overall, the inputs to our sizing formulas stay the same from Exchange 2013 to Exchange 2016. This means that our IOPS requirements, memory requirements, and all of the other values provided in the Exchange 2013 sizing guidance should continue to be used for Exchange 2016. We are changing one set of inputs, however.
|Messages sent or received per mailbox per day||Mcycles per User, Active DB Copy or Standalone||Mcycles per User, Passive DB Copy|
Recommended Maximum Processor Core Count
Recommended Maximum Memory
Note: Version 9.1 and later of the Exchange Server Role Requirements Calculator aligns with this guidance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.