Home
%3CLINGO-SUB%20id%3D%22lingo-sub-645891%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-645891%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20updated%20support%20for%20hypervisors.%20That%20will%20simplify%20the%20discussions%20when%20it%20comes%20to%20resources%20discussion.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-646618%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-646618%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20to%20hear%20there's%20an%20updated%20calculator.%20Including%20the%20Calculator%20in%20the%20ISO%3F%20You're%20kidding%20us...%20This%20means%20every%20time%20I%20want%20to%20download%20a%20copy%20I%20have%20to%20download%20the%20ISO.%20Which%20is%20not%20available%20as%20a%20normal%20download%20by%20the%20way!%20It%20seems%20you're%20trying%20to%20make%20it%20overly%20complicated%20for%20%22normal%22%20people%20to%20be%20able%20to%20download%20the%20stuff.%20As%20a%20consulting%20company%20I%20don't%20have%20a%20Enterprise%20Agreement.%20Yet%20I%20want%20to%20use%20the%20calculator%20for%20my%20projects...%20Come%20on%20Exchange%20Team!%20You%20can%20do%20better...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-652219%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-652219%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Christian%2C%20MSDN%20has%20the%20Exchange%202019%20bits%20too.%20The%20calculator%20will%20only%20be%20updated%20once%20per%20CU%2C%20so%20you%20don't%20need%20to%20download%20it%20any%20more%20often%20than%20you%20would%20the%20bits.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-653000%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-653000%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3Bfor%20updating%20the%20Exchange%20Calculator%2C%20we%20are%20looking%20forward%20to%20Exchange%20Server%202019.%20Just%20had%20a%20question%20regarding%20the%20maximum%20database%20limit%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EThe%20recommended%20maximum%20limit%20of%202TB%20for%20JBOD%20deployments%2C%20and%20200GB%20for%20RAID%20deployments%20will%20be%20enforced%20by%20default%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EWanted%20to%20see%20why%20the%20RAID%20deployments%20are%20limited%20by%20default%20to%20a%20200GB%20database%20maximum%20size%3F%20Would%20it%20be%20possible%20to%20get%20the%20technical%20reason%20behind%20setting%20that%20limit%3F%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-653306%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-653306%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88801%22%20target%3D%22_blank%22%3E%40Michael%20Hincapie%3C%2FA%3E%2C%20the%20200GB%20limit%20is%20not%20new.%26nbsp%3B%20It's%20been%20in%20place%20for%20quite%20some%20time%20when%20our%20preferred%20JBOD%20based%20solutions%20are%20not%20used.%26nbsp%3B%20You%20still%20have%20the%20ability%20to%20override%20default%20database%20size%20if%20you%20desire.%26nbsp%3B%20Obviously%2C%20it's%20not%20our%20recommendation%20however.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-672801%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-672801%22%20slang%3D%22en-US%22%3E%3CP%3EI%20totally%20agree%20with%20comments%20from%20Christian%20Schindler%2C%20why%20in%20earth%20is%20it%20only%20available%20with%20the%20ISO!%20Come%20on%26nbsp%3BMicrosoft!!!!%3C%2FP%3E%3CDIV%20class%3D%22lia-message-author-rank%20lia-component-author-rank%20lia-component-message-view-widget-author-rank%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-676298%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-676298%22%20slang%3D%22en-US%22%3E%3CP%3EAgreed%20on%20the%20availability%20model.%26nbsp%3B%20You%20need%20to%20buy%20Exchange%20(or%20an%20MSDN%20subscription%20first%20because%20it's%20not%20available%20like%20previous%20versions%20of%20Exchange)%20to%20get%20the%20document%20to%20plan%20its%20deployment%20on%20physical%20servers%20that%20you%20need%20to%20order%20before%20you'd%20want%20to%20install%20the%20software%20you%20need%20to%20buy....%20or%20that%20you%20could%20use%20the%20same%20document%20to%20make%20the%20cost%20justification%20to%20spin%20up%20an%20Office365%20tenant%20and%20move%20to%20that.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20previous%20distribution%20model%20seemed%20to%20work%20pretty%20well%20on%20the%20Technet%20Gallery%2C%20not%20sure%20how%20an%20Excel%20file%20logically%20fits%20well%20on%20a%20product%20ISO%3F%26nbsp%3B%20Seems%20silly%20to%20download%20%26gt%3B1GB%20ISO%20for%20a%20%26lt%3B2MB%20Excel%20spreadsheet%2C%20don'tchya%20think%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-695255%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-695255%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EHow%20calculator%20calculates%20memory%20configuration%20for%20exchange%202019%20server%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIts%20already%20stated%20as%20128%20GB%20for%20MBX%20role....%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20your%20calc%20will%20add%20more%20memory%20on%20top%20of%20base%20128%20GB%20memory%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOR%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20calc%20will%20bring%20down%20actual%20memory%20requirements%20for%20exchange%202019%20%3F%3F%3F%3F%3F%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20how%20its%20look%20like%2C%20you%20are%20insisting%20every%20one%20to%20go%20with%20O365%2C%20but%20smart%20customers%20have%20forced%20you%20to%20publish%20calculator%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-697000%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-697000%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F74090%22%20target%3D%22_blank%22%3E%40Mahesh%20PM%3C%2FA%3E%2C%20the%20memory%20calculation%20was%20updated%20for%20Exchange%20Server%202019%20to%20factor%20in%20CPU%20cores.%26nbsp%3B%20The%20memory%20calculation%20starts%20with%20a%20minimum%20value%20for%20Store%20memory%20and%20JET%20cache%20based%20upon%20%23%20of%20users%20and%20%23%20of%20databases.%26nbsp%3B%20Then%20it%20makes%20certain%20that%20there%20is%204GB%2FCore%20allocated.%26nbsp%3B%20If%20the%20user%20and%20database%20counts%20are%20low%2C%20but%20the%20core%20count%20is%20high%2C%20the%20memory%20requirement%20will%20be%20larger%20in%20Exchange%20Server%202019%20to%20support%20the%20memory%20requirements%20of%20the%20core%20density.%26nbsp%3B%20Our%20experience%20has%20shown%20that%20as%20core%20density%20increases%2C%20available%20memory%20must%20increase%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-712496%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-712496%22%20slang%3D%22en-US%22%3E%3CP%3EI%20want%20calculator.%20but%20I%20can't%20find%20Download%20link.%3C%2FP%3E%3CP%3Esomebody%20help%20me%20please!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-727101%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727101%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20available%20in%20the%20Exchange%20Server%202019%20Cumulative%20Update%202%20(CU2)%20package.%20Microsoft%20is%20not%20releasing%20the%20Calculator%20as%20a%20standalone%20package%20anymore.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-727126%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727126%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20someone%20PLEASE%20help%20me%20understand%20what%20I'm%20doing%20wrong%20here%3F%20I%20can't%20have%20more%20than%208%20Servers%20per%20DAG%2C%20even%20though%20the%20tools%20says%20%22between%201%20and%2016%22%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20the%20number%20of%20Servers%20remains%20at%208%2C%20regardless%20of%20how%20many%20mailboxes%20I%20input.%20Is%20there%20an%20auto-increment%20trigger%20that%20I%20have%20missed%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20991px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F121553iDD492B544D0170DE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Exchange-Calculator-2019_Error.png%22%20title%3D%22Exchange-Calculator-2019_Error.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737514%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737514%22%20slang%3D%22en-US%22%3E%22Moving%20this%20to%20the%20.ISO%20will%20allow%20us%20to%20update%20the%20calculator%20more%20readily%20and%20more%20frequently%22%20Exactly%2C%20creating%20an%20excel%20document%2C%20adding%20it%20to%20an%20iso%20image%2C%20then%20uploading%20that%20to%20the%20internet%20is%20much%20faster%20than%20just%20uploading%20the%20excel%20document.%20When%20I%20tell%20people%20that%2C%20they%20look%20at%20me%20like%20I'm%20crazy...%20%2Fs%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-738723%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-738723%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3Ei%20can%20find%20only%20Exchange%20Server%20Role%20Requirements%20Calculator%20v9.1%2C%20for%20exchange%202013%2F2016.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgallery.technet.microsoft.com%2FExchange-2013-Server-Role-f8a61780%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgallery.technet.microsoft.com%2FExchange-2013-Server-Role-f8a61780%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewere%20can%20i%20find%20calculator%20for%202019%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ERaviv%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-740058%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-740058%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F371277%22%20target%3D%22_blank%22%3E%40RavivY%3C%2FA%3E%26nbsp%3B%20-%20it's%20on%20the%202019%20ISO%2C%20as%20stated%20in%20the%20Summary%20section%20above.%20It's%20now%20owned%20by%20the%20core%20engineering%20team%2C%20so%20it%20ships%20as%20part%20of%20the%20final%20product.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-653344%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-653344%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20requirements%20for%20a%20Hybrid%20Management%20Server%20when%20all%20mailboxes%20are%20in%20Exchange%20Online%20would%20also%20be%20helpful.%20The%20recommended%20128GB%20is%20a%20little..%20well%20how%20do%20I%20put%20this...%20extreme!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-799520%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-799520%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20the%20sizing%20calculator%20make%20allowance%20for%20those%20organisations%20who%20wish%20to%20work%20in%20on-line%20mode%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-809044%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-809044%22%20slang%3D%22en-US%22%3E%3CP%3EI%20posted%20a%20question%20about%20this%20new%20Calculator%20almost%20two%20months%20ago.%20No%20response%20to-date.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20Support%20just%20informed%20me%20that%20I%20need%20to%20pay%20up%20in%20order%20for%20them%20to%20be%20able%20to%20field%20questions%20related%20to%20the%20Calculator.%20Interesting....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet%20me%20ask%20the%20question%20here%20again...%20has%20the%20maximum%20number%20of%20Mailbox%20Server%20in%20a%20DAG%20changed%3F%3C%2FP%3E%3CP%3EIf%20no%2C%20why%20does%20the%20calculator%20show%20a%20maximum%20of%208%3F%3C%2FP%3E%3CP%3EWhy%20is%20it%20raising%20an%20error%20when%20I%20input%20something%20above%208%3F%3C%2FP%3E%3CP%3EAnd%20why%20does%20the%20error%20say%20%22between%201%20and%2016%22%20when%20it%20is%20actually%20enforcing%20a%20%22between%201%20and%208%22%20rule%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20could%20I%20be%20doing%20wrong%3F%20Please%20help.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20780px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F127302i77D95FAC14F06A37%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22E2K19-Calculator-Bug-02.jpg%22%20title%3D%22E2K19-Calculator-Bug-02.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20480px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F127301i8905084F70F6185B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22E2K19-Calculator-Bug-01.jpg%22%20title%3D%22E2K19-Calculator-Bug-01.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-809189%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-809189%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%22Moving%20this%20to%20the%20.ISO%20will%20allow%20us%20to%20update%20the%20calculator%20more%20readily%20and%20more%20frequently%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESeriously%2C%20SOMEONE%20at%20Microsoft%20NEEDS%20to%20rethink%20the%20sanity%20of%20this%20decision.%20Downloading%206.1GB%20of%20iso%20just%20to%20obtain%20a%20760KB%20file%20is%20illogical%20and%20doesn't%20factor%20in%20the%20fact%20that%20a%20majority%20of%20humans%20still%20live%20in%20parts%20of%20the%20world%20where%20data%20is%20neither%20%22free%22%20nor%20abundant.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EPlease%20make%20this%20%22Calculator%22%20available%20in%20some%20other%20fashion%20-%20before%20you%20turn%20your%20customers%20into%20unwitting%20Victims%20of%20internet%20%22Do-Gooders%22%20who%20will%20be%20very%20glad%20to%20supply%20them%20a%20more%20logical%20and%20easier%20access%20to%20trojanized%20copies.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-811419%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-811419%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112819%22%20target%3D%22_blank%22%3E%40Deji%20Akomolafe%3C%2FA%3E%26nbsp%3B%20-%26nbsp%3BThe%20maximum%20has%20not%20changed%2C%20it%20is%20still%2016.%26nbsp%3B%20If%20it%20is%20only%20allowing%208%20it's%20because%20you%20have%20chosen%20site%20resilient%20deployment.%26nbsp%3B%20If%20you%20turn%20off%20site%20resilience%20the%20maximum%20node%20count%20is%2016.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-811553%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-811553%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E-%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-871880%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871880%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EGot%20the%20ISO%26nbsp%3B%26nbsp%3Bon%20VLSC%2C%20but%20can't%20find%20the%20calculator%20in%20it.%3C%2FP%3E%3CP%3ECould%20you%20give%20me%20the%20filename%20or%20the%20path%20where%20we%20can%20find%20it%3F%3C%2FP%3E%3CP%3Etried%20with%202019%20and%202016...%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20help%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EISO%20filename%3A%3C%2FP%3E%3CP%3ESW_DVD9_Exchange_Svr_2019_CU_3_MultiLang_Std_Ent_.iso_MLF_X22-18612.ISO%3C%2FP%3E%3CP%3Eand%26nbsp%3B%3C%2FP%3E%3CP%3ESW_DVD9_Exchange_Svr_2016_CU_14_MultiLang_Std_Ent_.iso_MLF_X22-18627.ISO%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-888317%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-888317%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20per%20the%20previous%20question%20which%20doesn't%20appear%20to%20have%20been%20answered%2C%20where%20do%20I%20find%20the%20calculator%20on%20the%20Ex2019%20ISO%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20...%20it%20really%20shouldn't%20be%20this%20hard!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-888519%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-888519%22%20slang%3D%22en-US%22%3E%3CP%3EFound%20it%20in%20the%20%5CSupport%20folder%20of%20the%20CU2%20or%20higher%20ISO.%20The%20file%20is%20named%26nbsp%3BCalculator%2010-0.xlsm.%20Hope%20this%20helps%20others%20looking%20for%20the%20calculator.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-925031%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-925031%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20a%20potential%20customer%20has%20to%20pay%20the%20big%20bucks--FIRST.%26nbsp%3B%20Only%20then%20can%20they%20get%20the%20calculator%20to%20size%20the%20project.%26nbsp%3B%20Only%20then%20can%20they%20get%20server%20hardware%20quotes.%26nbsp%3B%20Only%20then%20can%20they%20have%20all%20of%20the%20answers%20to%20build%20a%20project%20budget%20with%20the%20TCO.%26nbsp%3B%20And%20FINALLY%20they%20realize%20they%20cannot%20get%20it%20approved--but%20have%20ALREADY%20spent%20half%20of%20it%20(for%20the%20software)%3F%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWho%20the%20heck%20will%20win%20a%20consulting%20engagement%20like%20that%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20no%20one%20in%20the%20current%20Exchange%20team%20ever%20had%20to%20build%20a%20business%20case%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPLEASE%20make%20ALL%20sales%20and%20planning%20docs%20EASILY%2C%20QUICKLY%2C%20%26amp%3B%20PUBLICLY%20available--for%20FREE!%26nbsp%3B%20THAT%20then%20engenders%20customers'%20trust!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-925078%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-925078%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F430493%22%20target%3D%22_blank%22%3E%40LydaRA_SP%3C%2FA%3E%26nbsp%3B-%20the%20calc%20is%20available%20on%20MSDN%2C%20you%20don't%20need%20to%20buy%20Exchange%20licences%20to%20get%20to%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-958160%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-958160%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20we%20give%2050%20GB%20mailbox%20size%20then%20we%20get%20the%20following%20error.%20How%20come%2050%20GB%20size%20mailbox%20changes%20number%20of%20users%20requirements%3F%3C%2FP%3E%3CP%3EI%20think%20it%20is%20a%20bug%2C%20could%20you%20tell%20me%20what%20am%20I%20doing%20wrong%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F151464i19886BC5B9251F6C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22E2019%20Calc%20Error.png%22%20title%3D%22E2019%20Calc%20Error.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-958164%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-958164%22%20slang%3D%22en-US%22%3EAnother%20concern%2C%20why%20was%20it%20decided%20to%20add%20the%20calculator%20only%20in%20the%20ISO%2C%20I%20would%20think%20of%20getting%20in%20the%20ISO%20and%20direct%20public%20download%20would%20be%20ease%20of%20use.%20To%20get%20a%20file%20of%20763%20KB%2C%20we%20have%20to%20download%20ISO%20of%20over%205%20GB.%20Think%20of%20a%20consultant%2C%20who%20is%20travelling%20with%201%20GB%20data%20limit%20per%20day%2C%20Then%20their%20is%20no%20way%20to%20get%20the%20calculator.%20It%20does%20not%20sounds%20right.%20Please%20see%20if%20you%20can%20ease%20the%20download.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-983184%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-983184%22%20slang%3D%22en-US%22%3EThe%20New%20Exchange%20Server%20Role%20Requirements%20Calculator%20seems%20have%20got%20Gotchas.%20When%20I%20try%20and%20size%20for%20200K%20Mail%20boxed%20it%20seems%20to%20provide%20Weird%20Results.%20Can%20some%20one%20help%20me%20here.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-983188%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-983188%22%20slang%3D%22en-US%22%3EThe%20New%20Exchange%20Server%20Role%20Requirements%20Calculator%20seems%20have%20got%20Gotchas.%20When%20I%20try%20and%20size%20for%20200K%20Mail%20boxed%20it%20seems%20to%20provide%20Weird%20Results.%20Can%20some%20one%20help%20me%20here.%20CPU%20Utilization%3A%2016000%25%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1000498%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1000498%22%20slang%3D%22en-US%22%3E%3CP%3Eaayaz%20-%20I%20hope%20you%20calculated%20Specint2017%20and%20not%20Specint2006.%3C%2FP%3E%3CP%3EIf%20you%20wish%20you%20can%20send%20your%20calculation%20to%20my%20pn%40GoldenFive.net%20and%20I%20will%20see%20what%20is%20going%20on.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1033248%22%20slang%3D%22en-US%22%3ERe%3A%20Announcing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1033248%22%20slang%3D%22en-US%22%3E%3CP%3Eexchange%202019%20with%20400%20mailboxes%20and%201TB%20DB%20how%20many%20GB%20for%20RAM%20required%20and%20Cores%20of%20CPU%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644180%22%20slang%3D%22en-US%22%3EAnnouncing%20The%20Exchange%20Server%202019%20Sizing%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644180%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Exchange%20team%20is%20pleased%20to%20announce%20that%20the%20Exchange%202019%20Sizing%20Calculator%20has%20completed%20development.%26nbsp%3B%20We%20have%20heard%20the%20community%20since%20the%20release%20of%20Exchange%20Server%202019%20and%20have%20spent%20the%20past%20few%20months%20making%20usability%20improvements%20to%20the%20calculator%2C%20adding%20specific%20investments%20for%20Exchange%20Server%202019%20and%20validating%20the%20guidance%20output%20by%20the%20calculator.%26nbsp%3B%20You%E2%80%99ll%20notice%20new%20things%20have%20been%20added%20and%20some%20items%20that%20no%20longer%20made%20sense%20have%20been%20removed.%26nbsp%3B%20Read%20on%20to%20find%20out%20more%20details%20on%20what%20has%20changed.%3C%2FP%3EOptimized%20for%20Exchange%20Server%202019%3CP%3EThe%20first%20thing%20you%E2%80%99ll%20likely%20notice%20is%20that%20the%20new%20version%20of%20the%20calculator%20only%20supports%20Exchange%20Server%202019.%26nbsp%3B%20Removing%20support%20for%20previous%20releases%20allowed%20us%20to%20streamline%20the%20calculator%20and%20target%20today%E2%80%99s%20usage%20patterns%20vs.%20something%20that%20made%20sense%2012%20years%20ago.%26nbsp%3B%20Does%20anyone%20even%20remember%20deploying%20CCR%2C%20LCR%20and%20SCR%3F%26nbsp%3B%20You%20should%20notice%20that%20the%20input%20experience%20is%20significantly%20faster.%26nbsp%3B%20It%20also%20is%20designed%20to%20preferentially%20provide%20feedback%20on%20the%20input%20sheet%20without%20having%20to%20navigate%20to%20other%20sheets%20to%20find%20out%20that%20there%20is%20a%20problem%20or%20warning%20as%20a%20result%20of%20the%20specified%20settings.%3C%2FP%3EImproved%20Support%20for%20Virtualization%3CP%3EAnother%20area%20that%20received%20a%20lot%20of%20attention%20was%20providing%20better%20guidance%20when%20using%20virtualization%20technologies.%26nbsp%3B%20In%20particular%2C%20you%20will%20see%20new%20disk%20types%20optimized%20for%20deployments%20with%20Azure%20if%20you%20specify%20a%20virtualized%20deployment.%26nbsp%3B%20Choosing%20one%20of%20these%20disk%20types%20will%20relax%20rules%20for%20the%20calculator%20allowing%20a%20JBOD%20configuration%20to%20be%20recommended%20more%20frequently.%26nbsp%3B%20Using%20a%20JBOD%20configuration%20allows%20Exchange%20DAGs%20to%20be%20deployed%20more%20cost%20effectively%20with%20Azure.%26nbsp%3B%20This%20doesn%E2%80%99t%20change%20our%20recommendation%20that%20Exchange%20Native%20Data%20Protection%20offered%20by%20DAGs%20be%20used%20in%20all%20deployments.%26nbsp%3B%20DAGs%20are%20still%20the%20cornerstone%20of%20the%20Exchange%20HA%2FDR%20story.%3C%2FP%3E%3CP%3EYou%E2%80%99ll%20also%20notice%20that%20calculation%20of%20CPU%20requirements%20is%20improved%20for%20virtualized%20deployments.%26nbsp%3B%20If%20a%20virtualized%20option%20is%20chosen%2C%20you%20will%20see%20two%20CPU%20core%20values%20appear.%26nbsp%3B%20The%20first%20is%20to%20specify%20the%20number%20of%20cores%20deployed%20in%20the%20virtualization%20host%20and%20the%20second%20specifies%20the%20number%20of%20cores%20available%20to%20the%20guest%20virtual%20machine%20via%20the%20hypervisor.%26nbsp%3B%20You%E2%80%99ll%20also%20notice%20that%20we%20have%20added%20the%20option%20to%20specify%20Physical%20CPU%3AGuest%20CPU%20subscription%20ratio%20used%20in%20system%20design.%26nbsp%3B%20The%20calculator%20will%20use%20all%20of%20these%20inputs%20to%20determine%20what%20resources%20are%20actually%20available.%26nbsp%3B%20No%20more%20fumbling%20with%20these%20calculations%20on%20your%20own.%3C%2FP%3EUpdated%20SPECint%20Benchmark%3CP%3ESpeaking%20of%20CPU%E2%80%99s%2C%20we%20also%20thought%20it%20was%20time%20to%20move%20to%20a%20modern%20benchmark.%26nbsp%3B%20The%20Exchange%202019%20Calculator%20uses%20SPECint%202017%20criteria.%26nbsp%3B%20Don%E2%80%99t%20ask%20us%20to%20translate%20old%20CPU%20ratings%20to%20new%20ones%2C%20even%20SPECint%20states%20the%20standards%20should%20be%20considered%20separate%20and%20distinct%20with%20no%20direct%20conversion.%26nbsp%3B%20End%20of%20story.%3C%2FP%3EMetaCache%20(MCDB)%20Database%20Support%3CP%3EOnce%20upon%20a%20time%20we%20considered%20simply%20rev%E2%80%99ing%20the%20existing%20calculator%20to%20add%20a%20single%20input%20option%20and%20basic%20calculations%20to%20account%20for%20the%20new%20MCDB%20feature.%26nbsp%3B%20However%2C%20what%20could%20have%20been%20delivered%20in%20a%20matter%20of%20minutes%20to%20under%20an%20hour%2C%20we%20(a%20nameless%20individual)%20decided%20a%20more%20exhaustive%20refresh%20of%20the%20calculator%20was%20warranted.%26nbsp%3B%20Queue%20a%20lengthy%20delay%20and%20numerous%20emails%20asking%2C%20%E2%80%9CWhen%20will%20the%202019%20Calculator%20be%20available%2C%20Brent%3F%E2%80%9D%26nbsp%3B%20MCDB%20support%20was%20in%20fact%20the%20first%20thing%20that%20was%20added%20but%20as%20you%20can%20tell%20from%20this%20post%2C%20other%20work%20followed.%26nbsp%3B%20The%20MCDB%20calculations%20are%20based%20upon%20the%20same%20guidance%20we%E2%80%99ve%20provided%20to%20date%2C%20but%20now%20most%20of%20the%20math%20is%20done%20for%20you.%26nbsp%3B%20Given%20the%20variability%20of%20SSD%20capacities%2C%20the%20calculator%20will%20give%20you%20a%20required%20device%20count%20and%20capacity%20to%20be%20provisioned.%26nbsp%3B%20What%20you%20procure%20will%20vary%20based%20upon%20the%20values%20provided%20and%20what%E2%80%99s%20practically%20available%20on%20the%20market.%26nbsp%3B%20Device%20count%20should%20be%20the%20overriding%20determination%20in%20how%20many%20devices%20to%20use.%3C%2FP%3E2TB%20Database%20Limit%3CP%3EThe%20Exchange%20Team%20has%20always%20recommended%20that%20customers%20limit%20database%20size%20to%202TB.%26nbsp%3B%20Previous%20versions%20of%20the%20calculator%20would%20frequently%20treat%20this%20as%20a%20%E2%80%9Csuggestion%E2%80%9D%20and%20happily%20specify%20larger%20databases%20complete%20with%20a%20warning%20to%20not%20exceed%202TB.%26nbsp%3B%20That%20has%20changed%20in%20this%20updated%20version%20of%20the%20calculator.%26nbsp%3B%20The%20recommended%20maximum%20limit%20of%202TB%20for%20JBOD%20deployments%2C%20and%20200GB%20for%20RAID%20deployments%20will%20be%20enforced%20by%20default.%26nbsp%3B%20Depending%20upon%20your%20configuration%2C%20you%20may%20see%20a%20small%20increase%20in%20the%20number%20of%20DB%E2%80%99s%20specified%20by%20the%20calculator.%26nbsp%3B%20We%20have%20worked%20to%20make%20certain%20that%20disks%20are%20still%20utilized%20to%20the%20greatest%20extent%20possible.%26nbsp%3B%20Should%20you%20choose%20to%20ignore%20the%20best%20advice%20of%20the%20Exchange%20Team%2C%20the%20calculator%20will%20allow%20you%20to%20override%20the%20maximum%20database%20size%2C%20both%20larger%20or%20smaller%20than%20what%20we%20have%20chosen%20by%20default.%3C%2FP%3E%3CP%3EYou%20will%20notice%20that%20this%20change%20causes%20designs%20to%20be%20capacity%20bound%20more%20frequently%20than%20IO%20bound%2C%20especially%20with%20large%20mailboxes.%26nbsp%3B%20A%20trend%20that%20was%20already%20observed%20in%20previous%20versions.%26nbsp%3B%20Given%20the%20multi-year%20journey%20to%20reduce%20IO%2C%20investments%20to%20scale%20out%20O365%20and%20now%20the%20inclusion%20of%20MCDB%2C%20it%20shouldn%E2%80%99t%20be%20a%20surprise%20that%20the%20days%20of%20the%20typical%20on-premises%20server%20being%20IO%20bound%20are%20in%20the%20rear-view%20mirror.%26nbsp%3B%20We%20think%20that%E2%80%99s%20cool%2C%20don%E2%80%99t%20you%3F%3C%2FP%3ESummary%3CP%3EWe%20are%20excited%20to%20release%20this%20version%20of%20the%20Exchange%20Sizing%20Calculator%20and%20hope%20you%20find%20the%20changes%20we%20have%20made%20valuable.%26nbsp%3BFor%20the%20best%20experience%20we%20recommend%20you%20use%20Microsoft%20Office%20Professional%20Plus%202019%20or%20Microsoft%20Office%20365%20ProPlus.%20And%20now%20that%20you%20are%20excited%20as%20well%2C%20and%20even%20if%20you%20aren%E2%80%99t%2C%20you%E2%80%99re%20probably%20saying%20give%20me%20the%20download%20link%20already.%26nbsp%3B%20Well%20that%E2%80%99s%20the%20last%20change%20we%20are%20announcing.%26nbsp%3B%20The%20Exchange%202019%20Calculator%20will%20be%20included%20in%20the%20DVD%20.ISO.%26nbsp%3B%20So%20yes%2C%20you%20must%20wait%20just%20a%20few%20more%20days%20for%20the%20release%20of%20Cumulative%20Update%202%20before%20you%20can%20take%20it%20for%20a%20test%20drive.%26nbsp%3B%20Moving%20this%20to%20the%20.ISO%20will%20allow%20us%20to%20update%20the%20calculator%20more%20readily%20and%20more%20frequently%2C%20as%20well%20as%20ensure%20it%20is%20aligned%20with%20any%20future%20investments%20in%20Exchange%20Server.%3C%2FP%3E%3CP%3EThe%20Exchange%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-644180%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Exchange%20team%20is%20pleased%20to%20announce%20that%20the%20Exchange%202019%20Sizing%20Calculator%20has%20completed%20development.%20Read%20all%20about%20the%20new%20features%20here.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-644180%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premises%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPlanning%20and%20Architecture%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETools%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

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 past few months making usability improvements to the calculator, adding specific investments for Exchange Server 2019 and validating the guidance output by the calculator.  You’ll notice new things have been added and some items that no longer made sense have been removed.  Read on to find out more details on what has changed.

