Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1070411%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1070411%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20guys%2C%20just%20a%20hint%20the%20KB%20is%20still%20showing%20.NET%204.72%20as%20a%20prereq%20while%20it%20should%20be%204.8%20by%20reading%20this%20Blog%20post%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1070686%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1070686%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3Bhas%20released%20update%20about%20disk%20capacity%20that%20which%20i%20needed.%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071638%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071638%22%20slang%3D%22en-US%22%3EWow%2C%20Really%20amazing%20%3CA%20href%3D%22https%3A%2F%2Flieneticjaya.com%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%22%3Ehttps%3A%2F%2Flieneticjaya.com%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1072386%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072386%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356159%22%20target%3D%22_blank%22%3E%40Martin_Aigner%3C%2FA%3E%20good%20catch%20Martin.%20All%20fixed%20now.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1072926%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072926%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20update%20without%20DKIM%20and%20DMARC%20support%20on-premises.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1074479%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1074479%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20updated%20my%20test%20exchange%20server%20from%20CU14%20to%20CU15%20.%20No%20issue%20for%20the%20exchange%20mailbox%20and%20cas%20server%20but%20big%20issues%20on%20the%20edge%20exchange%20server%20.%3C%2FP%3E%3CP%3EI%20raised%20a%20ticket%20to%20the%20premier%20support%3C%2FP%3E%3CP%3EIt's%20failing%20at%20step%2010%20of%2012%20%3A%20Edge%20Transport%20Role%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5B12%2F19%2F2019%2010%3A34%3A11.0256%5D%20%5B2%5D%20%5BWARNING%5D%20The%20performance%20counter%20definition%20file%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CBin%5CPerf%5CAMD64%5CItemAssistantPerfCounters.xml%20could%20not%20be%20found.%3CBR%20%2F%3EParameter%20name%3A%20DefinitionFileName%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0256%5D%20%5B2%5D%20The%20performance%20counter%20definition%20file%20is%20invalid.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0256%5D%20%5B2%5D%20%5BWARNING%5D%20The%20performance%20counter%20definition%20file%20is%20invalid.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0256%5D%20%5B2%5D%20%5BWARNING%5D%20The%20performance%20counter%20definition%20file%20is%20invalid.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B2%5D%20Ending%20processing%20new-perfcounters%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B1%5D%20The%20following%201%20error(s)%20occurred%20during%20task%20execution%3A%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B1%5D%200.%20ErrorRecord%3A%20The%20performance%20counter%20definition%20file%20is%20invalid.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B1%5D%20The%20previous%20errors%20were%20generated%20by%20a%20non-critical%20task%20and%20will%20be%20ignored.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B1%5D%20Setup%20will%20continue%20processing%20component%20tasks...%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B1%5D%20Processing%20component%20'ADAM%20Configuration'%20(Configuring%20the%20local%20AD%20LDS%20instance.).%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B1%5D%20Executing%3A%3CBR%20%2F%3Einstall-AdamSchema%20-LdapFileName%20(%24roleInstallPath%20%2B%20%22%5CSetup%5CData%5Cschemaadam.ldf%22)%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B2%5D%20Active%20Directory%20session%20settings%20for%20'install-AdamSchema'%20are%3A%20View%20Entire%20Forest%3A%20'True'%2C%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B2%5D%20User%20specified%20parameters%3A%20-LdapFileName%3A'C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5C%5CSetup%5CData%5Cschemaadam.ldf'%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B2%5D%20Beginning%20processing%20install-AdamSchema%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A11.0272%5D%20%5B2%5D%20Running%20%26lt%3B%26gt%3B%20with%20arguments%20%26lt%3B-i%20-f%20%22C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5C%5CSetup%5CData%5Cschemaadam.ldf%22%20-s%20localhost%3A50389%20-j%20%22C%3A%5CUsers%5Cedgetest%5CAppData%5CLocal%5CTemp%5C1f15ef97-9aaa-4fcc-a23a-415df29873f5%22%20-c%20%22%3CSCHEMACONTAINERDN%3E%22%20%22%23schemaNamingContext%22%26gt%3B.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B2%5D%20Process%20ldifde.exe%20has%20finished%20with%20exit%20code%208224.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B2%5D%20%5BERROR%5D%20The%20AD%20LDS%20schema%20import%20process%20ldifde.exe%20failed%20with%20error%20code%208224.%20No%20schema%20has%20been%20imported%20into%20AD%20LDS.%20View%20the%20Setup%20logs%20for%20more%20information.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B2%5D%20%5BERROR%5D%20The%20AD%20LDS%20schema%20import%20process%20ldifde.exe%20failed%20with%20error%20code%208224.%20No%20schema%20has%20been%20imported%20into%20AD%20LDS.%20View%20the%20Setup%20logs%20for%20more%20information.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B2%5D%20Ending%20processing%20install-AdamSchema%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%20The%20following%201%20error(s)%20occurred%20during%20task%20execution%3A%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%200.%20ErrorRecord%3A%20The%20AD%20LDS%20schema%20import%20process%20ldifde.exe%20failed%20with%20error%20code%208224.%20No%20schema%20has%20been%20imported%20into%20AD%20LDS.%20View%20the%20Setup%20logs%20for%20more%20information.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%200.%20ErrorRecord%3A%20Microsoft.Exchange.Management.Edge.SetupTasks.AdamSchemaImportProcessFailureException%3A%20The%20AD%20LDS%20schema%20import%20process%20ldifde.exe%20failed%20with%20error%20code%208224.%20No%20schema%20has%20been%20imported%20into%20AD%20LDS.%20View%20the%20Setup%20logs%20for%20more%20information.%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception%20exception%2C%20ErrorCategory%20errorCategory%2C%20Object%20target%2C%20String%20helpUrl)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception%20exception%2C%20ErrorCategory%20category%2C%20Object%20target)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Edge.SetupTasks.InstallAdamSchemaTask.InternalProcessRecord()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.%3CPROCESSRECORD%3Eb__91_1()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%20%5BERROR%5D%20The%20following%20error%20was%20generated%20when%20%22%24error.Clear()%3B%3CBR%20%2F%3Einstall-AdamSchema%20-LdapFileName%20(%24roleInstallPath%20%2B%20%22%5CSetup%5CData%5Cschemaadam.ldf%22)%3C%2FPROCESSRECORD%3E%3C%2FSCHEMACONTAINERDN%3E%3C%2FP%3E%3CP%3E%22%20was%20run%3A%20%22Microsoft.Exchange.Management.Edge.SetupTasks.AdamSchemaImportProcessFailureException%3A%20The%20AD%20LDS%20schema%20import%20process%20ldifde.exe%20failed%20with%20error%20code%208224.%20No%20schema%20has%20been%20imported%20into%20AD%20LDS.%20View%20the%20Setup%20logs%20for%20more%20information.%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception%20exception%2C%20ErrorCategory%20errorCategory%2C%20Object%20target%2C%20String%20helpUrl)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception%20exception%2C%20ErrorCategory%20category%2C%20Object%20target)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Edge.SetupTasks.InstallAdamSchemaTask.InternalProcessRecord()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.%3CPROCESSRECORD%3Eb__91_1()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%22.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%20%5BERROR%5D%20The%20AD%20LDS%20schema%20import%20process%20ldifde.exe%20failed%20with%20error%20code%208224.%20No%20schema%20has%20been%20imported%20into%20AD%20LDS.%20View%20the%20Setup%20logs%20for%20more%20information.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%20%5BERROR-REFERENCE%5D%20Id%3DAdamComponent___3dc0bdb578114784859fe9bf9663d1f3%20Component%3DEXCHANGE14%3A%5CCurrent%5CRelease%5CShared%5CDatacenter%5CSetup%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%20Setup%20is%20stopping%20now%20because%20of%20one%20or%20more%20critical%20errors.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0334%5D%20%5B1%5D%20Finished%20executing%20component%20tasks.%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A12.0350%5D%20%5B1%5D%20Ending%20processing%20Install-GatewayRole%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A24.0537%5D%20%5B0%5D%20CurrentResult%20setupbase.maincore%3A396%3A%200%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A24.0537%5D%20%5B0%5D%20End%20of%20Setup%3CBR%20%2F%3E%5B12%2F19%2F2019%2010%3A34%3A24.0537%5D%20%5B0%5D%20**********************************************%3C%2FPROCESSRECORD%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1076044%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1076044%22%20slang%3D%22en-US%22%3E%3CP%3EIssue%20of%20the%20update%20CU15%20on%20the%20edge%20server%20is%20fixed%3C%2FP%3E%3CP%3EWe%20verified%20the%20connectivity%20on%20port%2050389%20%3A%20OK%3C%2FP%3E%3CP%3EWe%20force%20from%20the%20exchange%20mailbox%20server%20a%20edge%20synchronization%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStart-EdgeSynchronization%20-ForceUpdateCookie%3CBR%20%2F%3EStart-EdgeSynchronization%20-ForceFullSync%3CBR%20%2F%3ETest-EdgeSynchronization%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWait%20a%20few%20minutes%20and%20restart%20the%20CU15%20update%20.%20Then%20it%20was%20fine%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1076740%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1076740%22%20slang%3D%22en-US%22%3EHello%20Microsoft%2C%20What%20is%20Microsoft%20s%20recommended%20procedure%20to%20upgrade%20Exchange%202016%20CU12%20servers%20running%20.NET%204.7.2%2C%20keeping%20in%20mind%20that%20CU12%20does%20not%20support%20.NET%204.8%20and%20CU15%20does%20not%20support%20.NET%204.7.2%20%3F%20i.e.%20in%20what%20exact%20order%20should%20we%20upgrade%20these%20two%20components%3F%20Thanks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1077365%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1077365%22%20slang%3D%22en-US%22%3E%3CP%3ETrying%20to%20upgrade%20an%20installation%20of%20Exchange%202019%20Management%20Tools%20from%20CU3%20to%20CU4%20on%20Windows%2010%201909%20fails%20at%20the%20prerequisite%20analysis%20with%20%22This%20computer%20requires%20.NET%20Framework%204.8%22.%20Installing%20the%20management%20tools%20on%2064-bit%20Windows%2010%20is%20supposed%20to%20be%20supported%2C%20and%20obviously%20.NET%20Framework%204.8%20is%20built%20into%201903%20and%201909.%20How%20are%20you%20supposed%20to%20get%20past%20this%20(presumably%20defective)%20check%3F%20What%20is%20it%20checking%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1078093%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1078093%22%20slang%3D%22en-US%22%3E%3CP%3ECU4%20fails%20to%20install%20with%3A%3C%2FP%3E%3CP%3EError%3A%3CBR%20%2F%3EThis%20computer%20requires%20.NET%20Framework%204.8%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4503548%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4503548%3C%2FA%3E).%3CBR%20%2F%3EFor%20more%20information%2C%20visit%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FExchange%2Fplan-and-deploy%2Fsystem-requirements%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2FExchange%2Fplan-and-deploy%2Fsystem-requirements%3Fview%3Dexchserver-2019%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20.net%204.8%20is%20already%20installed%20on%20Windows%20Server%20Core%20Version%2010.0.18362.535%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1078899%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1078899%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CSTRONG%3EExchange%20Calculator%26nbsp%3B10.3%3C%2FSTRONG%3E%3CBR%20%2F%3EIn%20my%20testing%20I%20noticed%20that%20the%20capacity-based%20results%20seemed%20a%20bit%20off%20for%20what%20I%20was%20looking%20to%20do%20and%20(u%3C%2FSPAN%3Enless%20I%20am%20missing%20something)%20it%20appears%20related%20to%20the%20math%20used%20to%20determine%20the%20database%20disk%20capacity%20requirements%20when%20utilizing%20mailbox%20tiers.%20When%20compared%20to%20older%20versions%20of%20the%20calculator%2C%20I%20don't%20see%20the%20ratio%20for%20the%20tiered%20mailbox%20configuration%20being%20applied%20properly.%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CBR%20%2F%3EIn%20order%20to%20more%20easily%20explain%20what%20I%20am%20seeing%2C%20I%20have%20created%20a%20quick%20(1.5%20minute)%20video%20of%20my%20experience%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DtjNSmudDlUc%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%22%3Ehttps%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DtjNSmudDlUc%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EI%20leave%20plenty%20room%20to%20be%20incorrect%20here...That%20said%2C%20it%20does%20seem%20to%20work%20as%20expected%20when%20averaging%20those%20tiers%20out%20manually%20ahead%20of%20time%20and%20utilizing%20a%20single%20tier%20in%20the%20calculator.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1084976%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1084976%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%20as%20Neil%20above.%20Existing%20installation%20of%20management%20tools%2C%20exchange%202019%20CU3%20on%20Windows%2010%20Pro%201909.%20Upgrade%20fails%20prereq%20check%20demanding%20dot%20net%204.8.%20The%20dot%20net%204.8%20web%20installer%20refuses%20to%20install%20claiming%20an%20equivalent%20or%20later%20version%20is%20already%20installed.%20Catch-22.%20Same%20failure%20whether%20you%20use%20the%20GUI%20setup%20or%20command%20line%20%2Fm%3Aupgrade%20option.%20I%20don't%20see%20any%20way%20around%20this.%20Hopefully%20we%20can%20continue%20to%20use%20the%20management%20tools%20from%20CU3.%20Not%20updating%20the%20management%20tools%20has%20been%20a%20problem%20in%20the%20past.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1092005%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092005%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20answer%20my%20own%20question%3A%20the%20prerequisite%20check%20for%20the%20.NET%20Framework%20looks%20at%20the%20registry%20key%26nbsp%3BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CNET%20Framework%20Setup%5CNDP%5Cv4%5CFull.%20On%20Windows%2010%201903%20and%201909%20the%20value%20is%20528040%2C%20on%20all%20other%20versions%20of%20Windows%20it%20is%20528049%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fmigration-guide%2Fhow-to-determine-which-versions-are-installed%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%22%3E%3CFONT%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fmigration-guide%2Fhow-to-determine-which-versions-are-installed%3C%2FFONT%3E%3C%2FA%3E).%20If%20you%20change%20the%20key%20on%201909%20to%20528049%20the%20check%20passes%20and%20upgrade%20%2F%20installation%20of%20the%20management%20tools%20on%20Windows%2010%201909%20succeeds.%20Obviously%20you%20then%20change%20it%20back%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1092336%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092336%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20this%20article%2C%20%3CSTRONG%3ECumulative%20Update%2023%3C%2FSTRONG%3E%20is%20the%20only%20CU%20listed%20as%20a%20supported%20environment%20for%20a%20hybrid%20deployment%20(with%20Exchange%20Server%202013).%20I%20was%20hoping%20that%20CU22%20was%20also%20still%20a%20valid%20CU%20for%20a%20hybrid%20deployment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20do%20I%20understand%20it%20correct%20that%20the%20statement%20that%20%22the%20most%20current%20or%20the%20prior%20Cumulative%20Update%22%20in%20a%20hybrid%20deployment%20is%20no%20longer%20valid%20for%20Exchange%20Server%202013%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20I%20miss%20something%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1092516%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092516%22%20slang%3D%22en-US%22%3EThe%20silence%20is%20deafening.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1092759%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092759%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F286871%22%20target%3D%22_blank%22%3E%40Sam_T%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EWhen%20upgrading%20Exchange%20from%20an%20unsupported%20CU%20to%20the%20current%20CU%20and%20no%20intermediate%20CUs%20are%20available%2C%20you%20should%20first%20upgrade%20to%20the%20latest%20version%20of%20.NET%20that's%20supported%20by%20Exchange%20and%20then%20immediately%20upgrade%20to%20the%20current%20CU.%20This%20method%20doesn't%20replace%20the%20need%20to%20keep%20your%20Exchange%20servers%20up%20to%20date%20and%20on%20the%20latest%20supported%20CU.%20Microsoft%20makes%20no%20claim%20that%20an%20upgrade%20failure%20will%20not%20occur%20using%20this%20method%2C%20which%20may%20result%20in%20the%20need%20to%20contact%20Microsoft%20Support%20Services.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fexchange%252Fplan-and-deploy%252Fsupportability-matrix%253Fview%253Dexchserver-2019%26amp%3Bdata%3D04%257C01%257CRob.Whaley%2540microsoft.com%257C452e04b9ae4f4349ff2208d792d1f8ba%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637139302848941535%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C-1%26amp%3Bsdata%3D0vhkAQgXb43OGUA3VYP9s8EN2Z3m16e%252BtVo42vM7DPo%253D%26amp%3Breserved%3D0%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%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068848%22%20slang%3D%22en-US%22%3EReleased%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068848%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20servicing%20cumulative%20updates%20for%20Exchange%20Server%202016%20and%202019.%26nbsp%3BThese%20updates%20include%20fixes%20for%20customer%20reported%20issues%20as%20well%20as%20all%20previously%20released%20security%20updates.%26nbsp%3B%3C%2FP%3ESetup%20Now%20Requires%20.NET%20Framework%204.8%3CP%3EAs%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FReleased-June-2019-Quarterly-Exchange-Updates%2Fba-p%2F698398%22%20target%3D%22_blank%22%3Epreviously%20announced%3C%2FA%3E%20.NET%204.8%20is%20now%20required%20and%20enforced%20by%20setup%20with%20the%20updates%20released%20today.%3C%2FP%3ECalculator%20Updates%3CP%3ECumulative%20Update%204%20includes%20a%20significant%20update%20to%20the%20Exchange%202019%20sizing%20calculator.%26nbsp%3B%20After%20the%20initial%20re-work%20and%20optimization%20for%20Exchange%202019%20previously%20delivered%2C%20we%E2%80%99ve%20updated%20some%20formulas%20based%20upon%20new%20Big%20Funnel%20performance%20data%20gathered%20from%20the%20O365%20service%20and%20real-world%20customer%20experiences.%26nbsp%3B%20Version%2010.3%20of%20the%20calculator%20includes%20improvements%20to%20calculations%20and%20default%20settings%20which%20allow%20for%20better%20and%20smoother%20utilization%20of%20disk%20resources.%3C%2FP%3E%3CP%3EWe%E2%80%99ve%20received%20feedback%20from%20customers%20that%20they%E2%80%99d%20like%20more%20information%20on%20constraints%20which%20impact%20system%20design%2C%20specifically%20disk%20resources.%26nbsp%3B%20Included%20in%20this%20update%2C%20is%20an%20indication%20on%20the%20Input%20worksheet%20will%20provide%20information%20as%20to%20whether%20the%20design%20is%20constrained%20by%20IOPs%20throughput%20or%20disk%20capacity.%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%E2%80%99ve%20added%20additional%20explanatory%20messages%20when%20the%20calculator%20detects%20a%20setting%20conflict%2C%20made%20additional%20improvements%20in%20input%20performance%20and%20improved%20support%20for%20using%20manual%2Foverride%20configurations.%26nbsp%3B%20The%20Volume%20Design%20sheet%20had%20a%20complete%20re-work%20to%20improve%20the%20presentation%20and%20accuracy%20of%20the%20information%20being%20displayed%20to%20support%20these%20changes.%3C%2FP%3E%3CP%3EAll-in-all%2C%20this%20version%20of%20the%20calculator%20provides%20the%20best%20possible%20experience%20to%20plan%20your%20Exchange%202019%20deployment%20and%20replaces%20all%20previous%20releases.%3C%2FP%3EAddress%20Book%20Policy%20Changes%3CP%3EWhen%20organizations%20deploy%20Address%20Book%20Policies%20to%20users%20they%20can%20sometimes%20hit%20an%20issue%20when%20a%20locally%20logged%20in%20user%20without%20a%20mailbox%20tries%20to%20open%20a%20mailbox%20linked%20to%20another%20user%20account%20using%20Outlook.%20This%20conflict%20results%20in%20ABP%E2%80%99s%20being%20inconsistently%20applied.%3C%2FP%3E%3CP%3EThe%20updates%20released%20today%20contain%20a%20change%20detailed%20in%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4532747%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%22%20target%3D%22_blank%22%3EKB4532747%3C%2FA%3E%20which%20resolves%20this%20issue%20and%20ensures%20the%20ABP%E2%80%99s%20assigned%20to%20the%20mailbox%20being%20opened%20are%20always%20used.%3C%2FP%3ERelease%20Details%3CP%3EThe%20KB%20articles%20that%20describe%20the%20fixes%20in%20each%20release%20and%20product%20downloads%20are%20available%20as%20follows%3A%3C%2FP%3EExchange%20Server%202019%20Cumulative%20Update%204%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4522149%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%22%20target%3D%22_blank%22%3EKB4522149%3C%2FA%3E)%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2FLicensing%2Fservicecenter%2Fdefault.aspx%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%22%20target%3D%22_blank%22%3EVLSC%20Download%3C%2FA%3E%20Exchange%20Server%202016%20Cumulative%20Update%2015%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4522150%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%22%20target%3D%22_blank%22%3EKB4522150%3C%2FA%3E)%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3FfamilyID%3D0d01ba8c-d415-4bc9-b5c7-3bce431d2e3b%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%22%20target%3D%22_blank%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3FfamilyID%3Decfaa4c8-e659-4e6f-9bcd-9635abb7df11%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%22%20target%3D%22_blank%22%3EUM%20Lang%20Packs%3C%2FA%3E%20Additional%20Information%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%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%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%2015%20or%2014%3B%202019%20Cumulative%20Update%204%20or%203.%3C%2FP%3E%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%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%22%20target%3D%22_blank%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%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%22%20target%3D%22_blank%22%3EExchange%20Server%20Release%20Notes%3C%2FA%3E.%3C%2FP%3E%3CP%3ENote%3A%20Documentation%20may%20not%20be%20fully%20available%20at%20the%20time%20this%20post%20is%20published.%3C%2FP%3E%3CP%3EThe%20Exchange%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1068848%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.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1068848%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeployment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%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-1097180%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20December%202019%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1097180%22%20slang%3D%22en-US%22%3E%3CP%3Efor%20me%20I%20had%20the%20same%20problem%20with%20.NET%204.8%20prerequisite%20check.%20I%20changed%20the%20registry%20setting%26nbsp%3BComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CNET%20Framework%20Setup%5CNDP%5Cv4%5CFull%5CRelease%20from%20528040%20to%20528049%20as%20suggested%20by%26nbsp%3BNeil_Flanagan.%20The%20setup%20can%20then%20be%20run.%20(I%20had%20permission%20issue%20with%20the%20registry%20key%20since%20only%20the%20TrustInstaller%20has%20write%20permission%20and%20it%20was%20the%20owner.%20So%20I%20needed%20to%20change%20the%20owner%20and%20then%20to%20grant%20myself%20to%20have%20write%20permission)%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. 

