Mainstream Support for Exchange Server 2019 Ends Today

Valistral thanks for you comment. I'll give that a try tomorrow. And yes the problem was not solved with CU14.

JanMi we bumbed on that the other day while testing, the problem is not related to German localisations or localisations but to eventual UTF encoded characters present into FederationMetadata.xml, as the New-AuthServer commandlet is unable to parse UTF content by the looks. For the Italian locale removing every accented word in claims definitions and descriptions from ADFS, allowed the command to continue correctly.

And by the looks Exchange Server 2019 CU14 is still affected.

Nino_Bilic Ticket was closed due to not eligible for premier support. But the support assistent could reproduce the issue. Would be nice to have a official statement from The_Exchange_Team 

This is Microsoft just reshaping the meaning of what is "eligible for support".

Nino_Bilic I opened a ticket (2402090030004762) yesterday regarding this issue. Maybe this helps solving it.

JanMi Ack. At this time, we did not track this as a known issue, but will work on figuring out / reproducing / figuring out how to address.

The_Exchange_Team ScottSchnoll Nino_Bilic it looks like there is an issue with ADFS on localized (german) Windows Server 2022 operating system when enabling modern Auth (New-AuthServer) in an Exchange 2019 CU13 on-premises enviornment:

New-AuthServer -Type ADFS `
 -Name "JansCloudLabADFS" `
 -AuthMetadataUrl https://adfs.janscloudlab.de/FederationMetadata/2007-06/FederationMetadata.xml

Das Metadatendokument für die Authentifizierung kann nicht analysiert werden.
+ CategoryInfo : ParserError: (:) [New-AuthServer], AuthMetadataParserException
+ FullyQualifiedErrorId : [Server=TEST-EXCH02,RequestId=66961c25-9510-4ef0-b68d-dc586ca6a018,TimeStamp=08.02.2024 19:48:45]

[FailureCategory=Cmdlet-AuthMetadataParserException] D778FAD3,Microsoft.Exchange.Management.SystemConfigurationTasks.NewAuthServer
+ PSComputerName : test-exch02.ad.janscloudlab.de

Replacing the ADFS on german based Windows Server 2022 with an Server in english language everything works fine.

Is it a known issue and will it still be fixed in CU14 or CU15 even when we are in extended support now?

Frank_CariusBut the "Exchange Management Role" is still something that I must install from Exchange Server installation media on a Windows server and then update regularly, right? So I still need an Exchange Server, just without the database and transport roles. Did I understand that correctly?

You can install the Exchange Management Role

svhelden : You can install the Exchange Management Role only to manage the local AD exchange properties and let ADSync replicate them. So no local "exchange server" needed. 

benoitdbag : 3600 Limit is really an issue, but do you really want to have that in an Exchange Malbox?. normally this load is routet to an CRM-System/Newletter service and they should not pull these mails using POP3/IMAP4
Large MailboxMig is a challenge, of larger than 100GB. But a support engineer can add prepopulated archives and you can do a PSTimport then. But yes, thats not staight forward.

MX-Records?  I see no problem setting MX-records to 3rd Party Solutions and forward them via a Inbound Partner Connector to my tenant.

Frank

In November we were told "The CU14 release date slipped from this year to early next year. It will now likely be released in January 2024. " and "When CU14 is released in January". Then past Jan 9th "CU14 is in its final stages of testing and validation and will be released as soon as that's finished."

ms 

Since today is 31st, can we expect this to be released in soon in February or there is a chance of further delays?

TIA