Home
%3CLINGO-SUB%20id%3D%22lingo-sub-700462%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700462%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20wanted%20to%20post%20a%20quick%20note%3A%20we%20are%20aware%20of%20slight%20delay%20of%20downloads%20actually%20being%20available.%20We%20are%20working%20on%20this!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700497%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700497%22%20slang%3D%22en-US%22%3Eglad%20to%20hear%20that.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-701385%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701385%22%20slang%3D%22en-US%22%3EPlease%2C%20make%20CU2%20for%20Exchange%202019%20available%20at%20least%20on%20MSDN%20(Visual%20Studio%20Subscriptions)%20and%2For%20Microsoft%20partner%20benefit%20downloads%20to%20give%20ISVs%20faster%20access%20to%20Exchange%20versions%20which%20are%20used%20by%20our%20customers%20soon.%20Please%2C%20not%20the%20same%20waiting%20game%20as%20with%20CU1.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-706079%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-706079%22%20slang%3D%22en-US%22%3E%3CP%3ECongrats%20and%20thanks%20for%20the%20release%2C%20still%20waiting%20for%20Exchange%20Server%202019%20CU2%20to%20show%20up%20in%20MPN%20of%20VLSC...%3C%2FP%3E%3CP%3EOne%20other%20thing%2C%20the%20download%20link%20for%20the%20UM%20Language%20Packs%20for%20Exchange%20Server%202013%20CU23%20is%20pointing%20to%20the%20CU22%20version%20of%20the%20UM%20Language%20Packs.%20The%20correct%20URL%20is%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D58394%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%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D58394%3C%2FA%3E%26nbsp%3B(but%20only%20en-us%20is%20available%20at%20this%20moment).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-706127%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-706127%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20for%20the%202016%20UM%20Language%20Packs%2C%20it's%20only%20the%20en-us%20available.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-706823%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-706823%22%20slang%3D%22en-US%22%3E%3CP%3EI%20thought%20that%20the%20supported%20versions%20for%20hybrid%20deployments%20were%20N%20and%20N-1.%20But%20the%20article%20says%20that%20only%26nbsp%3B%3CSPAN%3ECumulative%20Update%2023%20is%20supported%20for%20the%20Exchange%202013.%20Does%20that%20mean%20that%20for%20Exchnage%202013%2C%20only%20the%20latest%20version%20is%20supported%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks!%20%3A)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-707125%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-707125%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F71714%22%20target%3D%22_blank%22%3E%40Damian%20Scoles%3C%2FA%3E%26nbsp%3Bsure%20thing.%20Will%20take%20care%20of%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3ECan%20you%20update%20the%26nbsp%3B%3CFONT%3EExchange%20Server%20supportability%20matrix%3C%2FFONT%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eto%20show%20.NET%204.8%20support%20for%20these%20updates%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20title%3D%22Exchange%20Server%20supportability%20matrix%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%22%20target%3D%22_self%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%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-201...%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%3CBR%20%2F%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-708076%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-708076%22%20slang%3D%22en-US%22%3E%3CP%3ELanguage%20packs%20and%20MSDN%20bits%20are%20on%20the%20way%20rest%20assured.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-710853%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-710853%22%20slang%3D%22en-US%22%3EWhy%20still%20no%20post%20on%20the%20%22Defense%20in%20Depth%22%20security%20updates%20for%20Exchange%3F%20This%20failed%20on%20my%20servers%20and%20left%20them%20in%20an%20unusable%20state%20and%20I%20know%20from%20posts%20elsewhere%20i'm%20not%20alone.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-710973%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-710973%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F363817%22%20target%3D%22_blank%22%3E%40TheVogon%3C%2FA%3E%26nbsp%3B-%20we're%20not%20planning%20to%20do%20a%20post%20on%20those%20updates.%20We've%20also%20not%20heard%20of%20the%20issues%20you%20mentioned%2C%20so%20you%20really%20should%20call%20in%20to%20support%20so%20they%20can%20help.%20If%20your%20servers%20are%20in%20an%20unusable%20state%20I%20really%20hope%20you've%20already%20called%20support%2C%20this%20isn't%20the%20best%20place%20to%20resolve%20that.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-713679%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-713679%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Exchange%20Team%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20releasing%20quarterly%20updates.%20Exchange%202019%20CU2%20is%20still%20not%20available%20for%20download.%20Do%20you%20think%20you%20could%20fix%20this%20before%20weekend%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20again%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-713750%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-713750%22%20slang%3D%22en-US%22%3EI%20dont%20see%20CU2%20in%20the%20VLSC%20yet.%20Any%20ETA%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-713791%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-713791%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20checking%20into%20the%20download%20issues%2C%20sorry%20about%20that.%20I%20really%20do%20hope%20we'll%20resolve%20that%20today.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714311%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714311%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Friday%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%20Any%20news%20yet%20on%20the%20availability%20of%20Exchange%202019%20CU2%20yet%3F%20I%20have%20an%20Exchange%202019%20server%20that%20needs%20to%20be%20built%20and%20am%20waiting%20for%20CU2%20instead%20of%20CU1%20and%20then%20updating.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ERay%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714327%22%20slang%3D%22en-US%22%3ERE%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714327%22%20slang%3D%22en-US%22%3EMSDN%20is%20live%20now.%20We're%20checking%20VLSC%20again.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714357%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714357%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%2C%20thanks%20for%20updating%20the%20matrix%20page.%26nbsp%3B%20However%20I%20see%20that%20Exchange%202013%20CU23%20supports%20only%20.NET%204.8%3F%26nbsp%3B%20I%20think%20that%20is%20incorrect%20and%20should%20show%20that%20it%20supports%20.NET%204.7.2%20and%20.NET%204.8%20due%20to%20your%20statement%20that%20.NET%204.8%20will%20not%20be%20required%20until%20December%3F%26nbsp%3B%20Maybe%20I%20am%20reading%20that%20wrong%20for%20Exchange%202013.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENext%2C%20I%20see%20Exchange%202019%20CU2%20is%20now%20available%20on%20MSDN.%26nbsp%3B%20However%2C%20no%20other%20versions%20are%20available%20for%20download%3F%26nbsp%3B%20I%20thought%20you%20were%20going%20to%20make%20at%20least%20one%20rev%20or%20two%20back%20allowed%20for%20downloading%2C%20but%20RTM%20and%20CU1%20are%20no%20longer%20available.%26nbsp%3B%20Curious%20if%20that%20was%20a%20mistake%20or%20overlooked%3F%26nbsp%3B%20Or%20is%20this%20the%20new%20policy%20of%20only%20leaving%20the%20most%20current%20available%3F%26nbsp%3B%20Now%20mind%20you%20this%20is%20only%20on%20MSDN%2C%20I%20don't%20have%20access%20to%20VLSC%20to%20see%20if%20that%20is%20any%20different.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714394%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714394%22%20slang%3D%22en-US%22%3EGreg%20-%20why%20no%20post%20on%20the%20Defense%20in%20Depth%20update%3F%20Since%20when%20have%20updates%20pushed%20out%20as%20critical%20had%20zero%20explanation%20anywhere%20of%20what%20they%20actually%20do%3F%20Is%20the%20Defense%20in%20Depth%20update%20included%20in%20CU2%3F%20The%20DiD%20update%20fails%20on%20multiple%20systems%20and%20leaves%20it%20in%20a%20state%20where%20the%20exchange%20services%20no%20longer%20start%2C%20you%20cant%20reinstall%20the%20update%20or%20reinstall%20CU1.%20See%20details%20and%20how%20I%20fixed%20it%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Feightwone.com%2F2019%2F06%2F12%2Fsecurity-updates-exchange-2013-2019-2010%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%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%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%2Feightwone.com%2F2019%2F06%2F12%2Fsecurity-updates-exchange-2013-2019-2010%2F%3C%2FA%3E%20And%20as%20you%20can%20see%20from%20that%20page%2C%20i'm%20not%20the%20only%20one%20who%20had%20this%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714410%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714410%22%20slang%3D%22en-US%22%3EAnd%20as%20an%20article%20suggestion%2C%20I%20understand%20that%20.Net%204.8%20includes%20major%20performance%20enhancements%20ported%20from%20.Net%20core.%20Some%20Exchange%20benchmarks%20would%20be%20interesting....%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714472%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714472%22%20slang%3D%22en-US%22%3E%3CP%3EDamian%2C%26nbsp%3Bthis%20will%20be%20fixed%20soon%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%3EFirst%2C%20thanks%20for%20updating%20the%20matrix%20page.%26nbsp%3B%20However%20I%20see%20that%20Exchange%202013%20CU23%20supports%20only%20.NET%204.8%3F%26nbsp%3B%20I%20think%20that%20is%20incorrect%20and%20should%20show%20that%20it%20supports%20.NET%204.7.2%20and%20.NET%204.8%20due%20to%20your%20statement%20that%20.NET%204.8%20will%20not%20be%20required%20until%20December%3F%26nbsp%3B%20Maybe%20I%20am%20reading%20that%20wrong%20for%20Exchange%202013.%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714620%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714620%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F363817%22%20target%3D%22_blank%22%3E%40TheVogon%3C%2FA%3E%20there's%20nothing%20specific%20we%20want%20to%20say%20about%20that%20particular%20issue%2C%20other%20than%20we%20advise%20customers%20to%20install%20it.%20We%20don't%20usually%20explain%20security%20patched%20in%20detail%2C%20there's%20nothing%20different%20about%20this.%3C%2FP%3E%0A%3CP%3EThe%20patch%20is%20included%20in%20CU2.%3C%2FP%3E%0A%3CP%3ESometimes%20there%20are%20issues%20installing%20patches%2C%20that%20can%20happen.%20But%20I'll%20go%20back%20to%20saying%20that%20the%20best%20way%20to%20fix%20a%20serious%20issue%20that%20leaves%20your%20machine%20in%20that%20state%20is%20to%20call%20support.%20Blogs%20and%20comments%20aren't%20the%20best%20way%20to%20deal%20with%20service%2Fserver%20impacting%20issues%20-%20and%20all%20too%20often%20they%20are%20filled%20with%20bad%2C%20confusing%20and%20contradictory%20advice.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-714995%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-714995%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20calculator%20does%20not%20work%20if%26nbsp%3Buse%20mailboxes%20larger%20than%2010%20gigabytes%20in%20size.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-715026%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-715026%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20evening%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20I'm%20not%20seeing%20CU2%20on%20MSDN%2FVisual%20Studio%2C%20and%20heck%20I'm%20not%20seeing%20CU1%20there%20anymore%2C%20was%20there%20this%20morning.%20CU2%20doesn't%20seem%20to%20be%20on%20ActionPack%20either.%20CU1%20is%20still%20there.%20Am%20I%20missing%20something%3F%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ERay%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-715353%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-715353%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Occasional-Visitor%20lia-component-message-view-widget-author-username%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20white-space%3A%20nowrap%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362888%22%20target%3D%22_blank%22%3E%40vaclav_mech%3C%2FA%3E%20-%20Once%20a%20product%20reaches%20extended%20support%2C%20we%20only%20support%20the%20latest%20CU.%26nbsp%3B%20This%20was%20discussed%20in%20%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FExchange-Server-2013-Enters-Extended-Support-Lifecycle-Phase%2Fba-p%2F607811%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FExchange-Server-2013-Enters-Extended-Support-Lifecycle-Phase%2Fba-p%2F607811%3C%2FA%3E%3C%2FFONT%3E.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-717714%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-717714%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20will%20EX2019%20CU2%20be%20available%20for%20download%20via%20VLSC%2C%20and%20why%20are%20the%20CUs%20not%20available%20publicly%20anymore%20in%20the%20first%20place%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-718146%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-718146%22%20slang%3D%22en-US%22%3E%3CP%3E1)%20This%20article%20links%20to%20Visual%20Studio%20C%2B%2B%202012%20runtime%2C%20but%20the%20KB%20article%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4489622%2Fcumulative-update-23-for-exchange-server-2013%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4489622%2Fcumulative-update-23-for-exchange-server-2013%3C%2FA%3E)%20links%20to%202013.%26nbsp%3B%20I%20assume%20the%20KB%20takes%20precedent%3F%3C%2FP%3E%3CP%3E2)%20Other%20commenters%20referred%20to%20the%20.NET%20support%20table%2C%20which%20I%20didn't%20see%20linked%20anywhere%2C%20but%20I%20did%20find%20it%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%3C%2FA%3E%3C%2FP%3E%3CP%3E3)%20The%20KB%20article%20states%3A%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22ng-scope%22%3ECumulative%20Update%2023%26nbsp%3Bfor%20Microsoft%20Exchange%20Server%202013%20was%20released%20on%20June%26nbsp%3B18%2C%202019.%20This%20cumulative%20update%20includes%20fixes%20for%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F4489622%23nonsecurity%2520issues%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Enonsecurity%20issues%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%20all%20previously%20released%20fixes%20for%20security%20and%20nonsecurity%20issues.%20These%20fixes%20will%20also%20be%20included%20in%20later%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj907309(v%3Dexchg.150).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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ecumulative%20updates%20for%20Exchange%20Server%202013%3C%2FA%3E.%3C%2FP%3E%3CP%20class%3D%22ng-scope%22%3EThis%20update%20also%20includes%20new%20daylight%20saving%20time%20(DST)%20updates%20for%20Exchange%20Server%202013.%20For%20more%20information%20about%20DST%2C%26nbsp%3Bsee%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F22803%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDaylight%20Saving%20Time%20Help%20and%20Support%20Center%3C%2FA%3E.%3C%2FP%3E%3CP%20class%3D%22ng-scope%22%3ESo%2C%20if%20we%20are%20up%20to%20date%20on%20the%20security%20updates%2C%20does%20that%20mean%20there's%20no%20compelling%20security%20benefit%20from%20this%20CU%20and%20this%20would%20only%20provide%20the%20non-security%20benefits%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719080%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719080%22%20slang%3D%22en-US%22%3EReleased%3A%20June%202019%20Quarterly%20Exchange%20Updates%20was%20posted%20on%20the%2018th%20of%20June.%20It%20is%20now%20the%2025th.%20And%202019%20CU2%20is%20still%20not%20actually%20available%20on%20the%20VSLC.%20Perhaps%20you%20shouldn't%20make%20the%20announcement%20before%20all%20the%20download%20platforms%20are%20ready%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719653%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719653%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20there%20be%20next%20version%20of%20On%20premises%20Exchange%20released%20or%20it%20just%20the%20O365%20in%20future.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719902%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719902%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F285960%22%20target%3D%22_blank%22%3E%40Neil_Flanagan%3C%2FA%3E%26nbsp%3B-%20the%20bits%20should%20be%20there%2C%20I've%20been%20told%20by%20others%20they%20are.%20Perhaps%20it's%20a%20replication%20thing%2C%20or%20results%20are%20being%20filtered%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F366243%22%20target%3D%22_blank%22%3E%40Ravikumar_Shankarappa%3C%2FA%3E%26nbsp%3B-%20too%20early%20to%20talk%20about%20that.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719916%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719916%22%20slang%3D%22en-US%22%3EStill%20only%20CU1%20for%202019%20available%20in%20VLSC.%20Tried%20refreshing%2C%20etc.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719956%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719956%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20is%20definitely%20not%20showing%20in%20VLSC%20for%20me%2C%20either.%20You%20can%20only%20select%20'MultiLanguage'%20using%20either%20the%20download%20manager%20or%20web%20browser%20options.%20Doesn't%20matter%20what%20combination%20you%20try%2C%20still%20shows%20CU1%20only.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719959%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719959%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20not%20on%20Action%20Pack%2C%20not%20seeing%20it%20on%20MSDN%2FVisual%20studio%20either.%20CU1%20was%20on%20MSDN%2FVisual%20studio%20last%20week%2C%20now%20no%20Exchange.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-722345%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-722345%22%20slang%3D%22en-US%22%3E%3CP%3ECU2%20is%20still%20not%20available%20in%20VLSC%20and%20I%20even%20have%20a%20ticket%20that%20has%20been%20escalated%20and%20been%20open%20for%20over%206%20days%20now.%20Grrr%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-722506%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-722506%22%20slang%3D%22en-US%22%3E%3CP%3ECU2%20in%20VLSC%20is%20showing%20for%20me%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-722510%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-722510%22%20slang%3D%22en-US%22%3E%3CP%3EYup%2C%20sorry%20about%20the%20delay%20in%20getting%20the%20bits%20onto%20VLSC.%20The%20hamster%20was%20asleep%2C%20the%20wheel%20wasn't%20turning.%20We%20just%20woke%20it%20up.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-722743%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-722743%22%20slang%3D%22en-US%22%3E%3CP%3EYep%20its%20finally%20there%20after%20a%20week%20from%20announcement.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-723044%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-723044%22%20slang%3D%22en-US%22%3E%3CH2%20style%3D%22margin%3A%200px%3B%20padding%3A%200px%3B%20border%3A%200px%20currentColor%3B%20border-image%3A%20none%3B%20color%3A%20rgb(51%2C%2051%2C%2051)%3B%20text-transform%3A%20none%3B%20line-height%3A%201.25%3B%20text-indent%3A%200px%3B%20letter-spacing%3A%20normal%3B%20font-family%3A%20wf_segoe-ui_light%2C%20%26quot%3BSegoe%20UI%20Light%26quot%3B%2C%20%26quot%3BSegoe%20WP%20Light%26quot%3B%2C%20wf_segoe-ui_normal%2C%20%26quot%3BSegoe%20UI%26quot%3B%2C%20Segoe%2C%20%26quot%3BSegoe%20WP%26quot%3B%2C%20Tahoma%2C%20Verdana%2C%20Arial%2C%20sans-serif%3B%20font-size%3A%2022.5px%3B%20font-style%3A%20normal%3B%20font-weight%3A%20normal%3B%20word-spacing%3A%200px%3B%20vertical-align%3A%20baseline%3B%20white-space%3A%20normal%3B%20box-sizing%3A%20inherit%3B%20orphans%3A%202%3B%20widows%3A%202%3B%20font-stretch%3A%20inherit%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20font-variant-ligatures%3A%20normal%3B%20font-variant-caps%3A%20normal%3B%20font-variant-numeric%3A%20inherit%3B%20font-variant-east-asian%3A%20inherit%3B%20-webkit-text-stroke-width%3A%200px%3B%20text-decoration-style%3A%20initial%3B%20text-decoration-color%3A%20initial%3B%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%20id%3D%22toc-hId-1767652670%22%3EFYI%3C%2FH2%3E%0A%3CH2%20style%3D%22margin%3A%200px%3B%20padding%3A%200px%3B%20border%3A%200px%20currentColor%3B%20border-image%3A%20none%3B%20color%3A%20rgb(51%2C%2051%2C%2051)%3B%20text-transform%3A%20none%3B%20line-height%3A%201.25%3B%20text-indent%3A%200px%3B%20letter-spacing%3A%20normal%3B%20font-family%3A%20wf_segoe-ui_light%2C%20%26quot%3BSegoe%20UI%20Light%26quot%3B%2C%20%26quot%3BSegoe%20WP%20Light%26quot%3B%2C%20wf_segoe-ui_normal%2C%20%26quot%3BSegoe%20UI%26quot%3B%2C%20Segoe%2C%20%26quot%3BSegoe%20WP%26quot%3B%2C%20Tahoma%2C%20Verdana%2C%20Arial%2C%20sans-serif%3B%20font-size%3A%2022.5px%3B%20font-style%3A%20normal%3B%20font-weight%3A%20normal%3B%20word-spacing%3A%200px%3B%20vertical-align%3A%20baseline%3B%20white-space%3A%20normal%3B%20box-sizing%3A%20inherit%3B%20orphans%3A%202%3B%20widows%3A%202%3B%20font-stretch%3A%20inherit%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20font-variant-ligatures%3A%20normal%3B%20font-variant-caps%3A%20normal%3B%20font-variant-numeric%3A%20inherit%3B%20font-variant-east-asian%3A%20inherit%3B%20-webkit-text-stroke-width%3A%200px%3B%20text-decoration-style%3A%20initial%3B%20text-decoration-color%3A%20initial%3B%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%20id%3D%22toc-hId--784504291%22%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D58354%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%22%3EUpdate%20Rollup%2028%20For%20Exchange%202010%20SP3%20(KB4503028)%3C%2FA%3E%3C%2FH2%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-723095%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-723095%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20given%20up%20on%20seeing%20it%20on%20Action%20Pack%20or%20Visual%20Studio.%20CU1%20is%20on%20Action%20Pack%20and%20CU1%20was%20on%20Visual%20Studio%2C%20now%20no%20Exchange%20whatsoever%20on%20Visual%20Studio.%20I%20opened%20a%20ticket%20a%20few%20days%20ago%20and%20got%20the%20run%20around%2C%20was%20given%20a%20phone%20number%20only%20to%20be%20told%20why%20are%20you%20calling%20here....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-725544%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-725544%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F364667%22%20target%3D%22_blank%22%3E%40RaySumperl%3C%2FA%3E%26nbsp%3Bas%20Kate%20Bush%20once%20said%2C%20Don't%20Give%20Up%2C%20your%20bits%20will%20one%20day%20come.%20And%20they%20should%20now%20be%20there.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20really%20am%20sorry%20for%20the%20delay%20with%20the%20availability%2C%20we're%20doing%20our%20best%20to%20make%20sure%20we%20don't%20have%20a%20repeat%20next%20time%20round.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-725763%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-725763%22%20slang%3D%22en-US%22%3E%3CP%3EGreg%2C%3C%2FP%3E%3CP%3ETHANK%20YOU!%20I%20am%20now%20downloading%20CU2.%20I'm%20sorry%20I%20was%20SO%20obnoxious.....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERay%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-725814%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-725814%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20ok%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F364667%22%20target%3D%22_blank%22%3E%40RaySumperl%3C%2FA%3E%26nbsp%3B%2C%20all%20is%20forgiven%20and%20it's%20our%20fault%20-%20we%20need%20to%20do%20a%20better%20job.%20Have%20fun%20with%20CU2.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-725832%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-725832%22%20slang%3D%22en-US%22%3EAny%20chance%20a%20dark%20mode%20OWA%20theme%20made%20it%20into%20this%20release%3F%20Its%20a%20shame%20its%20available%20to%20online%20but%20not%20on-prem.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-725913%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-725913%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F247742%22%20target%3D%22_blank%22%3E%40m49808%3C%2FA%3E%26nbsp%3Bwe%20have%20no%20plans%20to%20add%20that%20to%20on-prem%2C%20sorry.%20Online%20now%20uses%20React%2C%20we're%20not%20putting%20that%20on-prem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-731939%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-731939%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F365786%22%20target%3D%22_blank%22%3E%40ScriptMasterSkillet%3C%2FA%3E%20Answer%20to%20your%20questions%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%26nbsp%3B%20Yes%20the%20KB%20takes%20precedence.%26nbsp%3B%20We%20have%20a%20weird%20dance%20of%20both%20VC%2B%2B2012%2F2013%20runtimes%20being%20required.%26nbsp%3B%20We%20pre-req%20on%20the%202013%20runtime%20in%20Exchange%20SETUP%2C%20but%20UCMA%20installs%20the%202012%20runtime.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%26nbsp%3B%20Self%20explanatory%20you%20found%20the%20correct%20link.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3.%26nbsp%3B%20Under%20our%20Cumulative%20Update%20support%20policy%20during%20extended%20support%2C%20we%20will%20retire%20support%20for%20Cumulative%20Update%2022%20in%20the%20near%20future.%26nbsp%3B%20That%20means%20to%20get%20future%20updates%20for%20Exchange%202013%2C%20you%20will%20need%20to%20deploy%20the%20Cumulative%20Update%2023.%26nbsp%3B%20If%20you%20have%20applied%20the%20security%20update%20for%20Cumulative%20Update%2022%2C%20you%20have%20the%20same%20fixes%20that%20were%20deployed%20in%20Cumulative%20Update%2023%20with%20the%20exception%20of%20the%20AD%20permissions%20changes%20we%20included%20in%20Cumulative%20Update%2023.%26nbsp%3B%20We%20cannot%20change%20AD%20permissions%20in%20a%20Security%20Update%20package%20because%20doing%20so%20requires%20SETUP%20%2FPrepareAD%20to%20be%20executed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-732090%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-732090%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%2C%20Brent.%3C%2FP%3E%3CP%3EAre%20there%20any%20additional%20CUs%20planned%20for%20Exchange%202013%3F%26nbsp%3B%20I%20thought%20the%20last%20one%20was%20billed%20as%20the%20last%20one%2C%20yet%20here%20we%20are.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-698398%22%20slang%3D%22en-US%22%3EReleased%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-698398%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20servicing%20cumulative%20updates%20for%20Exchange%20Server%202013%2C%202016%20and%202019.%26nbsp%3B%20These%20updates%20include%20fixes%20for%20customer%20reported%20issues%20as%20well%20as%20all%20previously%20released%20security%20updates.%26nbsp%3B%20In%20our%20ongoing%20effort%20to%20evaluate%20Exchange%20permissions%2C%20the%20updates%20released%20today%20include%20an%20Active%20Directory%20permission%20change%20which%20will%20lower%20Exchange%20Server%20permissions.%26nbsp%3B%20Additional%20details%20and%20recommended%20customer%20actions%20follow.%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EDecreasing%20Exchange%20Rights%20in%20the%20Active%20Directory%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThe%20Exchange%20Team%20has%20made%20two%20changes%20to%20the%20rights%20Exchange%20has%20in%20the%20Active%20Directory.%26nbsp%3B%20We%20have%20placed%20a%20Deny%20ACE%20on%20the%20DNS%20Admins%20group%20and%20removed%20the%20ability%20for%20Exchange%20to%20assign%20Service%20Principal%20Names%20(SPN%E2%80%99s).%26nbsp%3B%20We%20have%20determined%20these%20rights%20are%20not%20required%20by%20Exchange.%26nbsp%3B%20Before%20upgrading%20to%20one%20of%20the%20updates%20released%20today%2C%20we%20recommend%20administrators%20apply%20the%20permissions%20change%20to%20their%20environment.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20order%20to%20apply%20these%20changes%2C%20a%20directory%20admin%20will%20need%20to%20run%20the%20cumulative%20update%20setup%20program%20we%20are%20releasing%20today%20with%20the%20%2FPrepareAD%20parameter.%26nbsp%3B%20When%20multiple%20Exchange%20versions%20co-exist%20in%20a%20single%20Active%20Directory%20forest%2C%20the%20cumulative%20update%20matching%20the%20latest%20version%20of%20Exchange%20deployed%20should%20be%20used.%26nbsp%3B%20Setup%20will%20automatically%20run%20%2FPrepareDomain%20in%20the%20domain%20where%20%2FPrepareAD%20is%20executed.%26nbsp%3B%20Environments%20with%20multiple%20domains%20in%20the%20forest%20will%20need%20to%20run%20the%20cumulative%20update%20setup%20program%20using%20the%20%2FPrepareDomain%20parameter%20in%20all%20domains%20in%20the%20forest.%26nbsp%3B%20These%20steps%20will%20update%20the%20rights%20granted%20to%20Exchange%20Servers%20in%20the%20Active%20Directory%20to%20meet%20the%20new%20permissions%20scope.%26nbsp%3B%20More%20information%20on%20%2FPrepareAD%20and%20%2FPrepareDomain%20is%20available%20at%20this%20link.%3C%2FP%3E%0A%3CP%3EThe%20directory%20updates%20released%20today%20are%20fully%20compatible%20with%20all%20versions%20of%20Exchange%20Server%20regardless%20of%20cumulative%20update%20or%20update%20rollup%20version%20deployed%20and%20so%20these%20changes%20can%20be%20applied%20to%20any%20existing%20Exchange%20deployment%20by%20following%20the%20steps%20above.%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3ESupport%20for%20.NET%20Framework%204.8%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThe%20updates%20released%20today%20add%20support%20for%20.NET%20Framework%204.8.%26nbsp%3B%20The%20minimum%20.NET%20requirement%20remains%204.7.2%20on%20Exchange%20Servers.%26nbsp%3B%20.NET%204.8%20will%20be%20required%20with%20all%20updates%20released%20in%20December%202019%20and%20later.%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EAuthentication%20Policies%20Update%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EWith%20the%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4471391%2Fcumulative-update-1-for-exchange-server-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efirst%20cumulative%20update%20(CU1)%20for%20Exchange%202019%3C%2FA%3E%20we%20shipped%20our%20initial%20implementation%20of%20disabling%20legacy%20authentication%20protocols%20on%20a%20per%20user%20basis.%3C%2FP%3E%0A%3CP%3EIn%20today%E2%80%99s%20second%20cumulative%20update%20we%20have%20now%20enhanced%20the%20feature%20to%20provide%20the%20ability%20to%20specify%20it%20as%20default%20authentication%20policy%20at%20Organization%20level.%3C%2FP%3E%0A%3CP%3EWe%20will%20be%20releasing%20an%20updated%20blog%20very%20soon%20providing%20more%20information%20about%20the%20feature%20and%20instructions%20on%20how%20to%20use%20it.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EFuture%20support%20of%20Modern%20Authentication%20in%20on-premises%20Exchange%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EOver%20the%20past%20couple%20of%20years%2C%20you%20have%20seen%20us%20deliver%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FAnnouncing-Hybrid-Modern-Authentication-for-Exchange-On-Premises%2Fba-p%2F607476%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EModern%20Authentication%20to%20Exchange%20when%20running%20a%20hybrid%20organization%3C%2FA%3E.%26nbsp%3B%20The%20usual%20follow-on%20question%20from%20a%20handful%20of%20customers%20has%20been%2C%20%E2%80%9CWhen%20will%20modern%20authentication%20be%20supported%20in%20non-hybrid%20environments%3F%E2%80%9D%26nbsp%3B%20Our%20response%20was%20typically%20something%20along%20the%20lines%20of%2C%20%E2%80%9CWe%E2%80%99re%20looking%20into%20it.%E2%80%9D%26nbsp%3B%20While%20that%20statement%20was%20true%20and%20accurate%2C%20after%20much%20deliberation%20we%20have%20come%20to%20the%20decision%20that%20this%20capability%20in%20on-premises%20Exchange%20server%20will%20no%20longer%20be%20pursued.%26nbsp%3B%20Our%20investments%20in%20Modern%20Authentication%20will%20be%20restricted%20to%20those%20with%20hybrid%20deployments.%26nbsp%3B%20We%20know%20this%20will%20be%20a%20disappointment%20for%20some%20customers%20but%20we%20wanted%20to%20make%20certain%20you%20were%20aware%20of%20this%20change%20in%20strategy.%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EControlled%20Connections%20to%20Public%20Folders%20in%20Outlook%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EAs%20we%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FAnnouncing-Support-for-Controlled-Connections-to-Public-Folders%2Fba-p%2F608591%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eannounced%20towards%20the%20end%20of%20last%20year%3C%2FA%3E%2C%20we%20added%20support%20to%20Exchange%20Online%20to%20help%20admins%20have%20control%20over%20which%20users%20would%20see%20public%20folders%20in%20their%20Outlook%20clients.%3C%2FP%3E%0A%3CP%3EWe%20are%20including%20this%20functionality%20in%20Exchange%20Server%202019%20Cumulative%20Update%202%20and%20Exchange%20Server%202016%20Cumulative%20Update%2013%2C%20both%20released%20today.%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3ERelease%20Details%3C%2FFONT%3E%3C%2FP%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%202%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4488401%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EKB4488401%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%22%3EVLSC%20Download%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202016%20Cumulative%20Update%2013%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4488406%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EKB4488406%3C%2FA%3E)%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3De14b880f-5bb1-4a6e-8c7a-3362b8ae8770%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D76a11a83-b9ac-44e4-83a5-d49b1470fd17%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EUM%20Lang%20Packs%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202013%20Cumulative%20Update%2023%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4489622%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EKB4489622%3C%2FA%3E)%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D4706d685-777d-4761-81a2-5736f38c21f8%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D58394%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%3CP%3E%3CFONT%20size%3D%224%22%3EAdditional%20Information%3C%2FFONT%3E%3C%2FP%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%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fprepare-active-directory-and-domains-exchange-2013-help%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edocumentation%3C%2FA%3E.%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%20KB981474%20to%20adjust%20the%20settings.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EReminder%3A%20%3C%2FSTRONG%3ECustomers%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%2013%20or%2012%3B%202019%20Cumulative%20Update%202%20or%201.%3C%2FP%3E%0A%3CP%3EFor%20the%20latest%20information%20on%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%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%22%3EExchange%20Server%20Release%20Notes%3C%2FA%3E.%26nbsp%3B%20You%20can%20also%20find%20updated%20information%20on%20Exchange%20Server%202013%20in%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150540(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWhat%E2%80%99s%20New%20in%20Exchange%20Server%202013%3C%2FA%3E%2C%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150489(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ERelease%20Notes%3C%2FA%3E%20and%20product%20documentation%20available%20on%20Docs.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EImportant%3A%3C%2FSTRONG%3E%26nbsp%3B%20To%20avoid%20a%20setup%20failure%2C%20it%20is%20necessary%20to%20install%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3Fid%3D30679%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EVisual%20C%2B%2B%202012%20runtime%3C%2FA%3E%20%3CSTRONG%3Ebefore%3C%2FSTRONG%3E%20installing%20the%20updates%20released%20today%20on%20Edge%20role%20if%20not%20already%20present.%3C%2FP%3E%0A%3CP%20class%3D%22note%22%3ENote%3A%20Documentation%20may%20not%20be%20fully%20available%20at%20the%20time%20this%20post%20is%20published.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-698398%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20servicing%20cumulative%20updates%20for%20Exchange%20Server%202013%2C%202016%20and%202019.%26nbsp%3B%20These%20updates%20include%20fixes%20for%20customer%20reported%20issues%20as%20well%20as%20all%20previously%20released%20security%20updates...%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-698398%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-701512%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701512%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20update%20the%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EExchange%20Server%20supportability%20matrix%3C%2FFONT%3E%20to%20show%20.NET%204.8%20support%20for%20these%20updates%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20title%3D%22Exchange%20Server%20supportability%20matrix%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748688%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748688%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20are%20the%20SHA1%2FSHA256%20hashes%20for%20ExchangeServer2016-x64-cu13.iso%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4471392%2Fcumulative-update-12-for-exchange-server-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4471392%2Fcumulative-update-12-for-exchange-server-2016%3C%2FA%3Ehas%20the%20has%20SHA1%20and%20SHA256%20for%20ExchangeServer2016-x64-cu12.iso%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4488406%2Fcumulative-update-13-for-exchange-server-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4488406%2Fcumulative-update-13-for-exchange-server-2016%3C%2FA%3Edoes%20not%20have%20the%20hashes%20for%20ExchangeServer2016-x64-cu13.iso%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748704%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748704%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F374393%22%20target%3D%22_blank%22%3E%40kevinds%3C%2FA%3E%26nbsp%3Bpreviously%20CU%20includes%20fixes%20for%20security%20issues.%20Therefore%20we%E2%80%99ve%20published%20the%20SHA%20hashes.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E