Setup Now Requires .NET Framework 4.8

As previously announced .NET 4.8 is now required and enforced by setup with the updates released today.

Calculator Updates

Cumulative Update 4 includes a significant update to the Exchange 2019 sizing calculator.  After the initial re-work and optimization for Exchange 2019 previously delivered, we’ve updated some formulas based upon new Big Funnel performance data gathered from the O365 service and real-world customer experiences.  Version 10.3 of the calculator includes improvements to calculations and default settings which allow for better and smoother utilization of disk resources.

We’ve received feedback from customers that they’d like more information on constraints which impact system design, specifically disk resources.  Included in this update, is an indication on the Input worksheet will provide information as to whether the design is constrained by IOPs throughput or disk capacity.

Dec2019 CU Post Image 1.png

 

We’ve added additional explanatory messages when the calculator detects a setting conflict, made additional improvements in input performance and improved support for using manual/override configurations.  The Volume Design sheet had a complete re-work to improve the presentation and accuracy of the information being displayed to support these changes.

All-in-all, this version of the calculator provides the best possible experience to plan your Exchange 2019 deployment and replaces all previous releases.

Address Book Policy Changes

When organizations deploy Address Book Policies to users they can sometimes hit an issue when a locally logged in user without a mailbox tries to open a mailbox linked to another user account using Outlook. This conflict results in ABP’s being inconsistently applied.