Optimized for Exchange Server 2019

The first thing you’ll likely notice is that the new version of the calculator only supports Exchange Server 2019.  Removing support for previous releases allowed us to streamline the calculator and target today’s usage patterns vs. something that made sense 12 years ago.  Does anyone even remember deploying CCR, LCR and SCR?  You should notice that the input experience is significantly faster.  It also is designed to preferentially provide feedback on the input sheet without having to navigate to other sheets to find out that there is a problem or warning as a result of the specified settings.

Improved Support for Virtualization

Another area that received a lot of attention was providing better guidance when using virtualization technologies.  In particular, you will see new disk types optimized for deployments with Azure if you specify a virtualized deployment.  Choosing one of these disk types will relax rules for the calculator allowing a JBOD configuration to be recommended more frequently.  Using a JBOD configuration allows Exchange DAGs to be deployed more cost effectively with Azure.  This doesn’t change our recommendation that Exchange Native Data Protection offered by DAGs be used in all deployments.  DAGs are still the cornerstone of the Exchange HA/DR story.

You’ll also notice that calculation of CPU requirements is improved for virtualized deployments.  If a virtualized option is chosen, you will see two CPU core values appear.  The first is to specify the number of cores deployed in the virtualization host and the second specifies the number of cores available to the guest virtual machine via the hypervisor.  You’ll also notice that we have added the option to specify Physical CPU:Guest CPU subscription ratio used in system design.  The calculator will use all of these inputs to determine what resources are actually available.  No more fumbling with these calculations on your own.