Today we are announcing the availability of quarterly servicing cumulative updates for Exchange Server 2013, 2016 and 2019.  These updates include fixes for customer reported issues as well as all previously released security updates.  In our ongoing effort to evaluate Exchange permissions, the updates released today include an Active Directory permission change which will lower Exchange Server permissions.  Additional details and recommended customer actions follow.

Decreasing Exchange Rights in the Active Directory

The Exchange Team has made two changes to the rights Exchange has in the Active Directory.  We have placed a Deny ACE on the DNS Admins group and removed the ability for Exchange to assign Service Principal Names (SPN’s).  We have determined these rights are not required by Exchange.  Before upgrading to one of the updates released today, we recommend administrators apply the permissions change to their environment. 

In order to apply these changes, a directory admin will need to run the cumulative update setup program we are releasing today with the /PrepareAD parameter.  When multiple Exchange versions co-exist in a single Active Directory forest, the cumulative update matching the latest version of Exchange deployed should be used.  Setup will automatically run /PrepareDomain in the domain where /PrepareAD is executed.  Environments with multiple domains in the forest will need to run the cumulative update setup program using the /PrepareDomain parameter in all domains in the forest.  These steps will update the rights granted to Exchange Servers in the Active Directory to meet the new permissions scope.  More information on /PrepareAD and /PrepareDomain is available at this link.

