{"id":744,"date":"2020-06-16T18:16:51","date_gmt":"2020-06-16T23:16:51","guid":{"rendered":"https:\/\/itblog.ldlnet.net\/?p=744"},"modified":"2020-06-16T18:32:08","modified_gmt":"2020-06-16T23:32:08","slug":"exchange-server-quarterly-update-cumulative-update-6-for-exchange-server-2019","status":"publish","type":"post","link":"https:\/\/itblog.ldlnet.net\/index.php\/2020\/06\/16\/exchange-server-quarterly-update-cumulative-update-6-for-exchange-server-2019\/","title":{"rendered":"Exchange Server Quarterly Update &#8211; Cumulative Update 6 for Exchange Server 2019"},"content":{"rendered":"\n<p>As many of you that follow Exchange have knowledge of, Microsoft releases their updates for Exchange Server every 3 months. Below is the latest update for Exchange Server 2019. I will be installing it very soon and will post any issues I may have with Server Core and GUI versions of Windows 2019.<\/p>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<p>Cumulative Update 6&nbsp;for Microsoft Exchange Server 2019&nbsp;was released on June 16, 2020. This cumulative update is a security update. It&nbsp;includes fixes for&nbsp;<a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4556415\/cumulative-update-6-for-exchange-server-2019#issues\" target=\"_blank\" rel=\"noreferrer noopener\">nonsecurity issues<\/a>&nbsp;and all previously released fixes for security and nonsecurity issues. These fixes will also be included in&nbsp;later&nbsp;<a href=\"https:\/\/docs.microsoft.com\/Exchange\/new-features\/build-numbers-and-release-dates\" target=\"_blank\" rel=\"noreferrer noopener\">cumulative updates for Exchange Server 2019<\/a>.&nbsp;<\/p>\n\n\n\n<p>This update also includes new daylight saving time (DST) updates for Exchange Server 2019. For more information about DST,&nbsp;see&nbsp;<a href=\"https:\/\/support.microsoft.com\/en-us\/help\/22803\" target=\"_blank\" rel=\"noreferrer noopener\">Daylight Saving Time Help and Support Center<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Known issues in this cumulative update<\/h2>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<ul class=\"wp-block-list\"><li>In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the&nbsp;<strong>\/PrepareDomain<\/strong>&nbsp;option in Setup, this action must be completed after the&nbsp;<strong>\/PrepareAD<\/strong>&nbsp;command for this cumulative update has been completed and the changes are replicated to all domains.&nbsp;Setup will try to run the&nbsp;<strong>\/PrepareAD<\/strong>&nbsp;command during the first server installation. Installation will finish only if the user who initiated Setup&nbsp;has the appropriate permissions.<br><br><strong>Notes<\/strong><ul><li>If you are upgrading from&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/support.microsoft.com\/en-us\/help\/4488401\" target=\"_blank\">Cumulative Update 2 for Exchange Server 2019<\/a>&nbsp;or&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/docs.microsoft.com\/Exchange\/new-features\/build-numbers-and-release-dates?view=exchserver-2019\" target=\"_blank\">a later cumulative update<\/a>&nbsp;for Exchange Server 2019 to&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/support.microsoft.com\/en-us\/help\/4556414\" target=\"_blank\">Cumulative Update 6&nbsp;for Exchange Server 2019<\/a>, there\u2019s no need to run the&nbsp;<strong>\/PrepareAD<\/strong>&nbsp;or&nbsp;<strong>\/PrepareDomain<\/strong>. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required.<\/li><li>If you have ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 2&nbsp;for Exchange Server 2019), or this is a first Exchange Server installation in the AD, then this&nbsp;<strong>Known Issue<\/strong>&nbsp;section should be taken care of.<br><ul><li><strong>About the \/PrepareDomain operation in multidomain:<\/strong><br><br>The&nbsp;<strong>\/PrepareDomain<\/strong>&nbsp;operation automatically runs in the Active&nbsp;Directory domain in which the&nbsp;<strong>\/PrepareAD&nbsp;<\/strong>commandis run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the&nbsp;<strong>\/PrepareDomain<\/strong>&nbsp;in other domains in the forest.<br><\/li><li><strong>About the permission question:<\/strong><br><br>As the&nbsp;<strong>\/PrepareAD<\/strong>&nbsp;is triggered in Setup, if the user who initiates Setup isn&#8217;t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages.<br><br><img decoding=\"async\" src=\"https:\/\/msegceporticoprodassets.blob.core.windows.net\/asset-blobs\/4523704_en_1\" alt=\"the Active Directory schema isn't up-to-date error\"><br><br>To avoid the&nbsp;errors, either the user should join Schema Admins and Enterprise Admins groups&nbsp;or another user in Schema Admins and Enterprise Admins groups manually runs the&nbsp;<strong>\/PrepareAD<\/strong>&nbsp;for this Cumulative Update first. Then, the Exchange admin user can start Setup.<br><\/li><\/ul><\/li><li>Autodiscover Event ID 1 occurs after you install&nbsp;Cumulative Update 3&nbsp;for Exchange Server 2019. For more information, see&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/support.microsoft.com\/en-us\/help\/4532190\" target=\"_blank\">KB&nbsp;4532190<\/a>.<\/li><\/ul><\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Issues that this cumulative update fixes<\/h2>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<p>This cumulative update also fixes the issues that are described in the following Microsoft Knowledge Base articles:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559441\" target=\"_blank\" rel=\"noreferrer noopener\">4559441&nbsp;<\/a>Foreign language characters set in RejectMessageReasonText of a transport rule aren&#8217;t shown correctly in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4547707\" target=\"_blank\" rel=\"noreferrer noopener\">4547707&nbsp;<\/a>Enable piping for Restore-RecoverableItems in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4549689\" target=\"_blank\" rel=\"noreferrer noopener\">4549689&nbsp;<\/a>HMA EvoSTS certificate rollover causes authentication prompts due to stalled key on worker process spawn (warmup phase) in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559446\" target=\"_blank\" rel=\"noreferrer noopener\">4559446&nbsp;<\/a>Changes to Outlook on the web blocked file extensions and MIME types in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559440\" target=\"_blank\" rel=\"noreferrer noopener\">4559440&nbsp;<\/a>Export to a PST for an eDiscovery search fails Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559439\" target=\"_blank\" rel=\"noreferrer noopener\">4559439&nbsp;<\/a>EAS creates failure report if a message with unknown recipients is in Drafts in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559442\" target=\"_blank\" rel=\"noreferrer noopener\">4559442&nbsp;<\/a>2080 Events caused by empty values in HKLM\\SYSTEM\\CurrentControlSet\\Services\\MSExchange ADAccess\\Instance0 in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559438\" target=\"_blank\" rel=\"noreferrer noopener\">4559438&nbsp;<\/a>Edge Transport server hangs in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559443\" target=\"_blank\" rel=\"noreferrer noopener\">4559443&nbsp;<\/a>Managed Folder Assistant fails with Event ID 9004 NotInBagPropertyErrorException in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559437\" target=\"_blank\" rel=\"noreferrer noopener\">4559437&nbsp;<\/a>PR_RECIPIENT_ENTRYID is computed if no email address or type in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559444\" target=\"_blank\" rel=\"noreferrer noopener\">4559444&nbsp;<\/a>Conversion from HTML to RTF removes non-breaking space in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559436\" target=\"_blank\" rel=\"noreferrer noopener\">4559436&nbsp;<\/a>Attachments with properties (like Azure Information Protection labels) not always matching in Exchange Server 2019<\/li><li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4559435\" target=\"_blank\" rel=\"noreferrer noopener\">4559435&nbsp;<\/a>Introduce an OrganizationConfig flag to enable or disable recipient read session in Exchange Server 2019<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Get Cumulative Update 6 for Exchange Server 2019<\/h2>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Volume Licensing Center<\/h3>\n\n\n\n<p>To get Cumulative Update 6&nbsp;for Exchange Server 2019, go to&nbsp;<a href=\"https:\/\/www.microsoft.com\/Licensing\/servicecenter\/default.aspx\" target=\"_blank\" rel=\"noreferrer noopener\">Microsoft Volume Licensing Center<\/a>.<\/p>\n\n\n\n<p><strong>Note<\/strong>&nbsp;The Cumulative Update 6&nbsp;package can be used to run a new installation of Exchange Server 2019&nbsp;or to upgrade an existing Exchange Server 2019&nbsp;installation to Cumulative Update 6.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cumulative update information<\/h2>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisites<\/h3>\n\n\n\n<p>This cumulative update requires Microsoft .NET Framework 4.8.<\/p>\n\n\n\n<p>A component that&#8217;s used within Exchange Server requires a new Visual C++ component to be installed together with Exchange Server. This&nbsp;prerequisite&nbsp;can be downloaded at&nbsp;<a href=\"https:\/\/www.microsoft.com\/download\/details.aspx?id=30679\" target=\"_blank\" rel=\"noreferrer noopener\">Visual C++ Redistributable Package for Visual Studio 2012<\/a>.<\/p>\n\n\n\n<p>For more information about the prerequisites to set up Exchange Server 2019, see&nbsp;<a href=\"https:\/\/docs.microsoft.com\/Exchange\/plan-and-deploy\/prerequisites\" target=\"_blank\" rel=\"noreferrer noopener\">Exchange 2019 prerequisites<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Restart requirement<\/h3>\n\n\n\n<p>You may have to restart the computer after you apply this cumulative update package.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Registry information<\/h3>\n\n\n\n<p>You don&#8217;t have to make any changes to the registry after you apply this cumulative update package.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Removal information<\/h3>\n\n\n\n<p>After you install this cumulative update package, you can&#8217;t uninstall the package to revert to an earlier version of Exchange Server 2019. If you uninstall this cumulative update package, Exchange Server 2019&nbsp;is removed from the server.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-text-color has-background has-dark-purple-background-color has-dark-purple-color is-style-wide\"\/>\n\n\n\n<h2 class=\"has-text-align-center wp-block-heading\">CHECK FOR UPDATES REGULARLY!<br>POSITIVE ATTITUDE <br>EQUALS <br>POSITIVE MINDSET!<\/h2>\n\n\n\n<p class=\"has-small-font-size\"><strong>REFERENCES:<\/strong><br><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4556415\/cumulative-update-6-for-exchange-server-2019\" target=\"_blank\" rel=\"noreferrer noopener\">Exchange Server 2019 CU6<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>As many of you that follow Exchange have knowledge of, Microsoft releases their updates for Exchange Server every 3 months. Below is<\/p>\n<p class=\"link-more\"><a class=\"myButt \" href=\"https:\/\/itblog.ldlnet.net\/index.php\/2020\/06\/16\/exchange-server-quarterly-update-cumulative-update-6-for-exchange-server-2019\/\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":161,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,2],"tags":[9,151,147,148],"class_list":["post-744","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-exchange","category-general","tag-exchange","tag-exchange-2019","tag-exchange-setup","tag-exchange-upgrade","odd"],"_links":{"self":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/744","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/comments?post=744"}],"version-history":[{"count":2,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/744\/revisions"}],"predecessor-version":[{"id":747,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/744\/revisions\/747"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media\/161"}],"wp:attachment":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media?parent=744"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/categories?post=744"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/tags?post=744"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}