The updates released today contain a change detailed in KB4532747 which resolves this issue and ensures the ABP’s assigned to the mailbox being opened are always used.

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 15 or 14; 2019 Cumulative Update 4 or 3.

For the latest information on 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

21 Comments
Senior Member

Thanks guys, just a hint the KB is still showing .NET 4.72 as a prereq while it should be 4.8 by reading this Blog post

Senior Member

@The_Exchange_Team has released update about disk capacity that which i needed. Thanks

@Martin_Aigner good catch Martin. All fixed now. 

Senior Member

Another update without DKIM and DMARC support on-premises. 

New Contributor

Hello,

I updated my test exchange server from CU14 to CU15 . No issue for the exchange mailbox and cas server but big issues on the edge exchange server .

I raised a ticket to the premier support

It's failing at step 10 of 12 : Edge Transport Role

 

[12/19/2019 10:34:11.0256] [2] [WARNING] The performance counter definition file C:\Program Files\Microsoft\Exchange Server\V15\Bin\Perf\AMD64\ItemAssistantPerfCounters.xml could not be found.
Parameter name: DefinitionFileName
[12/19/2019 10:34:11.0256] [2] The performance counter definition file is invalid.
[12/19/2019 10:34:11.0256] [2] [WARNING] The performance counter definition file is invalid.
[12/19/2019 10:34:11.0256] [2] [WARNING] The performance counter definition file is invalid.
[12/19/2019 10:34:11.0272] [2] Ending processing new-perfcounters
[12/19/2019 10:34:11.0272] [1] The following 1 error(s) occurred during task execution:
[12/19/2019 10:34:11.0272] [1] 0. ErrorRecord: The performance counter definition file is invalid.
[12/19/2019 10:34:11.0272] [1] The previous errors were generated by a non-critical task and will be ignored.
[12/19/2019 10:34:11.0272] [1] Setup will continue processing component tasks...
[12/19/2019 10:34:11.0272] [1] Processing component 'ADAM Configuration' (Configuring the local AD LDS instance.).
[12/19/2019 10:34:11.0272] [1] Executing:
install-AdamSchema -LdapFileName ($roleInstallPath + "\Setup\Data\schemaadam.ldf")


