%3CLINGO-SUB%20id%3D%22lingo-sub-1976527%22%20slang%3D%22en-US%22%3EReleased%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1976527%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%3BIn%20a%20change%20to%20a%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fexchange-server-2016-and-the-end-of-mainstream-support%2Fba-p%2F1574110%22%20target%3D%22_blank%22%3Eprevious%20announcement%3C%2FA%3E%2C%20we%20now%20plan%20to%20release%20the%20final%20cumulative%20update%20for%20Exchange%20Server%202016%20in%20March%202021%2C%20which%20will%20include%20all%20fixes%20made%20for%20customer%20reported%20and%20accepted%20issues%20received%20before%20the%20end%20of%20mainstream%20support.%20%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--1180784909%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%20id%3D%22toc-hId--1179772890%22%3EOWA%20Cannot%20Download%20Attachment%3C%2FH2%3E%0A%3CP%3EThis%20update%20addresses%20a%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4588297%2Fattachments-not-downloaded-or-previewed-from-owa%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ecustomer%20reported%20issue%3C%2FA%3E%20which%20meant%20that%20a%20user%20was%20unable%20to%20preview%20or%20download%20an%20attachment%20in%20a%20mailbox%20they%20had%20access%20to%20when%20they%20had%20signed%20into%20it%20using%20OWA%E2%80%99s%20%E2%80%9Copen%20another%20mailbox%E2%80%9D%20feature.%20When%20logging%20in%20directly%20to%20the%20mailbox%20there%20was%20no%20issue.%20This%20update%20resolves%20this%20issue%20for%20both%20Exchange%20Server%202016%20and%20Exchange%20Server%202019.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1306727924%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%20id%3D%22toc-hId-1307739943%22%3EServer%20Assisted%20Search%3C%2FH2%3E%0A%3CP%3EThis%20update%20resolves%20an%20Exchange%20Server%202019%20issue%20which%20meant%20that%20a%20search%20using%20Outlook%20in%20cached%20mode%20returned%20a%20maximum%20of%20175%20results.%20This%20update%20will%20ensure%20the%20search%20response%20is%20complete%2C%20or%20to%20a%20maximum%20of%201000%20results.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--500726539%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%20id%3D%22toc-hId--499714520%22%3ENew-MoveRequest%20Not%20Logged%20in%20Audit%20Logs%3C%2FH2%3E%0A%3CP%3EThis%20update%20resolves%20an%20issue%20which%20meant%20resulted%20in%20New%2FResume%2FRemove-MoveRequest%20actions%20by%20an%20admin%20not%20being%20logged%20by%20the%20admin%20audit%20logging%20agent.%20Update-MoveRequest%20was%20being%20correctly%20logged.%20This%20update%20resolves%20this%20for%20both%20Exchange%20Server%202016%20and%20Exchange%20Server%202019%2C%20to%20ensure%20all%20*-MoveRequest%20requests%20are%20properly%20logged.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1986786294%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%22%20id%3D%22toc-hId-1987798313%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%208%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4588885%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB4588885%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%20noreferrer%22%3EVLSC%20Download%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202016%20Cumulative%20Update%2019%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4588884%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB4588884%3C%2FA%3E)%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3D2ef459a6-c8a5-417f-89a8-c8afa9ea00dd%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3D1a9b78ea-a4cd-44c1-a777-8df0f1330215%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EUM%20Lang%20Packs%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThese%20updates%20contain%20schema%20and%20directory%20changes%20and%20so%20require%20you%20prepare%20AD%20and%20all%20domains.%20You%20can%20find%20more%20information%20on%20that%20process%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-179331831%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%22%20id%3D%22toc-hId-180343850%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%20noreferrer%22%3Ehere%3C%2FA%3E%20to%20adjust%20the%20settings.%3C%2FP%3E%0A%3CP%3EAdditionally%2C%20a%20reminder%20that%20if%20you%20plan%20to%20install%20any%20Cumulative%20Update%20using%20the%20unattended%20option%20with%20either%20PowerShell%20or%20Command%20Prompt%2C%20make%20sure%20you%20specify%20either%20the%20full%20path%20to%20the%20setup.exe%20file%20or%20use%20a%20%E2%80%9C.%E2%80%9D%20in%20front%20of%20the%20command%20if%20you%20are%20running%20it%20directly%20from%20directory%20containing%20the%20update.%20If%20you%20do%20not%20the%20Exchange%20Server%20Setup%20program%20starts%20and%20may%20indicate%20that%20it%20completed%20successfully.%20Read%20more%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Ftroubleshoot%2Fsetup%2Fex2019-setup-does-not-run-correctly-started-powershell%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%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%2019%20or%2018%3B%202019%20Cumulative%20Update%208%20or%207.%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%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%20noreferrer%22%3EExchange%20Server%20Release%20Notes%3C%2FA%3E.%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-1976527%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.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1976527%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202019%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1992632%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1992632%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%2C%20do%20you%20have%20the%20new%20Forest%20and%20domain%20Range%20Upper%20and%20Object%20version%20after%20executing%20the%20%2FprepareAD%20and%20%2Fprepareall%20domains%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20exchange%202016%20CU18%20the%20object%20were%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BExchange%20version%20Forest%20range%20Upper%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BDomain%20Object%20version%26nbsp%3B%20%26nbsp%3B%20Object%20version%3C%2FP%3E%3CP%3E%3CSTRONG%3E2016%20CU18%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2015332%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%2016218%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%2013238%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EThanks%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1992837%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1992837%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%20went%20smoothly%20yesterday%2C%20on%20two%20servers%20in%20a%20DAG.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20got%20an%20issue%26nbsp%3Bin%20Outlook%20Web%20Access%20with%202016%20CU19%20now%20though%2C%20where%20instead%20of%20previewing%20PDF%20attachments%2C%20it%20will%20download%20them%20and%20just%20show%20a%20spinning%20blue%20circle%20of%20dots%20in%20the%20preview%20pane.%20Previews%20of%20Excel%20and%20Word%20documents%20are%20working%20well%20and%20rendering%20through%20our%20Office%20Online%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20can%20someone%20confirm%20this%20behaviour%20when%20previewing%20pdfs%20in%202016%20CU19.%20Thanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F346709%22%20target%3D%22_blank%22%3E%40benoitrando%3C%2FA%3E.%20Check%20versions%20at%20the%20bottom%20of%20this%20webpage%2C%20which%20have%20already%20been%20updated%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Feightwone.com%2Freferences%2Fschema-versions%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Feightwone.com%2Freferences%2Fschema-versions%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EI've%20just%20checked%202016%20CU19%2C%20and%20my%20versions%20match%3A-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%20border%3D%221%22%3E%3CTBODY%3E%3CTR%3E%3CTD%3EExchange%20Version%3C%2FTD%3E%3CTD%3EForest%20Range%20Upper%3C%2FTD%3E%3CTD%3EForest%20Object%20Version%3C%2FTD%3E%3CTD%3EDomain%20Object%20Version%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E2016%20CU19%3C%2FTD%3E%3CTD%3E15333%3C%2FTD%3E%3CTD%3E16219%3C%2FTD%3E%3CTD%3E13239%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1993099%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1993099%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F346709%22%20target%3D%22_blank%22%3E%40benoitrando%3C%2FA%3E%26nbsp%3Bwe%20document%20the%20information%20for%20each%20release%20here%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2016%23exchange-active-directory-versions%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EPrepare%20Active%20Directory%20and%20domains%20for%20Exchange%20Server%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1994224%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1994224%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F848816%22%20target%3D%22_blank%22%3E%40keen120%3C%2FA%3E%26nbsp%3BCVE-2020-16969%20was%20fixed%20with%20Exchange%202016%20build%26nbsp%3B%3CSTRONG%3E2044.7%3C%2FSTRONG%3E%20and%20%3CSTRONG%3E2106.3%3C%2FSTRONG%3E%20and%20for%20Exchange%202019%20with%20build%26nbsp%3B%3CSTRONG%3E659.7%3C%2FSTRONG%3E%20and%20%3CSTRONG%3E721.3%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExchange%202016%20CU19%20is%20build%3A%26nbsp%3B%3CSPAN%3E15.1.%3CU%3E%3CSTRONG%3E2176.2%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EExchange%202019%20CU8%20is%20build%3A%26nbsp%3B%3CSPAN%3E15.2.%3CU%3E%3CSTRONG%3E792.3%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20here%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fnew-features%2Fbuild-numbers-and-release-dates%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Server%20build%20numbers%20and%20release%20dates%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKB4581424%20is%20not%20applicable%20for%20Exchange%202019%20CU8%20%2F%20Exchange%202016%20CU19.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1995327%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1995327%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%3CSTRONG%3EHello%20Microsoft%2C%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHow%20can%20I%20migrate%20on-premises%20public%20folders%20from%20Exchange%202016%2C%20cross-forest%2C%20to%20another%20Exchange%202016%20org%20%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1996586%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1996586%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903579%22%20target%3D%22_blank%22%3E%40aleach%3C%2FA%3E%26nbsp%3Bthanks%20for%20bringing%20this%20up%20to%20our%20attention.%20We'll%20have%20a%20look%20at%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1996628%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1996628%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20updates%20on%20removal%20on%20Exchange%20management-only%20server%20(last%20Exchange%20server)%2C%20after%20migrating%20to%20Exchange%20Online%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2FRasmus%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1997059%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1997059%22%20slang%3D%22en-US%22%3E%3CP%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%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903579%22%20target%3D%22_blank%22%3E%40aleach%3C%2FA%3E%26nbsp%3Bsame%20issue%20after%20applying%20CU19%20to%20exchange%202016%20%3A%20OWA%20(with%20Edge%20Chromium)%20wants%20to%20download%20PDF%20attachments%20and%20no%20more%20preview%20through%20Office%20Online%20Server.%20Preview%20of%20.docx%2C%20.xlsx%20still%20works.%3C%2FP%3E%3CP%3Eif%20anyone%20has%20a%20clue...%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1993476%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1993476%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20about%26nbsp%3B%3CSPAN%3EKB4581424%3F%20Is%20that%20included%20in%202016%20CU19%20and%202019%20CU8%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2004541%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2004541%22%20slang%3D%22en-US%22%3E%3CP%3Eplease%20delete%20this%20post%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2007310%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2007310%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%3CSTRONG%3EHello%20Microsoft%2C%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHow%20can%20I%20migrate%20on-premises%20public%20folders%20from%20Exchange%202016%2C%20cross-forest%2C%20to%20another%20Exchange%202016%20org%20%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2008369%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2008369%22%20slang%3D%22en-US%22%3E%3CP%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%26nbsp%3B%20Update%20Exchange%202019%20to%20CU8%2C%20we%20experience%20the%20same%20behavior%20as%20reported%20in%20the%20post%20above%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903579%22%20target%3D%22_blank%22%3E%40aleach%3C%2FA%3E%2C%3C%2FP%3E%3CDIV%20class%3D%22user-mention-tag%22%3E%3CDIV%20class%3D%22user-mention-tag%22%3E%3CP%20class%3D%22user-mention-tag-label%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F216768%22%20target%3D%22_blank%22%3E%40Dominique%20SCHMIT%3C%2FA%3E%26nbsp%3B%20and%20others%3CSPAN%3E.%26nbsp%3BPDF%20can%20no%20longer%20be%20previewed%20and%20are%20downloaded%20instead.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2009958%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2009958%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F537560%22%20target%3D%22_blank%22%3E%40JSho03%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F909015%22%20target%3D%22_blank%22%3E%40Chris_Cyril%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F216768%22%20target%3D%22_blank%22%3E%40Dominique%20SCHMIT%3C%2FA%3E%26nbsp%3B%20Thanks%20all%20for%20confirming%20this%20is%20a%20common%20regression%2C%20and%20isn't%20unique%20to%20my%20setup.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%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%26nbsp%3BHopefully%20the%20bug%20has%20been%26nbsp%3Breported%20and%20a%20fix%20will%20be%20released%20for%20an%20upcoming%20Patch%20Tuesday%3F%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2009986%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2009986%22%20slang%3D%22en-US%22%3E%3CP%3EI%20experience%20the%20same%20behaviour%20which%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903579%22%20target%3D%22_blank%22%3E%40aleach%3C%2FA%3E%26nbsp%3Bcommented.%20The%20bug%20appears%20in%20the%20first%20opened%20mailbox%20and%20in%20the%20additional%20one%20too.%20As%20far%20as%20i%20can%20see%20it's%20only%20happens%20with%20.pdf%20attachments.%20Other%20previewable%20attachments%20(e.g.%20.png%20files)%20aren't%20affected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdited%20for%20clarification%3A%20i%20installed%20Exchange%202019%20CU8%20in%20our%20lab%20environment%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2010359%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2010359%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20everybody%20for%20reporting.%20Engineering%20is%20currently%20investigating%20this%20behavior.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2014486%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2014486%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%3CSTRONG%3EHello%20Microsoft%2C%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHow%20can%20I%20migrate%20on-premises%20public%20folders%20from%20Exchange%202016%2C%20cross-forest%2C%20to%20another%20Exchange%202016%20org%20%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2018084%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2018084%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EHello%20Lukas%2C%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eafter%20installing%20the%20CU8%20for%202019%2C%20I%20can%20confirm%20that%20there%20are%20many%20errors%20in%20the%20application%20log%20every%201%20hour.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EThese%20are%3A%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3E-%20%22ASP.NET%204.0.30319.0%22%20Evend%20ID%201309%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3E-%20%22MSExchange%20Front%20End%20HTTP%20Proxy%22%20Event%20ID%201003%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3E-%20%22MSExchange%20Common%22%20Event%20ID%204999%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EAll%20are%20related%20to%20%22DuplicateKeyException%22%2C%20%22TimeoutCache.DuplicateKeyException%22%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3EMore%20information%20at%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.reddit.com%2Fr%2Fexchangeserver%2Fcomments%2Fkhhfa1%2Fpossible_2019_cu8_bug%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fwww.reddit.com%2Fr%2Fexchangeserver%2Fcomments%2Fkhhfa1%2Fpossible_2019_cu8_bug%2F%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3EBest%20regards%20Marco%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2018504%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2018504%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668274%22%20target%3D%22_blank%22%3E%40Marco%3C%2FA%3E%26nbsp%3Bthanks%20for%20reporting.%20We%E2%80%99ll%20have%20a%20look%20at%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2019208%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2019208%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Equick%20one%20-%20does%20the%20schema%20update%20for%20CU8%20also%20qualify%20us%20to%20apply%20CU19%20in%20our%202016%20environment%3F%3C%2FP%3E%3CP%3EWe%20plan%20to%20introduce%202019%20now%2C%20and%20the%20question%20is%20do%20we%20only%20need%20to%20run%20%2Fprepareschema%20%2FprepareAD%20off%20the%202019%20sources%20or%20also%20from%202016%20to%20apply%20the%20CU19%20to%20our%20existing%202016%20environment%3C%2FP%3E%3CP%3ESchema%20modifications%20seem%20to%20be%20the%20same%20but%20does%20the%20setup%20process%20identify%20this%20prereq%20as%20fulfilled%20then%20after%20running%20from%202019%20CU8%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20for%20confirming%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ergds%3C%2FP%3E%3CP%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2021965%22%20slang%3D%22zh-CN%22%3EReply%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2021965%22%20slang%3D%22zh-CN%22%3E%3CP%3ERepair%20or%20not%20this%20on%20exchange%202016%E3%80%82%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fzh-cn%2Fexchange%2Ftroubleshoot%2Fcompliance%2Fsearch-adminauditlog-mailboxauditlog-return-no-result%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fzh-cn%2Fexchange%2Ftroubleshoot%2Fcompliance%2Fsearch-adminauditlog-mailboxauditlog-return-no-result%E3%80%82%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2023884%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2023884%22%20slang%3D%22en-US%22%3E%3CP%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%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903579%22%20target%3D%22_blank%22%3E%40aleach%3C%2FA%3E%3CSPAN%3E%26nbsp%3BI%20have%20experienced%20the%20same%20issue.%20we%20are%20unable%20to%20preview%20the%20PDF%2C%20spinning%20is%20going%20on.%20after%20the%20CU19%20update%20in%20DAG.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2044427%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2044427%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F914776%22%20target%3D%22_blank%22%3E%40Rana_Shahzad%3C%2FA%3E%26nbsp%3Bplease%20track%20the%20following%20support%20article%20for%20the%20.pdf%20preview%20issue.%20Microsoft%20is%20still%20researching%20this%20problem.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4583558%2Fpdf-preview-function-in-owa-leads-to-download-action-unexpectedly%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4583558%2Fpdf-preview-function-in-owa-leads-to-download-action-unexpectedly%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2045130%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2045130%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20also%20running%20into%20the%20same%20issue%20as%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668274%22%20target%3D%22_blank%22%3E%40Marco%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EThese%20are%3A%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3E-%20%22ASP.NET%204.0.30319.0%22%20Evend%20ID%201309%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3E-%20%22MSExchange%20Front%20End%20HTTP%20Proxy%22%20Event%20ID%201003%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3E-%20%22MSExchange%20Common%22%20Event%20ID%204999%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3Eseem%20like%20our%20are%20all%20related%20to%20the%20MAPI%20protocol..%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2047851%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2047851%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20also%20the%20same%20issues%20as%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668274%22%20target%3D%22_blank%22%3E%40Marco%3C%2FA%3E%3CBR%20%2F%3EEver%20since%20we%20updated%20to%202019%20CU8.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20errors%20appear%20in%20Exchange%20Server%20Application%20log%20when%20users%20connect%20to%20the%20server%20with%20their%20Outlook%20desktop%20apps.%3C%2FP%3E%3CP%3EASP.NET%204.0.30319.0%22%20Evend%20ID%201309%3CBR%20%2F%3E%22MSExchange%20Front%20End%20HTTP%20Proxy%22%20Event%20ID%201003%3CBR%20%2F%3E%22MSExchange%20Common%22%20Event%20ID%204999%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ein%20MAPI%20and%20Autodiscover%20protocol.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2056253%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2056253%22%20slang%3D%22en-US%22%3E%3CP%3E%2B1%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668274%22%20target%3D%22_blank%22%3E%40Marco%3C%2FA%3E%26nbsp%3B%26amp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F924377%22%20target%3D%22_blank%22%3E%40harminckilenc%3C%2FA%3E%26nbsp%3Babout%20errors%3C%2FP%3E%3CP%3E%3CSPAN%3EASP.NET%204.0.30319.0%22%20Evend%20ID%201309%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%22MSExchange%20Front%20End%20HTTP%20Proxy%22%20Event%20ID%201003%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%22MSExchange%20Common%22%20Event%20ID%204999%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1994280%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1994280%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20morning%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20on%20my%20second%20day%20with%20Office%20365%20technical%20support%20trying%20to%20understand%20when%20they%20would%20stop%20supporting%20Exchange%202016%20in%20a%20hybrid%20configuration.%26nbsp%3B%20When%20would%20they%20stop%20assisting%20with%20migrations%20or%20Exchange%202016%20related%20issues.%26nbsp%3B%20So%20far%2C%20I%20have%20links%20to%20multiple%20EOL%20articles%2C%20but%20I%20don't%20have%20clarity.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMainstream%20end%20date%20was%20October%2013%2C%202020%2C%20but%20that%20has%20extend.%3C%2FP%3E%3CP%3ECumulative%20Update%2019%20released%20December%2015%2C%202020.%3C%2FP%3E%3CP%3ECumulative%20Update%2020%20should%20come%20out%20in%20March%202021%2C%20with%20no%20further%20Cumulative%20Updates.%3C%2FP%3E%3CP%3EExtended%20End%20is%20October%2014%2C%202025.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EO365%20support%20assists%20with%20issue%20on%20current%20version%20released%20minus%201.%26nbsp%3B%20CU%2019%20and%20CU%2018%20currently.%26nbsp%3B%20Assuming%20CU%2020%20is%20released%20in%20March%202021.%26nbsp%3B%20Does%20O365%20tech%20support%20provide%20support%20for%20Exchange%202016%20CU%2019%20and%2020%20through%20October%2014%2C%202025%3F%26nbsp%3B%20When%20does%20O365%20tech%20support%20stop%20supporting%20Exchange%202016%20as%20of%20today%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20pointers%20or%20information%20provided%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EScott%20Stancil%3C%2FP%3E%3CP%3EColumbia%20Southern%20University%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2071467%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2071467%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F927451%22%20target%3D%22_blank%22%3E%40Sasha_Odarchuk%3C%2FA%3E%26nbsp%3BMicrosoft%20is%20researching%20this%20problem%20and%20will%20post%20more%20information%20in%20this%20article%20when%20it%20becomes%20available.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F4602646%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F4602646%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2007988%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2007988%22%20slang%3D%22en-US%22%3E%3CP%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%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903579%22%20target%3D%22_blank%22%3E%40aleach%3C%2FA%3E%20We%20don't%20run%20an%20Office%20Online%20Server%2C%20and%20I%20can%20confirm%20the%20same%20issue%20-%20we%20can%20no%20longer%20preview%20PDF%20files%2C%20but%20can%20download%20them.%20Preview%20just%20is%20blank.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2083250%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2083250%22%20slang%3D%22en-US%22%3E%3CP%3E%40Sasha%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F927451%22%20target%3D%22_blank%22%3EOdarchuk%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20update%20on%20this..%20I%20hope%20there%20is%20a%20solution%20soon%2C%20maybe%20a%20hotfix%3F%3C%2FP%3E%3CP%3ENot%20only%20is%20this%20annoying%20as%20it%20appears%20that%20when%20the%20MAPI%20type%20event%20happens%20for%20a%20user..%20they%20are%20prompted%20to%20login%20again%20shortly%20after%20the%20event.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20we%20try%20to%20teach%20our%20users%20to%20avoid%20login%20windows%20when%20dealing%20with%20email%20as%20a%20security%20conscious%20effort..%20but%20now%20we%20are%20having%20them%20identify%20this%20login%20box%20as%20%22safe%22%20but%20all%20other%20are%20bad.%20This%20leads%20to%20confusion.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2086873%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202020%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2086873%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F4602646%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F4602646%3C%2FA%3E%26nbsp%3Bnow%20seems%20to%20have%20disappeared%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. In a change to a previous announcement, we now plan to release the final cumulative update for Exchange Server 2016 in March 2021, which will include all fixes made for customer reported and accepted issues received before the end of mainstream support.  

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