The directory updates released today are fully compatible with all versions of Exchange Server regardless of cumulative update or update rollup version deployed and so these changes can be applied to any existing Exchange deployment by following the steps above.

Support for .NET Framework 4.8

The updates released today add support for .NET Framework 4.8.  The minimum .NET requirement remains 4.7.2 on Exchange Servers.  .NET 4.8 will be required with all updates released in December 2019 and later.

Authentication Policies Update

With the first cumulative update (CU1) for Exchange 2019 we shipped our initial implementation of disabling legacy authentication protocols on a per user basis.

In today’s second cumulative update we have now enhanced the feature to provide the ability to specify it as default authentication policy at Organization level.

We will be releasing an updated blog very soon providing more information about the feature and instructions on how to use it.  

Future support of Modern Authentication in on-premises Exchange

Over the past couple of years, you have seen us deliver Modern Authentication to Exchange when running a hybrid organization.  The usual follow-on question from a handful of customers has been, “When will modern authentication be supported in non-hybrid environments?”  Our response was typically something along the lines of, “We’re looking into it.”  While that statement was true and accurate, after much deliberation we have come to the decision that this capability in on-premises Exchange server will no longer be pursued.  Our investments in Modern Authentication will be restricted to those with hybrid deployments.  We know this will be a disappointment for some customers but we wanted to make certain you were aware of this change in strategy.

