%3CLINGO-SUB%20id%3D%22lingo-sub-1649072%22%20slang%3D%22en-US%22%3EReleased%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1649072%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20servicing%20cumulative%20updates%20for%20Exchange%20Server%202016%20and%202019.%26nbsp%3BThese%20updates%20include%20fixes%20for%20customer%20reported%20issues%20as%20well%20as%20all%20previously%20released%20security%20updates.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20full%20list%20of%20fixes%20is%20contained%20in%20the%20KB%20article%20for%20each%20CU%2C%20but%20we%20wanted%20to%20highlight%20the%20following.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%20id%3D%22toc-hId--1267535191%22%3ECalculator%20Updates%3C%2FH2%3E%0A%3CP%3EA%20few%20bug%20fixes%20are%20included%20in%20this%20quarterly%20release%20of%20the%20Exchange%20Sizing%20Calculator.%26nbsp%3BThe%20calculator%20was%20updated%20to%20ensure%20CPU%20usage%20was%20correctly%20calculated%20in%20some%20scenarios%20and%20an%20issue%20in%20which%20when%20the%20second%20node%20was%20removed%20in%20worst%20case%20failure%20scenario%2C%20and%20which%20resulted%20in%20a%20zero%20transport%20DB%20size%20when%20Safety%20Net%20was%20enabled%20was%20also%20resolved.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%20id%3D%22toc-hId-1219977642%22%3ESurface%20Hub%20Teams%20and%20Skype%20Experience%3C%2FH2%3E%0A%3CP%3EWhen%20Exchange%20Server%202019%20CU5%20and%20Exchange%20Server%202016%20CU16%20were%20released%20we%20subsequently%20discovered%20issues%20with%20Surface%20Hub%20devices%20configured%20with%20on-premises%20mailboxes.%20In%20those%20cases%20if%20both%20the%20Teams%20and%20Skype%20for%20Business%20clients%20were%20installed%20side%20by%20side%2C%20the%20Surface%20Hub%20would%20pick%20the%20incorrect%20client%20when%20joining%20meetings.%20The%20CU%E2%80%99s%20issued%20today%20resolved%20these%20issues.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%20id%3D%22toc-hId--587476821%22%3ERelease%20Details%3C%2FH2%3E%0A%3CP%3EThe%20KB%20articles%20that%20describe%20the%20fixes%20in%20each%20release%20and%20product%20downloads%20are%20available%20as%20follows%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EExchange%20Server%202019%20Cumulative%20Update%207%20(%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fkb%2FKB4571787%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3EKB4571787%3C%2FA%3E)%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2FLicensing%2Fservicecenter%2Fdefault.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3EVLSC%20Download%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202016%20Cumulative%20Update%2018%20(%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fkb%2FKB4571788%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3EKB4571788%3C%2FA%3E)%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3Ffamilyid%3D42086856-b6eb-4c6c-96cd-1c9d33a07d04%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3Ffamilyid%3D99d303cb-4815-4466-a924-328beaebfca2%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3EUM%20Lang%20Packs%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH2%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%20id%3D%22toc-hId-1900036012%22%3EAdditional%20Information%3C%2FH2%3E%0A%3CP%3EMicrosoft%20recommends%20all%20customers%20test%20the%20deployment%20of%20any%20update%20in%20their%20lab%20environment%20to%20determine%20the%20proper%20installation%20process%20for%20your%20production%20environment.%20For%20information%20on%20extending%20the%20schema%20and%20configuring%20Active%20Directory%2C%20please%20review%20the%20appropriate%20documentation.%3C%2FP%3E%0A%3CP%3EAlso%2C%20to%20prevent%20installation%20issues%20you%20should%20ensure%20that%20the%20Windows%20PowerShell%20Script%20Execution%20Policy%20is%20set%20to%20%E2%80%9CUnrestricted%E2%80%9D%20on%20the%20server%20being%20upgraded%20or%20installed.%20To%20verify%20the%20policy%20settings%2C%20run%20the%20Get-ExecutionPolicy%20cmdlet%20from%20PowerShell%20on%20the%20machine%20being%20upgraded.%20If%20the%20policies%20are%20NOT%20set%20to%20Unrestricted%20you%20should%20use%20the%20resolution%20steps%20in%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Fplan-and-deploy%2Fdeployment-ref%2Fms-exch-setupreadiness-powershellexecutionpolicycheckset%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20to%20adjust%20the%20settings.%3C%2FP%3E%0A%3CP%3EReminder%3A%20Customers%20in%20hybrid%20deployments%20where%20Exchange%20is%20deployed%20on-premises%20and%20in%20the%20cloud%2C%20or%20who%20are%20using%20Exchange%20Online%20Archiving%20(EOA)%20with%20their%20on-premises%20Exchange%20deployment%20are%20required%20to%20deploy%20the%20currently%20supported%20cumulative%20update%20for%20the%20product%20version%20in%20use%2C%20e.g.%2C%202013%20Cumulative%20Update%2023%3B%202016%20Cumulative%20Update%2018%20or%2017%3B%202019%20Cumulative%20Update%207%20or%206.%3C%2FP%3E%0A%3CP%3EFor%20the%20latest%20information%20on%20the%20Exchange%20Server%20and%20product%20announcements%20please%20see%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150540(v%3Dexchg.160).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3EWhat's%20New%20in%20Exchange%20Server%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150489(v%3Dexchg.160).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%20noopener%20noreferrer%22%3EExchange%20Server%20Release%20Notes%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3ENote%3A%20Documentation%20may%20not%20be%20fully%20available%20at%20the%20time%20this%20post%20is%20published.%3C%2FP%3E%0A%3CP%3EThe%20Exchange%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1649072%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20servicing%20cumulative%20updates%20for%20Exchange%20Server%202016%20and%202019.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1649072%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1668919%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1668919%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20there%20any%20AD%20Prep%20or%20Schema%20changes%20needed%20between%20Exchange%202016%20CU17%20%26amp%3B%20the%20newly%20released%20CU18%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1668994%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1668994%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Microsoft%20%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20information.%20I%20believe%20we%20have%20to%20wait%20till%20the%20article%20is%20updated%20as%20getting%20page%20not%20found%20errors%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4571787%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%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4571787%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4571787%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%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4571787%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1669078%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1669078%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Lukas%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELinks%20are%20accessible%20now%26nbsp%3B%20Thank%20you%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1668767%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1668767%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1673018%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1673018%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%3CSTRONG%3EKB4571788%26nbsp%3B%3C%2FSTRONG%3Efor%20Exchange%202016%20CU18%20says%3A%20-%3CBR%20%2F%3E%22If%20you%20are%20upgrading%20from%26nbsp%3BCumulative%20Update%2013%20for%20Exchange%20Server%202016%26nbsp%3Bor%26nbsp%3Ba%20later%20cumulative%20update%26nbsp%3Bfor%20Exchange%20Server%202016%20to%26nbsp%3BCumulative%20Update%2018%26nbsp%3Bfor%20Exchange%20Server%202016%2C%20then%20there%E2%80%99s%20%3CU%3Eno%20need%20to%20run%3C%2FU%3E%20the%26nbsp%3B%2FPrepareAD.%3CBR%20%2F%3EHowever%2C%20in%20your%20comment%20above%20to%20J_ware%2C%20you%20are%20saying%20that%3A%20-%3CBR%20%2F%3E%22objectVersion%20(Default)%20was%20increased%20to%2013238%20(2016)%2013238%20(2019)%20and%20objectVersion%20(Configuration)%20to%2016218%20(2016)%2016755%20(2019)%2C%20so%20%2FPrepareAD%20%3CU%3Eis%20required%3C%2FU%3E%22%3CBR%20%2F%3ECould%20you%20please%20clarify%3F%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1678767%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1678767%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20required%20to%20reboot%20the%20server%20after%20upgrading%20CU%2017%20to%2018%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnattended%20setup%20does%20not%20mention%20this%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1669031%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1669031%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350201%22%20target%3D%22_blank%22%3E%40j_ware%3C%2FA%3E%26nbsp%3Bthere%20are%20no%20Schema%20changes%20but%26nbsp%3B%3CSTRONG%3EobjectVersion%20(Default)%3C%2FSTRONG%3E%20was%20increased%20to%26nbsp%3B13238%20(2016)%26nbsp%3B13238%20(2019)%20and%26nbsp%3B%3CSTRONG%3EobjectVersion%20(Configuration)%26nbsp%3B%3C%2FSTRONG%3Eto%26nbsp%3B16218%20(2016)%2016755%20(2019)%2C%20so%20%2FPrepareAD%20is%20required.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDocumentation%20will%20be%20available%20very%20soon.%20Stay%20tuned.%3C%2FP%3E%3C%2FLINGO-BODY%3E

