Windows Server 2022 TLS and Server Manager errors.

Question

hello everyone!
We are migrating from Exchange 2016 to 2019 version.

After installing Exchange 2019 CU12 distributions on Windows Server 2022 and creating a DAG, the following two errors appeared.
1.There is an error in the system logs for the TLS protocol:
Log Name: System
Source: Schannel
Date: 12/29/2022 3:38:44 PM
Event ID: 36871
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ru1-mbx-01.cobion.group
Description:
A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

corrected according to this recommendation: a-fatal-error-occurred-while-creating-a-tls-client-credential
Will disabling the script of the first problem affect the work of clients and the mail service?

2.An error like this constantly appears in the Server Manager panel:

Is there a relationship with mail services, the appearance of an error in Server Manager?
Wherever I Googled this error, it didn't help.
Both of these errors appeared after we installed MS Exchange 2019 CU 12 distributions on Windows Server 2022.

Actually two questions:

1. Will disabling the script of the first problem affect the work of clients and the mail service?
2. Is there a relationship with mail services, the appearance of an error in Server Manager?

Thanks!

Answer 1

Hi @Cobion ，
Thank you for sharing your current progress.
According to the screenshot in the original description, the warning existed before the script was run.
There's a Server Manager Troubleshooting Guide on the TechNet Wiki that might help you with your refresh errors.

In addition ，I also found some similar threads ,you can try referring to the solutions in the link to see if the warning changes:
Windows Server 2012 R2 upgrade - Refresh completed with one or more warning message (microsoft.com)
Automatic Refresh Error (microsoft.com)

If none of the above suggestions help for this warning，it is recommended that you create a new thread, and add the Windows-Server related tags to get more professional help.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi! Tell me, do I need to manually enable TLS 1.2 on Exchange 2019, or is it enabled by default? I just don't remember it being enabled on the original Exchange 2016. Where can I see it?
Thanks!

And if there is an opportunity, please tell me about the security settings (Extended Protection in Exchange Server - description-of-the-security-update-for-microsoft-exchange-server-2019-and-2016-october-11-2022-kb5019077-b5ae8793-5e5c-4faa-972d-9228945973e5), in the latest SU Exchange Server 2019 CU12 Nov22SU - does it close all the settings that needed to be done on the IIS side, or first you need to do it by link, and then put SU messages?
Thanks!

Answer 3

Hi @Cobion ,

1. By default, Windows Server 2022 uses Transport Layer Security (TLS) 1.3. Support for TLS 1.3 will be added to Exchange Server 2019 in 2023.

It is recommend that you currently enable TLS 1.2 on your Exchange server, which does not affect the work of clients and messaging services.

2.Regarding the error in Server Manager, I found some relevant threads for your reference:
computed response packet size (microsoft.com)
WinRM packet size is somehow too big so everything decides to freak out - Microsoft Q&A
According to the problem scenarios provided by other users, this is not only due to the error caused by installing exchange2019.It is recommended that you run this command to increase the maximum envelope size to see if it works：

winrm set winrm/config @{MaxEnvelopeSizekb="xxxxx"}   

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.