Controlled Connections to Public Folders in Outlook

As we announced towards the end of last year, we added support to Exchange Online to help admins have control over which users would see public folders in their Outlook clients.

We are including this functionality in Exchange Server 2019 Cumulative Update 2 and Exchange Server 2016 Cumulative Update 13, both released today.

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 KB981474 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 13 or 12; 2019 Cumulative Update 2 or 1.

For the latest information on Exchange Server and product announcements please see What's New in Exchange Server and Exchange Server Release Notes.  You can also find updated information on Exchange Server 2013 in What’s New in Exchange Server 2013, Release Notes and product documentation available on Docs.

Important:  To avoid a setup failure, it is necessary to install the Visual C++ 2012 runtime before installing the updates released today on Edge role if not already present.

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

The Exchange Team

47 Comments
Microsoft

Just wanted to post a quick note: we are aware of slight delay of downloads actually being available. We are working on this!

Occasional Visitor
glad to hear that.
Regular Visitor
Please, make CU2 for Exchange 2019 available at least on MSDN (Visual Studio Subscriptions) and/or Microsoft partner benefit downloads to give ISVs faster access to Exchange versions which are used by our customers soon. Please, not the same waiting game as with CU1.

Can you update the Exchange Server supportability matrix to show .NET 4.8 support for these updates:

 

