Disabling TLS 1.0 in the environment breaks Task Management functionality

Products

• IT Management Suite
• Client Management Suite

Issue/Introduction

Disabling TLS 1.0 in the OS for Task Servers breaks Task Management functionality, even with TLS 1.0 unchecked in the Symantec Management Platform (SMP) console.

Cause

Usually caused by encryption protocols and/or algorithms not being set correctly in the environment.

Resolution

This issue is caused by configuration issues in the environment, and not with the SMP software.

Task communications have three components and the issue may be at more than one:

• The Server running the SMP software
• Systems operating as Task Servers
• The individual agents

To better understand the cause, load the Schannel logging on the Notification Server and compare the information with that from a Task Server. If there is no disparity, also check one of the Agents reporting to the Task Server.

• Enable Schannel event logging in Windows and Windows Server
• Microsoft documents referencing several of the event that might be reported

Use IISCrypto from Nartac software to make changes to Cipher Suites.

Additional Information

Similar KBs:

After moving from HTTP to HTTPS - no Site Server Task Servers are able to register 

New client machines can't register when only TLS 1.2 is enabled on the SMP server. COM error: An existing connection was forcibly closed by the remote host (0x80072746) 

Unable to register to a Task Server if only TLS 1.2 is enabled (Uses IISCrypto to make changes to Cipher Suites)

The client and server cannot communicate. TLS version mismatch