OWA Cannot Download Attachment

This update addresses a customer reported issue which meant that a user was unable to preview or download an attachment in a mailbox they had access to when they had signed into it using OWA’s “open another mailbox” feature. When logging in directly to the mailbox there was no issue. This update resolves this issue for both Exchange Server 2016 and Exchange Server 2019.

Server Assisted Search

This update resolves an Exchange Server 2019 issue which meant that a search using Outlook in cached mode returned a maximum of 175 results. This update will ensure the search response is complete, or to a maximum of 1000 results.

New-MoveRequest Not Logged in Audit Logs

This update resolves an issue which meant resulted in New/Resume/Remove-MoveRequest actions by an admin not being logged by the admin audit logging agent. Update-MoveRequest was being correctly logged. This update resolves this for both Exchange Server 2016 and Exchange Server 2019, to ensure all *-MoveRequest requests are properly logged.

Release Details

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

These updates contain schema and directory changes and so require you prepare AD and all domains. You can find more information on that process here.

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.

Additionally, a reminder that if you plan to install any Cumulative Update using the unattended option with either PowerShell or Command Prompt, make sure you specify either the full path to the setup.exe file or use a “.” in front of the command if you are running it directly from directory containing the update. If you do not the Exchange Server Setup program starts and may indicate that it completed successfully. Read more here.

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 19 or 18; 2019 Cumulative Update 8 or 7.

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