https://docs.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-201...

 

Thanks!

Regular Visitor

Congrats and thanks for the release, still waiting for Exchange Server 2019 CU2 to show up in MPN of VLSC...

One other thing, the download link for the UM Language Packs for Exchange Server 2013 CU23 is pointing to the CU22 version of the UM Language Packs. The correct URL is https://www.microsoft.com/en-us/download/details.aspx?id=58394 (but only en-us is available at this moment).

Frequent Contributor

Same for the 2016 UM Language Packs, it's only the en-us available.

 

Occasional Visitor

I thought that the supported versions for hybrid deployments were N and N-1. But the article says that only Cumulative Update 23 is supported for the Exchange 2013. Does that mean that for Exchnage 2013, only the latest version is supported?

Thanks! :)

Microsoft

@Damian Scoles sure thing. Will take care of this.

 

Can you update the Exchange Server supportability matrix to show .NET 4.8 support for these updates:

 

https://docs.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-201....

 

Thanks!



 

Language packs and MSDN bits are on the way rest assured. 

Frequent Visitor
Why still no post on the "Defense in Depth" security updates for Exchange? This failed on my servers and left them in an unusable state and I know from posts elsewhere i'm not alone.

@TheVogon - we're not planning to do a post on those updates. We've also not heard of the issues you mentioned, so you really should call in to support so they can help. If your servers are in an unusable state I really hope you've already called support, this isn't the best place to resolve that. 

