Building a new SolarWinds Platform on VMWare, Windows Server 2019 running SolarWinds Platform 2023.2.1
Under My Deployment > Deployment Health showed an issue with TLS 1.0 & TLS 1.1
The help pane in Deployment Health said to add two registry keys to each with Server Set Enabled & Client Set Enabled. This did not work.
The KB article: How to disable TLS 1.0 or 1.1 in the registry or using IIS Crypto in Orion Servers (solarwinds.com) says to create a subkey of Server for each & this worked fine.
The help pane in Deployment Health needs to be updated with the above guidelines.
What the Help Dialog Should Say |
---|
Check if TLS 1.0 or 1.1 is Disabled |
What went wrong TLS 1.0 or TLS 1.1 is enabled. For security issues these protocols should be disabled. What you can do Disable TLS 1.0 and 1.1 via the Registry - Use the Windows Registry Editor to navigate to the following keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server - Note: You may need to create the
TLS 1.0 , TLS 1.1 , and Server registry keys.
- Create a new DWORD (32-bit) Value in each called
DisabledByDefault - Create a new DWORD (32-bit) Value in each called
Enabled - Set the value of
DisabledByDefault to 1 - Set the value of
Enabled to 0 - Restart the computer.
Related KB articles |