Today we are announcing the availability of the 2024 H1 Cumulative Update (CU) for Exchange Server 2019 (aka CU14). CU14 includes fixes for customer reported issues, a security change, and all previo...
Updated Feb 22, 2024
Version 11.0
Blog Post
The_Exchange_Team Nino_Bilic Since TLS 1.0, 1.1 & 1.2 is already enabled on Exchange servers so after creating "SchUseStrongCypto" Key should not impact anything to the exchange servers if any of the client is still coming with TLS1.0 or 1.1 connections, right?
Also, I dont have SchUseStrongCrypto key created at below registry path. why it is still checking v.2.0 do I need to make changes here also.?
HKLM\Software\WOW6432Node\Microsoft\.NetFramework\v2.0.50727 - no SchUseStrongCypto and SystemDefaultTLSversion entry present.
HKLM\Software\WOW6432Node\Microsoft\.NetFramework\v4.0.30319\ only SystemDefaultTLSVersions entry is there no SchUseStrongCypto
if I run below command, it won't make any changes to the Server only give me output what pre-requisites needed to configure, right?
PS C:\> .\ExchangeExtendedProtectionManagement.ps1 -PrerequisitesCheckOnly