Frequent Visitor

Hello Exchange Team

 

Thanks for releasing quarterly updates. Exchange 2019 CU2 is still not available for download. Do you think you could fix this before weekend?

 

thanks again

New Contributor
I dont see CU2 in the VLSC yet. Any ETA?

We are checking into the download issues, sorry about that. I really do hope we'll resolve that today. 

Frequent Visitor

Good Friday everyone,

   Any news yet on the availability of Exchange 2019 CU2 yet? I have an Exchange 2019 server that needs to be built and am waiting for CU2 instead of CU1 and then updating.

 

Thanks

Ray

MSDN is live now. We're checking VLSC again.

First, thanks for updating the matrix page.  However I see that Exchange 2013 CU23 supports only .NET 4.8?  I think that is incorrect and should show that it supports .NET 4.7.2 and .NET 4.8 due to your statement that .NET 4.8 will not be required until December?  Maybe I am reading that wrong for Exchange 2013.

 

Next, I see Exchange 2019 CU2 is now available on MSDN.  However, no other versions are available for download?  I thought you were going to make at least one rev or two back allowed for downloading, but RTM and CU1 are no longer available.  Curious if that was a mistake or overlooked?  Or is this the new policy of only leaving the most current available?  Now mind you this is only on MSDN, I don't have access to VLSC to see if that is any different.

 