Updated SPECint Benchmark

Speaking of CPU’s, we also thought it was time to move to a modern benchmark.  The Exchange 2019 Calculator uses SPECint 2017 criteria.  Don’t ask us to translate old CPU ratings to new ones, even SPECint states the standards should be considered separate and distinct with no direct conversion.  End of story.e2019calc_1.jpg

MetaCache (MCDB) Database Support

Once upon a time we considered simply rev’ing the existing calculator to add a single input option and basic calculations to account for the new MCDB feature.  However, what could have been delivered in a matter of minutes to under an hour, we (a nameless individual) decided a more exhaustive refresh of the calculator was warranted.  Queue a lengthy delay and numerous emails asking, “When will the 2019 Calculator be available, Brent?”  MCDB support was in fact the first thing that was added but as you can tell from this post, other work followed.  The MCDB calculations are based upon the same guidance we’ve provided to date, but now most of the math is done for you.  Given the variability of SSD capacities, the calculator will give you a required device count and capacity to be provisioned.  What you procure will vary based upon the values provided and what’s practically available on the market.  Device count should be the overriding determination in how many devices to use.e2019calc_2.jpg

2TB Database Limit

The Exchange Team has always recommended that customers limit database size to 2TB.  Previous versions of the calculator would frequently treat this as a “suggestion” and happily specify larger databases complete with a warning to not exceed 2TB.  That has changed in this updated version of the calculator.  The recommended maximum limit of 2TB for JBOD deployments, and 200GB for RAID deployments will be enforced by default.  Depending upon your configuration, you may see a small increase in the number of DB’s specified by the calculator.  We have worked to make certain that disks are still utilized to the greatest extent possible.  Should you choose to ignore the best advice of the Exchange Team, the calculator will allow you to override the maximum database size, both larger or smaller than what we have chosen by default.