33 Comments
New Contributor

Hello , do you have the new Forest and domain Range Upper and Object version after executing the /prepareAD and /prepareall domains

 

For exchange 2016 CU18 the object were

 

 Exchange version Forest range Upper       Domain Object version    Object version

2016 CU18          15332                            16218                              13238

 

Thanks

Regular Visitor

Update went smoothly yesterday, on two servers in a DAG.

 

I've got an issue in Outlook Web Access with 2016 CU19 now though, where instead of previewing PDF attachments, it will download them and just show a spinning blue circle of dots in the preview pane. Previews of Excel and Word documents are working well and rendering through our Office Online server.

 

Please can someone confirm this behaviour when previewing pdfs in 2016 CU19. Thanks.

 

PS. @benoitrando. Check versions at the bottom of this webpage, which have already been updated: https://eightwone.com/references/schema-versions/

I've just checked 2016 CU19, and my versions match:-

 

Exchange VersionForest Range UpperForest Object VersionDomain Object Version
2016 CU19153331621913239

 

 

Microsoft

@benoitrando we document the information for each release here:

 

Prepare Active Directory and domains for Exchange Server 

 

 

Occasional Visitor

What about KB4581424? Is that included in 2016 CU19 and 2019 CU8?

Microsoft

@keen120 CVE-2020-16969 was fixed with Exchange 2016 build 2044.7 and 2106.3 and for Exchange 2019 with build 659.7 and 721.3.

 