Thanks.

Frequent Visitor
Greg - why no post on the Defense in Depth update? Since when have updates pushed out as critical had zero explanation anywhere of what they actually do? Is the Defense in Depth update included in CU2? The DiD update fails on multiple systems and leaves it in a state where the exchange services no longer start, you cant reinstall the update or reinstall CU1. See details and how I fixed it here: https://eightwone.com/2019/06/12/security-updates-exchange-2013-2019-2010/ And as you can see from that page, i'm not the only one who had this issue.
Frequent Visitor
And as an article suggestion, I understand that .Net 4.8 includes major performance enhancements ported from .Net core. Some Exchange benchmarks would be interesting....
Microsoft

Damian, this will be fixed soon:

 

First, thanks for updating the matrix page.  However I see that Exchange 2013 CU23 supports only .NET 4.8?  I think that is incorrect and should show that it supports .NET 4.7.2 and .NET 4.8 due to your statement that .NET 4.8 will not be required until December?  Maybe I am reading that wrong for Exchange 2013.

@TheVogon there's nothing specific we want to say about that particular issue, other than we advise customers to install it. We don't usually explain security patched in detail, there's nothing different about this.

The patch is included in CU2.

Sometimes there are issues installing patches, that can happen. But I'll go back to saying that the best way to fix a serious issue that leaves your machine in that state is to call support. Blogs and comments aren't the best way to deal with service/server impacting issues - and all too often they are filled with bad, confusing and contradictory advice.