You will notice that this change causes designs to be capacity bound more frequently than IO bound, especially with large mailboxes.  A trend that was already observed in previous versions.  Given the multi-year journey to reduce IO, investments to scale out O365 and now the inclusion of MCDB, it shouldn’t be a surprise that the days of the typical on-premises server being IO bound are in the rear-view mirror.  We think that’s cool, don’t you?

Summary

We are excited to release this version of the Exchange Sizing Calculator and hope you find the changes we have made valuable. For the best experience we recommend you use Microsoft Office Professional Plus 2019 or Microsoft Office 365 ProPlus. And now that you are excited as well, and even if you aren’t, you’re probably saying give me the download link already.  Well that’s the last change we are announcing.  The Exchange 2019 Calculator will be included in the DVD .ISO.  So yes, you must wait just a few more days for the release of Cumulative Update 2 before you can take it for a test drive.  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.

The Exchange Team

32 Comments

Thanks for the updated support for hypervisors. That will simplify the discussions when it comes to resources discussion.

Regular Visitor

Good to hear there's an updated calculator. Including the Calculator in the ISO? You're kidding us... This means every time I want to download a copy I have to download the ISO. Which is not available as a normal download by the way! It seems you're trying to make it overly complicated for "normal" people to be able to download the stuff. As a consulting company I don't have a Enterprise Agreement. Yet I want to use the calculator for my projects... Come on Exchange Team! You can do better...