Exchange 2016 CU19 is build: 15.1.2176.2

Exchange 2019 CU8 is build: 15.2.792.3

 

From here:

Exchange Server build numbers and release dates | Microsoft Docs

 

KB4581424 is not applicable for Exchange 2019 CU8 / Exchange 2016 CU19.

Senior Member

Good morning,

 

I am on my second day with Office 365 technical support trying to understand when they would stop supporting Exchange 2016 in a hybrid configuration.  When would they stop assisting with migrations or Exchange 2016 related issues.  So far, I have links to multiple EOL articles, but I don't have clarity.

 

Mainstream end date was October 13, 2020, but that has extend.

Cumulative Update 19 released December 15, 2020.

Cumulative Update 20 should come out in March 2021, with no further Cumulative Updates.

Extended End is October 14, 2025.

 

O365 support assists with issue on current version released minus 1.  CU 19 and CU 18 currently.  Assuming CU 20 is released in March 2021.  Does O365 tech support provide support for Exchange 2016 CU 19 and 20 through October 14, 2025?  When does O365 tech support stop supporting Exchange 2016 as of today?

 

Any pointers or information provided would be greatly appreciated.

 

Scott Stancil

Columbia Southern University

New Contributor

Hello Microsoft,

 

How can I migrate on-premises public folders from Exchange 2016, cross-forest, to another Exchange 2016 org ? 