[12/19/2019 10:34:11.0272] [2] Active Directory session settings for 'install-AdamSchema' are: View Entire Forest: 'True',
[12/19/2019 10:34:11.0272] [2] User specified parameters: -LdapFileName:'C:\Program Files\Microsoft\Exchange Server\V15\\Setup\Data\schemaadam.ldf'
[12/19/2019 10:34:11.0272] [2] Beginning processing install-AdamSchema
[12/19/2019 10:34:11.0272] [2] Running <C:\windows\ADAM ldifde.exe> with arguments <-i -f "C:\Program Files\Microsoft\Exchange Server\V15\\Setup\Data\schemaadam.ldf" -s localhost:50389 -j "C:\Users\edgetest\AppData\Local\Temp\1f15ef97-9aaa-4fcc-a23a-415df29873f5" -c "<SchemaContainerDN>" "#schemaNamingContext">.
[12/19/2019 10:34:12.0334] [2] Process ldifde.exe has finished with exit code 8224.
[12/19/2019 10:34:12.0334] [2] [ERROR] The AD LDS schema import process ldifde.exe failed with error code 8224. No schema has been imported into AD LDS. View the Setup logs for more information.
[12/19/2019 10:34:12.0334] [2] [ERROR] The AD LDS schema import process ldifde.exe failed with error code 8224. No schema has been imported into AD LDS. View the Setup logs for more information.
[12/19/2019 10:34:12.0334] [2] Ending processing install-AdamSchema
[12/19/2019 10:34:12.0334] [1] The following 1 error(s) occurred during task execution:
[12/19/2019 10:34:12.0334] [1] 0. ErrorRecord: The AD LDS schema import process ldifde.exe failed with error code 8224. No schema has been imported into AD LDS. View the Setup logs for more information.
[12/19/2019 10:34:12.0334] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Edge.SetupTasks.AdamSchemaImportProcessFailureException: The AD LDS schema import process ldifde.exe failed with error code 8224. No schema has been imported into AD LDS. View the Setup logs for more information.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Edge.SetupTasks.InstallAdamSchemaTask.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[12/19/2019 10:34:12.0334] [1] [ERROR] The following error was generated when "$error.Clear();
install-AdamSchema -LdapFileName ($roleInstallPath + "\Setup\Data\schemaadam.ldf")

