Merge pull request #2287 from microsoft/Batre-MSFT-patch-3

Update Emerging-Issues.md

Author: dpaulson45

docs/Emerging-Issues.md

@@ -13,6 +13,7 @@ This page lists emerging issues for Exchange On-Premises deployments, possible r
 
 |**Updated on**|**Update causing the issue**|**Issue**|**Workaround/Solution**|
 |-|-|-|-|
+| 2/24/2025 | [Exchange Server 2019 CU14](https://support.microsoft.com/KB/5035606) OR [Exchange Server 2019 Cumulative Update 15](https://support.microsoft.com/kb/5042461) | Environments that are using SSL offloading configuration may face issues with Outlook connectivity issues after upgrading to [Exchange Server 2019 CU14](https://support.microsoft.com/KB/5035606) OR [Exchange Server 2019 Cumulative Update 15](https://support.microsoft.com/kb/5042461) | As announced in [August 2023](https://techcommunity.microsoft.com/t5/exchange-team-blog/coming-soon-enabling-extended-protection-on-exchange-server-by/ba-p/3911849) , by default, starting with [Exchange Server 2019 CU14](https://support.microsoft.com/KB/5035606), setup enables the Windows Extended Protection (EP) feature on the Exchange server being installed. Extended Protection isn't supported in environments that use SSL Offloading. SSL termination during SSL Offloading causes Extended Protection to fail. To enable Extended Protection in your Exchange environment, you must not be using SSL offloading with your Load Balancers. Please check [this link](https://learn.microsoft.com/exchange/plan-and-deploy/post-installation-tasks/security-best-practices/exchange-extended-protection?view=exchserver-2019#scenarios-that-could-affect-client-connectivity-when-extended-protection-was-enabled) for more details |
 | 2/6/2025 | HCW | You may see following error when creating Migration Endpoint using HCW <BR><BR> "The last connection attempt happened too recently" | Please create the Migration Endpoint manually by following steps in [this article](https://aka.ms/mep) while the issue is being fixed in HCW|
 | 1/29/2025 | [November Exchange Security Update for Exchange 2016 & Exchange 2019 V2](https://support.microsoft.com/help/5049233) | You may see following error when installing [November 2024 V2 Exchange Security Update](https://support.microsoft.com/topic/description-of-version-2-of-the-security-update-for-microsoft-exchange-server-2019-and-2016-november-27-2024-kb5049233-e807f65d-da39-48a9-9a7e-69612cac8077): <BR><BR> Error 1935. An error occurred during the installation of assembly 'Microsoft.Exchange.Data.Common,version="15.1.2503.00",fileVersion="15.1.2507.44",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL"'. For more information, refer to Microsoft Help and Support. HRESULT: 0x800700B7. assembly interface: IAssemblyCacheItem, function: Commit, component: {B79F9EB4-6D81-48F3-BC2D-3A0A83C30742} | Please follow the workaround provided on [this KB article](https://aka.ms/NovSUKB) |
 | 11/29/2024 | [November Exchange Security Update for Exchange 2016 & Exchange 2019 V2](https://support.microsoft.com/help/5049233) | Time zone exception may be reported in event viewer, after installing the [November Exchange Security Update for Exchange 2016 & Exchange 2019 V2](https://support.microsoft.com/help/5049233) <BR><BR> Event log entries are generated if Exchange Server fails to process calendar information, such as: <BR><BR> w3wp\#MSExchangeOWAAppPool, M.Exchange.Net , M.E.E.ExIanaTimeZoneProvider+Cache.AddTimeZone, M.E.ExchangeSystem.InvalidTimeZoneException <BR>OR<BR>Microsoft.Exchange.ExchangeSystem.InvalidTimeZoneException: Time zone id already exists | Please follow the workaround provided on [this KB article](https://support.microsoft.com/en-us/topic/time-zone-exception-occurs-after-installing-exchange-server-november-2024-su-version-1-or-version-2-851b3005-6d39-49a9-a6b5-5b4bb42a606f) |
@@ -22,8 +23,6 @@ This page lists emerging issues for Exchange On-Premises deployments, possible r
 | 4/23/2024 |  [March 2024 Security Update for Exchange 2019,2016](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2024-exchange-server-security-updates/ba-p/4075348) | After installing the Security Update, add-ins may stop working with following error <BR><BR>"Add-in Error Something went wrong and we couldn't start this add-in. Please try again later or contact your system administrator   | Please install [April 2024 Hotfix Update](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-april-2024-exchange-server-hotfix-updates/ba-p/4120536) |
 | 4/23/2024 |  [March 2024 Security Update for Exchange 2019,2016](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2024-exchange-server-security-updates/ba-p/4075348) |After installing the March 2024 Security Update, Unread envelope icon is not getting updated after applying March 2024 SU   | Please install [April 2024 Hotfix Update](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-april-2024-exchange-server-hotfix-updates/ba-p/4120536) |
 | 4/23/2024 |  [March 2024 Security Update for Exchange 2019,2016](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2024-exchange-server-security-updates/ba-p/4075348) |After installing the March 2024 Security Update, preview of Office documents in OWA may fail with error "Sorry, there was a problem and we can't open this document."   | Please install [April 2024 Hotfix Update](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-april-2024-exchange-server-hotfix-updates/ba-p/4120536) |
-| 2/20/2024 | [CU 14 for Exchange 2019](https://support.microsoft.com/KB/5035606) | Environments that are using SSL offloading configuration may face issues with Outlook connectivity issues after upgrading to Exchange 2019 CU14.  | As announced in [August 2023](https://techcommunity.microsoft.com/t5/exchange-team-blog/coming-soon-enabling-extended-protection-on-exchange-server-by/ba-p/3911849) , by default, starting with CU14, Setup enables the Windows Extended Protection (EP) feature on the Exchange server being installed. Extended Protection isn't supported in environments that use SSL Offloading. SSL termination during SSL Offloading causes Extended Protection to fail. To enable Extended Protection in your Exchange environment, you must not be using SSL offloading with your Load Balancers. Please check [this link](https://learn.microsoft.com/exchange/plan-and-deploy/post-installation-tasks/security-best-practices/exchange-extended-protection?view=exchserver-2019#scenarios-that-could-affect-client-connectivity-when-extended-protection-was-enabled) for more details |
-| 2/20/2024 | [CU 14 for Exchange 2019](https://support.microsoft.com/KB/5035606)| Environments that are using SSL offloading configuration may face issues with Outlook connectivity issues after upgrading to Exchange 2019 CU14. | As announced in [August 2023](https://techcommunity.microsoft.com/t5/exchange-team-blog/coming-soon-enabling-extended-protection-on-exchange-server-by/ba-p/3911849) , by default, starting with CU14, Setup enables the Windows Extended Protection (EP) feature on the Exchange server being installed. Extended Protection isn't supported in environments that use SSL Offloading. SSL termination during SSL Offloading causes Extended Protection to fail. To enable Extended Protection in your Exchange environment, you must not be using SSL offloading with your Load Balancers. Please check [this link](https://learn.microsoft.com/exchange/plan-and-deploy/post-installation-tasks/security-best-practices/exchange-extended-protection?view=exchserver-2019#scenarios-that-could-affect-client-connectivity-when-extended-protection-was-enabled) for more details |
 | 2/19/2024 | [CU 14 for Exchange 2019](https://support.microsoft.com/topic/5036404) | Exchange 2019 CU14 RecoverServer fails while creating "New-PushNotificationsVirtualDirectory" with following error: <BR><BR>Exception setting "ExtendedProtectionTokenChecking": "Cannot convert null to type "Microsoft.Exchange.Data.Directory.SystemConfiguration.ExtendedProtectionTokenCheckingMode" due to enumeration values that are not valid.<BR>  | Please follow the steps from [this KB](https://support.microsoft.com/topic/5036404) to resolve the issue
 | 11/23/2023 | [November 2023 Security Update](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-november-2023-exchange-server-security-updates/ba-p/3980209) for Exchange 2016, Exchange 2019 | Some customers may find queue viewer crashing with error <BR><BR>"Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints" | The error can occur if the Exchange server auth certificate has expired. Solution is to renew the [Exchange server auth certificate manually](https://learn.microsoft.com/exchange/troubleshoot/administration/cannot-access-owa-or-ecp-if-oauth-expired) or by using [this script](https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/) |
 | 10/12/2023 | [All versions of August 2023 Security Update](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-august-2023-exchange-server-security-updates/ba-p/3892811) for Exchange 2016, Exchange 2019 | Users in account forest can't change expired password in OWA in multi-forest Exchange deployments after installing any version of [August 2023 Security Update for Exchange servers](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-august-2023-exchange-server-security-updates/ba-p/3892811) <BR><BR>**Note**<BR> The account forest user will be able to change the password after they sign in to Outlook on the web if their password is not yet expired. The issue affects only account forest users who have passwords that are already expired. This change does not affect users in organizations that don't use multiple forests.|** Update on 10/12/2023 ** <BR><BR> Follow steps on [this article](https://support.microsoft.com/topic/users-in-account-forest-can-t-change-expired-password-in-owa-in-multi-forest-exchange-deployments-after-installing-august-2023-su-b17c3579-0233-4d84-9245-755dd1092edb) |