Microsoft

@aleach thanks for bringing this up to our attention. We'll have a look at this.

Senior Member

Hello,

 

Any updates on removal on Exchange management-only server (last Exchange server), after migrating to Exchange Online ?

 

/Rasmus

Frequent Visitor

@Lukas Sassl @aleach same issue after applying CU19 to exchange 2016 : OWA (with Edge Chromium) wants to download PDF attachments and no more preview through Office Online Server. Preview of .docx, .xlsx still works.

if anyone has a clue...

Regards

Occasional Contributor

please delete this post

New Contributor

Hello Microsoft,

 

How can I migrate on-premises public folders from Exchange 2016, cross-forest, to another Exchange 2016 org ? 

Frequent Visitor

@Lukas Sassl @aleach We don't run an Office Online Server, and I can confirm the same issue - we can no longer preview PDF files, but can download them. Preview just is blank.

Occasional Visitor

@Lukas Sassl  Update Exchange 2019 to CU8, we experience the same behavior as reported in the post above by @aleach,

@Dominique SCHMIT  and others. PDF can no longer be previewed and are downloaded instead. 

Regular Visitor

@JSho03  @Chris_Cyril @Dominique SCHMIT  Thanks all for confirming this is a common regression, and isn't unique to my setup.

 

@Lukas Sassl Hopefully the bug has been reported and a fix will be released for an upcoming Patch Tuesday? :smile:

