The Exchange team is pleased to announce that the Exchange 2019 Sizing Calculator has completed development. We have heard the community since the release of Exchange Server 2019 and have spent the ...
Updated Jul 01, 2019
Version 4.0
Blog Post
Hi all,
I'm struggling with the decision to include the primary tool used to architect and validate an Exchange deployment inside the ISO for the CU for the product. I've read the comments by Nino, and, well they sound flimsy at best. I never found the calculator for previous Exchange versions being neglected. If it is going through the same bug checking etc as the CU as Nino states, how are broken calculations like what Tony Brock found making it out? Per the blog post, "...Moving this to the .ISO will allow us to update the calculator more readily and more frequently, as well as ensure it is aligned with any future investments in Exchange Server..." - you guys are smart guys. Not sure how you read that sentence and believed it before you published. Since when was it easier to create/update an ISO containing an Excel file (forget the rest of the code that has to go into the ISO), and then posting the ISO to a download site vs just posting an Excel file to a download site? Also, just because it's on the CD/ISO - doesn't mean it stays aligned with the product. Neglecting the tool would be a process problem (that I have never actually witnessed), and putting it on the CD/ISO isn't going to address that. Policy and process update does, which could also be included with the file on a download site.
I will say this - at least Nino didn't try and deny that pushing deployments to Office365 is part of the reason. His reply was to a comment about including the calc being a way to push folks to Office365. The first line of his response seems to accept that as a reality:
"