" was run: "Microsoft.Exchange.Management.Edge.SetupTasks.AdamSchemaImportProcessFailureException: The AD LDS schema import process ldifde.exe failed with error code 8224. No schema has been imported into AD LDS. View the Setup logs for more information.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Edge.SetupTasks.InstallAdamSchemaTask.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[12/19/2019 10:34:12.0334] [1] [ERROR] The AD LDS schema import process ldifde.exe failed with error code 8224. No schema has been imported into AD LDS. View the Setup logs for more information.
[12/19/2019 10:34:12.0334] [1] [ERROR-REFERENCE] Id=AdamComponent___3dc0bdb578114784859fe9bf9663d1f3 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/19/2019 10:34:12.0334] [1] Setup is stopping now because of one or more critical errors.
[12/19/2019 10:34:12.0334] [1] Finished executing component tasks.
[12/19/2019 10:34:12.0350] [1] Ending processing Install-GatewayRole
[12/19/2019 10:34:24.0537] [0] CurrentResult setupbase.maincore:396: 0
[12/19/2019 10:34:24.0537] [0] End of Setup
[12/19/2019 10:34:24.0537] [0] **********************************************

New Contributor

Issue of the update CU15 on the edge server is fixed

We verified the connectivity on port 50389 : OK

We force from the exchange mailbox server a edge synchronization

 

