Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Enable TLS 1.2 on Windows Server 2008

Enable TLS 1.2 on Windows Server 2008

Table of contents

Updated August 1, 2018

Overview

To enable Transport Layer Security (TLS) 1.2 on remote machines running Windows Server 2008 that are connected to the Orion Platform, you'll need to edit registry keys and change Windows security options.

Starting with Orion Platform 2017.3, Orion server support for Windows Server 2008 Orion was deprecated. This article applies to remote machines being monitored by the Orion server -- not the Orion server itself. Also, this information applies to Windows Server 2008, not Windows Server 2008 R2.

Environment

  • Windows Server 2008

Steps

SolarWinds strongly recommends that you back up your registry before making any edits to your system registry. You should only edit the registry if you are experienced and confident in doing so. Using a registry editor incorrectly can cause serious issues with your operating system, which could require you to reinstall your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

 

To enable TLS 1.2 on a Windows Server 2008 machine:  

  1. Log into the machine with Administrator privileges.
  2. Apply all available Windows updates.
  3. Restart the machine.
  4. Add registry keys for both Client and Server in the following path:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2 
    RegEdit1_2.png

 

  1. In the Local Group Policy Editor, navigate to Computer Configuration > Windows Settings > Local policies > Security Options.
  2. Enable the "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" setting.
  3. Force an update of the Group Policy on the machine by opening a command prompt and typing:
    cmd.exe: gpupdate /force

 

See the following links for reference:

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

Last modified

Tags

Classifications

Public