Hello all,
seems that SEC 5.5.1 is in the works already (though naturally I can't say when exactly later this year will be).
Christian
This thread was automatically locked due to age.
Hello all,
seems that SEC 5.5.1 is in the works already (though naturally I can't say when exactly later this year will be).
Christian
Sweaaaaaaat !!! :) Like you said, It's Friday morning :)
As usual ...
Some feedback.
I am logged as Domain Admin. After a very long time I had this on the install screen:
The command "CheckDBConnection -l" yields this :
C:\sec_551\ServerInstaller\CheckDBConnection>CheckDBConnection -l
Sophos Connectivity Verifier
5.5.1.955
Copyright 2000-2018 Sophos Limited. All rights reserved.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sophos Group. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.
TestDatabaseConnectionWithConnectionString 'Server=.\SOPHOS;Database=master; Timeout=3; Trusted_Connection=Yes;'
NewConnStr 'Server=.\SOPHOS;Database=master; Timeout=3; Trusted_Connection=Yes;;'
TestDatabaseConnectionWithConnectionString 'Server=.\SOPHOS;Database=master; Timeout=3; Trusted_Connection=Yes;Encrypt=yes;'
NewConnStr 'Server=.\SOPHOS;Database=master; Timeout=3; Trusted_Connection=Yes;Encrypt=yes;;'
(/) Operating system is ready to use TLS 1.2
(/) Installed .NET Framework supports TLS 1.2
Connection to the SQL Server established
(x) SQL Server instance does not support TLS 1.2
(x) SQL Server TCP/IP protocol detection failed
(/) There is a certificate installed that can be used with SQL Server
(/) SQL Server Native Client library supports TLS 1.2
Encrypted connection to the SQL Server cannot be established
Windows Server 2012 R2 - Standard Server - 6.3.9600.0 - 6 -
SOPHOS - 11.0.7462.6 - SP4-GDR -
Corindon WSUS
Client Library information:
sm - SQLNCLI11 - 11.0.7462
tcp - SQLNCLI11 - 11.0.7462
np - SQLNCLI11 - 11.0.7462
tcp - SQLNCLI11 - 11.0.7462.6
C:\sec_551\ServerInstaller\CheckDBConnection>
I still have both errors:
(x) SQL Server instance does not support TLS 1.2
(x) SQL Server TCP/IP protocol detection failed.
Both of these errors are wrong.
It was soooo easy to upgrade and maintain Symantec SEC. Why I have done that ultra stupid decision to migrate to something else ?
