Windows Server 2016 and TLS 1.0, 1.1 removal

  • 23 November 2021
  • 2 replies
  • 613 views
Phil Seifert
Rank
Userlevel 7
Badge +21

Many companies are removing support for TLS 1.0 and TLS 1.1 from their servers, usually to enhance security.

It has been seen when using Windows Server 2016 there are issues when disabling these TLS versions and only TLS 1.2 is enabled.  This is encountered when using Microsoft OLE DB Provider for SQL Server and using the DB connection dialog from Configuration Editor to the profile database.

To remedy this, it is necessary to deploy a new driver from Microsoft on the servers:

 

Microsoft OLE DB Driver for SQL Server
  • This driver is needed for Alliance v14 HF24 (& higher) or Alliance v15.1 (& higher) when running on Windows Server 2016 to support TLS 1.2.
  • Earlier versions of Alliance do not support TLS 1.2 in the Astea Browser (Publisher)
  • Windows Server 2019 already supports this DB driver with TLS 1.2 and is not necessary to install.

There is an installation package supplied with Alliance v15.4:

\Setup\Tools\TLS-SQL-Provider\msoledbsql_18.1.0.0_x64.msi

 

 

2 replies

A
Rank
Userlevel 2
Badge +2

Are there issues for Astea V10 when disabling TLS 1.0, 1.1 or SSLV3?

Phil Seifert
Rank
Userlevel 7
Badge +21

Hi Anthony,

Yes, the Publisher does not support TLS 1.2.  This only comes as noted above in the post…

  • This driver is needed for Alliance v14 HF24 (& higher) or Alliance v15.1 (& higher) when running on Windows Server 2016 to support TLS 1.2.
  • Earlier versions of Alliance do not support TLS 1.2 in the Astea Browser (Publisher)

Reply


Terms & ConditionsCookie settings