Greg

Senior Member

The calculator does not work if use mailboxes larger than 10 gigabytes in size.

Frequent Visitor

Good evening everyone,

     I'm not seeing CU2 on MSDN/Visual Studio, and heck I'm not seeing CU1 there anymore, was there this morning. CU2 doesn't seem to be on ActionPack either. CU1 is still there. Am I missing something????

 

Thanks

Ray

Microsoft

@vaclav_mech - Once a product reaches extended support, we only support the latest CU.  This was discussed in https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Exchange-Server-2013-Enters-Extended-Suppo....

New Contributor

When will EX2019 CU2 be available for download via VLSC, and why are the CUs not available publicly anymore in the first place?

Occasional Visitor

1) This article links to Visual Studio C++ 2012 runtime, but the KB article (https://support.microsoft.com/en-us/help/4489622/cumulative-update-23-for-exchange-server-2013) links to 2013.  I assume the KB takes precedent?

2) Other commenters referred to the .NET support table, which I didn't see linked anywhere, but I did find it: https://docs.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019

3) The KB article states: 

Cumulative Update 23 for Microsoft Exchange Server 2013 was released on June 18, 2019. This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues. These fixes will also be included in later cumulative updates for Exchange Server 2013.

This update also includes new daylight saving time (DST) updates for Exchange Server 2013. For more information about DST, see Daylight Saving Time Help and Support Center.

So, if we are up to date on the security updates, does that mean there's no compelling security benefit from this CU and this would only provide the non-security benefits?

Senior Member
Released: June 2019 Quarterly Exchange Updates was posted on the 18th of June. It is now the 25th. And 2019 CU2 is still not actually available on the VSLC. Perhaps you shouldn't make the announcement before all the download platforms are ready?
Occasional Visitor

Will there be next version of On premises Exchange released or it just the O365 in future. 

@Neil_Flanagan - the bits should be there, I've been told by others they are. Perhaps it's a replication thing, or results are being filtered?

 

@Ravikumar_Shankarappa - too early to talk about that. 

New Contributor
Still only CU1 for 2019 available in VLSC. Tried refreshing, etc.
Visitor

It is definitely not showing in VLSC for me, either. You can only select 'MultiLanguage' using either the download manager or web browser options. Doesn't matter what combination you try, still shows CU1 only.

Frequent Visitor

Still not on Action Pack, not seeing it on MSDN/Visual studio either. CU1 was on MSDN/Visual studio last week, now no Exchange.

Frequent Visitor

CU2 is still not available in VLSC and I even have a ticket that has been escalated and been open for over 6 days now. Grrr

Visitor

CU2 in VLSC is showing for me now.

Yup, sorry about the delay in getting the bits onto VLSC. The hamster was asleep, the wheel wasn't turning. We just woke it up. 

Frequent Visitor

Yep its finally there after a week from announcement. 

Microsoft
Frequent Visitor

I've given up on seeing it on Action Pack or Visual Studio. CU1 is on Action Pack and CU1 was on Visual Studio, now no Exchange whatsoever on Visual Studio. I opened a ticket a few days ago and got the run around, was given a phone number only to be told why are you calling here....

@RaySumperl as Kate Bush once said, Don't Give Up, your bits will one day come. And they should now be there. 

 

I really am sorry for the delay with the availability, we're doing our best to make sure we don't have a repeat next time round. 

Frequent Visitor

Greg,

THANK YOU! I am now downloading CU2. I'm sorry I was SO obnoxious.....

 

Ray

It's ok @RaySumperl , all is forgiven and it's our fault - we need to do a better job. Have fun with CU2. 

New Contributor
Any chance a dark mode OWA theme made it into this release? Its a shame its available to online but not on-prem.

@m49808 we have no plans to add that to on-prem, sorry. Online now uses React, we're not putting that on-prem. 

Microsoft

@ScriptMasterSkillet Answer to your questions:

 

1.  Yes the KB takes precedence.  We have a weird dance of both VC++2012/2013 runtimes being required.  We pre-req on the 2013 runtime in Exchange SETUP, but UCMA installs the 2012 runtime.

 

2.  Self explanatory you found the correct link.

 

3.  Under our Cumulative Update support policy during extended support, we will retire support for Cumulative Update 22 in the near future.  That means to get future updates for Exchange 2013, you will need to deploy the Cumulative Update 23.  If you have applied the security update for Cumulative Update 22, you have the same fixes that were deployed in Cumulative Update 23 with the exception of the AD permissions changes we included in Cumulative Update 23.  We cannot change AD permissions in a Security Update package because doing so requires SETUP /PrepareAD to be executed.

Occasional Visitor

Thank you, Brent.

Are there any additional CUs planned for Exchange 2013?  I thought the last one was billed as the last one, yet here we are.

Occasional Visitor

What are the SHA1/SHA256 hashes for ExchangeServer2016-x64-cu13.iso ?

 

https://support.microsoft.com/en-us/help/4471392/cumulative-update-12-for-exchange-server-2016 has the has SHA1 and SHA256 for ExchangeServer2016-x64-cu12.iso

 

But https://support.microsoft.com/en-us/help/4488406/cumulative-update-13-for-exchange-server-2016 does not have the hashes for ExchangeServer2016-x64-cu13.iso

Microsoft

@kevinds previously CU includes fixes for security issues. Therefore we’ve published the SHA hashes.