Occasional Visitor

I experience the same behaviour which @aleach commented. The bug appears in the first opened mailbox and in the additional one too. As far as i can see it's only happens with .pdf attachments. Other previewable attachments (e.g. .png files) aren't affected.

 

Edited for clarification: i installed Exchange 2019 CU8 in our lab environment

Microsoft

Thanks everybody for reporting. Engineering is currently investigating this behavior.

New Contributor

Hello Microsoft,

 

How can I migrate on-premises public folders from Exchange 2016, cross-forest, to another Exchange 2016 org ? 

Senior Member

Hello Lukas,

after installing the CU8 for 2019, I can confirm that there are many errors in the application log every 1 hour.

 

These are:

- "ASP.NET 4.0.30319.0" Evend ID 1309

- "MSExchange Front End HTTP Proxy" Event ID 1003

- "MSExchange Common" Event ID 4999

 

All are related to "DuplicateKeyException", "TimeoutCache.DuplicateKeyException"

 

More information at: https://www.reddit.com/r/exchangeserver/comments/khhfa1/possible_2019_cu8_bug/

 

Best regards Marco

Microsoft

@Marco thanks for reporting. We’ll have a look at it.

Occasional Visitor

Thanks guys,

 

quick one - does the schema update for CU8 also qualify us to apply CU19 in our 2016 environment?