Today we are announcing the availability of quarterly servicing cumulative updates for Exchange Server 2016 and 2019. These updates include fixes for customer reported issues as well as all previously released security updates. 

A full list of fixes is contained in the KB article for each CU, but we wanted to highlight the following.

Calculator Updates

A few bug fixes are included in this quarterly release of the Exchange Sizing Calculator. The calculator was updated to ensure CPU usage was correctly calculated in some scenarios and an issue in which when the second node was removed in worst case failure scenario, and which resulted in a zero transport DB size when Safety Net was enabled was also resolved.

Surface Hub Teams and Skype Experience

When Exchange Server 2019 CU5 and Exchange Server 2016 CU16 were released we subsequently discovered issues with Surface Hub devices configured with on-premises mailboxes. In those cases if both the Teams and Skype for Business clients were installed side by side, the Surface Hub would pick the incorrect client when joining meetings. The CU’s issued today resolved these issues.

Release Details

The KB articles that describe the fixes in each release and product downloads are available as follows:

Additional Information

Microsoft recommends all customers test the deployment of any update in their lab environment to determine the proper installation process for your production environment. For information on extending the schema and configuring Active Directory, please review the appropriate documentation.

Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded. If the policies are NOT set to Unrestricted you should use the resolution steps in here to adjust the settings.