Start-EdgeSynchronization -ForceUpdateCookie
Start-EdgeSynchronization -ForceFullSync
Test-EdgeSynchronization

 

Wait a few minutes and restart the CU15 update . Then it was fine

New Contributor
Hello Microsoft, What is Microsoft s recommended procedure to upgrade Exchange 2016 CU12 servers running .NET 4.7.2, keeping in mind that CU12 does not support .NET 4.8 and CU15 does not support .NET 4.7.2 ? i.e. in what exact order should we upgrade these two components? Thanks
Senior Member

Trying to upgrade an installation of Exchange 2019 Management Tools from CU3 to CU4 on Windows 10 1909 fails at the prerequisite analysis with "This computer requires .NET Framework 4.8". Installing the management tools on 64-bit Windows 10 is supposed to be supported, and obviously .NET Framework 4.8 is built into 1903 and 1909. How are you supposed to get past this (presumably defective) check? What is it checking?

New Contributor

CU4 fails to install with:

Error:
This computer requires .NET Framework 4.8 (https://support.microsoft.com/kb/4503548).
For more information, visit: https://docs.microsoft.com/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019

 

But .net 4.8 is already installed on Windows Server Core Version 10.0.18362.535

Senior Member

Exchange Calculator 10.3
In my testing I noticed that the capacity-based results seemed a bit off for what I was looking to do and (u
nless I am missing something) it appears related to the math used to determine the database disk capacity requirements when utilizing mailbox tiers. When compared to older versions of the calculator, I don't see the ratio for the tiered mailbox configuration being applied properly.


In order to more easily explain what I am seeing, I have created a quick (1.5 minute) video of my experience:


https://www.youtube.com/watch?v=tjNSmudDlUc

I leave plenty room to be incorrect here...That said, it does seem to work as expected when averaging those tiers out manually ahead of time and utilizing a single tier in the calculator.

Occasional Visitor

Same problem as Neil above. Existing installation of management tools, exchange 2019 CU3 on Windows 10 Pro 1909. Upgrade fails prereq check demanding dot net 4.8. The dot net 4.8 web installer refuses to install claiming an equivalent or later version is already installed. Catch-22. Same failure whether you use the GUI setup or command line /m:upgrade option. I don't see any way around this. Hopefully we can continue to use the management tools from CU3. Not updating the management tools has been a problem in the past.

Senior Member

To answer my own question: the prerequisite check for the .NET Framework looks at the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full. On Windows 10 1903 and 1909 the value is 528040, on all other versions of Windows it is 528049 (https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-ar...). If you change the key on 1909 to 528049 the check passes and upgrade / installation of the management tools on Windows 10 1909 succeeds. Obviously you then change it back again.

New Contributor

In this article, Cumulative Update 23 is the only CU listed as a supported environment for a hybrid deployment (with Exchange Server 2013). I was hoping that CU22 was also still a valid CU for a hybrid deployment.

 

So, do I understand it correct that the statement that "the most current or the prior Cumulative Update" in a hybrid deployment is no longer valid for Exchange Server 2013?

 

Did I miss something?

New Contributor
The silence is deafening.

@Sam_T 
When upgrading Exchange from an unsupported CU to the current CU and no intermediate CUs are available, you should first upgrade to the latest version of .NET that's supported by Exchange and then immediately upgrade to the current CU. This method doesn't replace the need to keep your Exchange servers up to date and on the latest supported CU. Microsoft makes no claim that an upgrade failure will not occur using this method, which may result in the need to contact Microsoft Support Services.

 

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

Regular Visitor

for me I had the same problem with .NET 4.8 prerequisite check. I changed the registry setting Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release from 528040 to 528049 as suggested by Neil_Flanagan. The setup can then be run. (I had permission issue with the registry key since only the TrustInstaller has write permission and it was the owner. So I needed to change the owner and then to grant myself to have write permission)

Occasional Visitor

@Olivier Debonne , If CU23 is the final CU issued for Exchange 2013 and it's been more than three months since CU23 was issued, then it makes sense that you need to be on that release for support in a hybrid environment.  CU22 being more than six months old would have fallen off by now.

Frequent Visitor

Can you please add a SHA256 hash for the Exchange 2013 and 2016 CU ISO downloads?  Cumulative Update CU15 for Exchange Server 2016 (KB4522150) at https://www.microsoft.com/en-us/download/details.aspx?id=100780 lacks this information, and I'm not sure I have a valid download of entire 6.6 GB file ExchangeServer2016-x64-CU15.ISO.

Occasional Visitor

@The_Exchange_Team, it looks like a feature that became broken in CU14 is still broken in CU15.  The eDiscovery PST export tool still throws a "FailedToLoadStatus" error.  The fix that finally worked for us is described in the comments at the following page (note that it's a different Robert, not me) : https://eightwone.com/2019/11/13/security-updates-exchange-2013-2019/

 

For an Exchange admin, it's not such a big deal perhaps to copy DLLs from an earlier, working version of the export tool.  But it's the legal folks that run the tool in some organizations and they may not be so technical.  Note: I also tried wiping out my Windows profile on a 2012 R2 server that was throwing the error and that didn't help.  I had to copy the old DLL to get relief.  I hope this can be fixed in the next CU.

Occasional Visitor

After 2016 CU15 unable to fix the unheathy status:

 

Server State Name TargetResource HealthSetName AlertValue ServerComponent
------ ----- ---- -------------- ------------- ---------- ---------------

Server1 NotApplicable MaintenanceFailureMonitor.OLS User Store - Query OLS User Store - Query Unhealthy None

 

>Get-ServerHealth -HealthSet "OLS User Store - Query" -Server Server1 | Format-List

RunspaceId : 522ba05e-d5f7-44cc-9022-593a22cee5d0
Server : Server1
CurrentHealthSetState : NotApplicable
Name : MaintenanceFailureMonitor.OLS User Store - Query
TargetResource :
HealthSetName : OLS User Store - Query
HealthGroupName : ServiceComponents
AlertValue : Unhealthy
FirstAlertObservedTime : 16.03.2020 12:27:52
Description :
IsHaImpacting : False
RecurranceInterval : 300
DefinitionCreatedTime : 16.03.2020 12:08:16
HealthSetDescription :
ServerComponentName : None
LastTransitionTime : 16.03.2020 12:27:52
LastExecutionTime : 16.03.2020 13:12:53
LastExecutionResult : Succeeded
ResultId : 482515544
WorkItemId : 2033339796
IsStale : False
Error :
Exception :
IsNotified : False
LastFailedProbeId : -274855559
LastFailedProbeResultId : 128480061
ServicePriority : 0
Identity : OLS User Store - Query\MaintenanceFailureMonitor.OLS User Store - Query\
IsValid : True
ObjectState : New


EVENT Viewer: Microsoft-Exchange-ManagedAvailability/Monitoring
Maintenance workitem "OlsQuery.Maintenance.Workitem" (ID: 2045954113) has failed. Health Manager has detected it is either set to run once and failed, or has been failing consistently. Maintenance workitem failure could cause monitoring gap and should be investigated.
The error message from the last result is:
System.FormatException: Input string was not in a correct format.
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Double.Parse(String s)
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetAttribute[T](Dictionary`2 attributes, String attributeName, Boolean isMandatory, T defaultValue, Func`2 parseMethod)
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetAttribute[T](String attributeName, Boolean isMandatory, T defaultValue, Func`2 parseMethod)
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetDouble(String attributeName, Boolean isMandatory, Double defaultValue, Nullable`1 minimum, Nullable`1 maximum)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.OlsQuery.FailureRateProbeSettings..ctor(WorkDefinition workDefinition, String prefix)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.OlsQuery.FailureRateProbe.AddWorkDefinitions(MaintenanceWorkItem maintenanceWorkItem)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.OlsQuery.OlsQueryDiscovery.CreateMonitoringContexts(LocalEndpointManager endpointManager)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.OlsQuery.OlsQueryDiscovery.DoWork(CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<ExecuteAsync>d__b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<StartExecutingAsync>d__7.MoveNext()

@stennukas - I've checked with a few people and we're not familiar with this one - please open a support case.