Hey Christian, MSDN has the Exchange 2019 bits too. The calculator will only be updated once per CU, so you don't need to download it any more often than you would the bits. 

Occasional Contributor

Thank you @The_Exchange_Team for updating the Exchange Calculator, we are looking forward to Exchange Server 2019. Just had a question regarding the maximum database limit:

 

The recommended maximum limit of 2TB for JBOD deployments, and 200GB for RAID deployments will be enforced by default

Wanted to see why the RAID deployments are limited by default to a 200GB database maximum size? Would it be possible to get the technical reason behind setting that limit? 

Microsoft

@Michael Hincapie, the 200GB limit is not new.  It's been in place for quite some time when our preferred JBOD based solutions are not used.  You still have the ability to override default database size if you desire.  Obviously, it's not our recommendation however.

Occasional Contributor

The requirements for a Hybrid Management Server when all mailboxes are in Exchange Online would also be helpful. The recommended 128GB is a little.. well how do I put this... extreme! 

Regular Visitor

I totally agree with comments from Christian Schindler, why in earth is it only available with the ISO! Come on Microsoft!!!!

 
Regular Visitor

Agreed on the availability model.  You need to buy Exchange (or an MSDN subscription first because it's not available like previous versions of Exchange) to get the document to plan its deployment on physical servers that you need to order before you'd want to install the software you need to buy.... or that you could use the same document to make the cost justification to spin up an Office365 tenant and move to that. 

 

The previous distribution model seemed to work pretty well on the Technet Gallery, not sure how an Excel file logically fits well on a product ISO?  Seems silly to download >1GB ISO for a <2MB Excel spreadsheet, don'tchya think?

Frequent Visitor

Hello,

How calculator calculates memory configuration for exchange 2019 server?

 

Its already stated as 128 GB for MBX role....?

 

So your calc will add more memory on top of base 128 GB memory?

 

OR

 

Now calc will bring down actual memory requirements for exchange 2019 ????????

 

Some how its look like, you are insisting every one to go with O365, but smart customers have forced you to publish calculator ?

 

 

Microsoft

@Mahesh PM, the memory calculation was updated for Exchange Server 2019 to factor in CPU cores.  The memory calculation starts with a minimum value for Store memory and JET cache based upon # of users and # of databases.  Then it makes certain that there is 4GB/Core allocated.  If the user and database counts are low, but the core count is high, the memory requirement will be larger in Exchange Server 2019 to support the memory requirements of the core density.  Our experience has shown that as core density increases, available memory must increase as well.

Regular Visitor

I want calculator. but I can't find Download link.

somebody help me please!

Frequent Visitor

It's available in the Exchange Server 2019 Cumulative Update 2 (CU2) package. Microsoft is not releasing the Calculator as a standalone package anymore.

Frequent Visitor

Could someone PLEASE help me understand what I'm doing wrong here? I can't have more than 8 Servers per DAG, even though the tools says "between 1 and 16"?

 

Also, the number of Servers remains at 8, regardless of how many mailboxes I input. Is there an auto-increment trigger that I have missed?

Exchange-Calculator-2019_Error.png

 

Thanks

Occasional Visitor
"Moving this to the .ISO will allow us to update the calculator more readily and more frequently" Exactly, creating an excel document, adding it to an iso image, then uploading that to the internet is much faster than just uploading the excel document. When I tell people that, they look at me like I'm crazy... /s
Occasional Visitor

Hi

i can find only Exchange Server Role Requirements Calculator v9.1, for exchange 2013/2016.

https://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780

 

were can i find calculator for 2019 ?

 

Thanks,

Raviv

@RavivY  - it's on the 2019 ISO, as stated in the Summary section above. It's now owned by the core engineering team, so it ships as part of the final product. 

Occasional Visitor

Does the sizing calculator make allowance for those organisations who wish to work in on-line mode?

Frequent Visitor

I posted a question about this new Calculator almost two months ago. No response to-date.

 

Microsoft Support just informed me that I need to pay up in order for them to be able to field questions related to the Calculator. Interesting....

 

Let me ask the question here again... has the maximum number of Mailbox Server in a DAG changed?

If no, why does the calculator show a maximum of 8?

Why is it raising an error when I input something above 8?

And why does the error say "between 1 and 16" when it is actually enforcing a "between 1 and 8" rule?

 

What could I be doing wrong? Please help.

 

 

 

E2K19-Calculator-Bug-02.jpgE2K19-Calculator-Bug-01.jpg

Frequent Visitor

"Moving this to the .ISO will allow us to update the calculator more readily and more frequently"

 

Seriously, SOMEONE at Microsoft NEEDS to rethink the sanity of this decision. Downloading 6.1GB of iso just to obtain a 760KB file is illogical and doesn't factor in the fact that a majority of humans still live in parts of the world where data is neither "free" nor abundant.

 

Please make this "Calculator" available in some other fashion - before you turn your customers into unwitting Victims of internet "Do-Gooders" who will be very glad to supply them a more logical and easier access to trojanized copies.

@Deji Akomolafe  - The maximum has not changed, it is still 16.  If it is only allowing 8 it's because you have chosen site resilient deployment.  If you turn off site resilience the maximum node count is 16. 

Frequent Visitor
Occasional Visitor

Hi,

Got the ISO  on VLSC, but can't find the calculator in it.

Could you give me the filename or the path where we can find it?

tried with 2019 and 2016...

Thank you for your help 

 

ISO filename:

SW_DVD9_Exchange_Svr_2019_CU_3_MultiLang_Std_Ent_.iso_MLF_X22-18612.ISO

and 

SW_DVD9_Exchange_Svr_2016_CU_14_MultiLang_Std_Ent_.iso_MLF_X22-18627.ISO

Senior Member

As per the previous question which doesn't appear to have been answered, where do I find the calculator on the Ex2019 ISO?

 

Microsoft ... it really shouldn't be this hard!

Senior Member

Found it in the \Support folder of the CU2 or higher ISO. The file is named Calculator 10-0.xlsm. Hope this helps others looking for the calculator.

Occasional Visitor

So a potential customer has to pay the big bucks--FIRST.  Only then can they get the calculator to size the project.  Only then can they get server hardware quotes.  Only then can they have all of the answers to build a project budget with the TCO.  And FINALLY they realize they cannot get it approved--but have ALREADY spent half of it (for the software)????

 

Who the heck will win a consulting engagement like that???

 

Has no one in the current Exchange team ever had to build a business case???

 

PLEASE make ALL sales and planning docs EASILY, QUICKLY, & PUBLICLY available--for FREE!  THAT then engenders customers' trust!

@LydaRA_SP - the calc is available on MSDN, you don't need to buy Exchange licences to get to it. 

New Contributor

If we give 50 GB mailbox size then we get the following error. How come 50 GB size mailbox changes the number of mailboxes requirements?

I think it is a bug, could you tell me what am I doing wrong?

 

E2019 Calc Error.png

 

New Contributor
Another concern, why was it decided to add the calculator only in the ISO, I would think of getting in the ISO and direct public download would be ease of use. To get a file of 763 KB, we have to download ISO of over 5 GB. Think of a consultant, who is travelling with 1 GB data limit per day, Then their is no way to get the calculator. It does not sounds right. Please see if you can ease the download.
Occasional Visitor
The New Exchange Server Role Requirements Calculator seems have got Gotchas. When I try and size for 200K Mail boxed it seems to provide Weird Results. Can some one help me here.
Occasional Visitor
The New Exchange Server Role Requirements Calculator seems have got Gotchas. When I try and size for 200K Mail boxed it seems to provide Weird Results. Can some one help me here. CPU Utilization: 16000%
New Contributor

aayaz - I hope you calculated Specint2017 and not Specint2006.

If you wish you can send your calculation to my pn@GoldenFive.net and I will see what is going on.

Visitor

exchange 2019 with 400 mailboxes and 1TB DB how many GB for RAM required and Cores of CPU?