We plan to introduce 2019 now, and the question is do we only need to run /prepareschema /prepareAD off the 2019 sources or also from 2016 to apply the CU19 to our existing 2016 environment

Schema modifications seem to be the same but does the setup process identify this prereq as fulfilled then after running from 2019 CU8?

 

thanks for confirming

 

rgds

Martin

Occasional Visitor
Occasional Visitor

@Lukas Sassl @aleach I have experienced the same issue. we are unable to preview the PDF, spinning is going on. after the CU19 update in DAG. 

Microsoft

@Rana_Shahzad please track the following support article for the .pdf preview issue. Microsoft is still researching this problem.

 

https://support.microsoft.com/en-us/help/4583558/pdf-preview-function-in-owa-leads-to-download-actio...

Occasional Visitor

 

We are also running into the same issue as @Marco

 

These are:

- "ASP.NET 4.0.30319.0" Evend ID 1309

- "MSExchange Front End HTTP Proxy" Event ID 1003

- "MSExchange Common" Event ID 4999

 

seem like our are all related to the MAPI protocol..

Occasional Visitor

We have also the same issues as @Marco
Ever since we updated to 2019 CU8.

 

These errors appear in Exchange Server Application log when users connect to the server with their Outlook desktop apps.

ASP.NET 4.0.30319.0" Evend ID 1309
"MSExchange Front End HTTP Proxy" Event ID 1003
"MSExchange Common" Event ID 4999

 