Reminder: Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the currently supported cumulative update for the product version in use, e.g., 2013 Cumulative Update 23; 2016 Cumulative Update 18 or 17; 2019 Cumulative Update 7 or 6.

For the latest information on the Exchange Server and product announcements please see What's New in Exchange Server and Exchange Server Release Notes.

Note: Documentation may not be fully available at the time this post is published.

The Exchange Team

15 Comments
Regular Visitor

 :)

Senior Member

Are there any AD Prep or Schema changes needed between Exchange 2016 CU17 & the newly released CU18?

Regular Visitor

Hello Microsoft ,

 

Thank you for the information. I believe we have to wait till the article is updated as getting page not found errors

 

https://support.microsoft.com/en-us/help/4571787

https://support.microsoft.com/en-us/help/4571787

Microsoft

@j_ware there are no Schema changes but objectVersion (Default) was increased to 13238 (2016) 13238 (2019) and objectVersion (Configuration) to 16218 (2016) 16755 (2019), so /PrepareAD is required.

 

Documentation will be available very soon. Stay tuned.

Microsoft

@Ajit Terdalkar yes, you're right. Stay tuned. They will be online very soon.

Regular Visitor

Hello Lukas,

 

Links are accessible now  Thank you 

Occasional Visitor

I have downloaded Exchange 2019 CU7, when I do an update - there will be CU6 installed?
Is there a problem with this image? SW_DVD9_Exchange_Svr_2019_CU_7_MultiLang_Std_Ent_.iso_MLF_X22-38503.ISO
Why I start the GUI setup - there will be shown CU7, when I start the same setup with powershell, there will be shown CU6

 

I checked the image several times ...

 

???

New Contributor
@Lukas SasslKB4571788 for Exchange 2016 CU18 says: -
"If you are upgrading from Cumulative Update 13 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016 to Cumulative Update 18 for Exchange Server 2016, then there’s no need to run the /PrepareAD.
However, in your comment above to J_ware, you are saying that: -
"objectVersion (Default) was increased to 13238 (2016) 13238 (2019) and objectVersion (Configuration) to 16218 (2016) 16755 (2019), so /PrepareAD is required"
Could you please clarify?
 
Microsoft

@sjhudson let me check that. I guess it's a mistake. 

Occasional Visitor

Is it required to reboot the server after upgrading CU 17 to 18?

 

Unattended setup does not mention this

 

@mp2884  - Thanks for reporting. We're investigating. 

Senior Member

@Martijn Westera yes, you will need to reboot after installing a CU.

Microsoft

@mp2884 

We've checked this and it looks like you've run setup.exe by using PowerShell without using the full path or ".\" (as we've described it here in step 3: https://docs.microsoft.com/en-us/exchange/plan-and-deploy/deploy-new-installations/unattended-instal....

 

When calling the setup.exe in PowerShell without executing using the full path or ".\" under its current directory, Exchange setup process seems to treat the Setup.exe based on environment variable, and the local Exchange installation path will be set as the "sourcedir" and you end up in the described behavior.

 

Please make sure to run setup.exe using the full path or ".\" to avoid this scenario.

Senior Member

@mp2884 @Lukas Sassl  I always use a "Run As Administrator" command prompt for running CU updates or any other Exchange installer, and also make sure all interactive powershell sessions are closed and no one else is logged on to the server; if someone else is logged on and has the exchange management shell open that will cause the install to fail.

Microsoft

@j_ware This is exemplary and highly recommended. Anyway - in the scenario described above setup is executed and at first glance it looks successful but after the setup process you're still on the same Exchange build because we don't use the new bits from the Exchange CU .iso due to the wrong "sourcedir". To avoid this, call setup.exe by using the full path in unattended mode: E:\setup.exe (PowerShell and/or cmd) or if you're in the same directory .\setup.exe (PowerShell only) should also do the job.