in MAPI and Autodiscover protocol.

Occasional Visitor

+1 to @Marco & @harminckilenc about errors

ASP.NET 4.0.30319.0" Evend ID 1309
"MSExchange Front End HTTP Proxy" Event ID 1003
"MSExchange Common" Event ID 4999

Microsoft

@Sasha_Odarchuk Microsoft is researching this problem and will post more information in this article when it becomes available.

 

https://support.microsoft.com/en-us/topic/event-ids-1003-1309-and-4999-are-logged-after-installing-e...

Occasional Visitor

@Lukas Sassl

 

Thanks for the update on this.. I hope there is a solution soon, maybe a hotfix?

Not only is this annoying as it appears that when the MAPI type event happens for a user.. they are prompted to login again shortly after the event.

 

Also we try to teach our users to avoid login windows when dealing with email as a security conscious effort.. but now we are having them identify this login box as "safe" but all other are bad. This leads to confusion.

Senior Member

https://support.microsoft.com/help/4602646 now seems to have disappeared

Occasional Visitor

+1 to @Sasha_Odarchuk & @Marco & @harminckilenc about errors

ASP.NET 4.0.30319.0" Evend ID 1309
"MSExchange Front End HTTP Proxy" Event ID 1003
"MSExchange Common" Event ID 4999

Occasional Visitor

 

@Neil_Flanagan

 

I hope they are updating the KB Article with a fix.

 

Microsoft