Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Using TLSv1.1 or TLSv1.2 for communication between MSSQL server and OfficeScan

    • Updated:
    • 8 Dec 2017
    • Product/Version:
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • N/A N/A
    • Windows 10
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2003 32-Bit
    • Windows 2003 64-Bit
    • Windows 2003 Datacenter 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Server R2
    • Windows 2003 Standard 64-bit
    • Windows 2008 32-Bit
    • Windows 2008 64-Bit
    • Windows 2008 Datacenter
    • Windows 2008 Datacenter 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 2012
    • Windows 2012 Datacenter R2
    • Windows 2012 Enterprise
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Essential R2
    • Windows 2012 Server Essentials
    • Windows 2012 Server R2
    • Windows 2012 Standard
    • Windows 2012 Standard R2
    • Windows 2016
    • Windows 7 32-Bit
    • Windows 7 64-Bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
Summary

This article discusses how to check the TLS v1.1 and 1.2 support capability of the OfficeScan server with a remote MSSQL server as its database.

Details
Public

To check for TLS v1.1 and 1.2 support capability:

  1. Check if TLS v1.1 and 1.2 protocol are supported or not:
    1. On the OfficeScan server, create an empty text document on the Desktop.
    2. Modify the file extension to ".udl".
    3. Double-click the file.
    4. Go to the Provider tab and click SQL Server Native Client 11.0.
    5. Go to the Connection tab and input the remote SQL server address, User name, and Password.

      Data Link Properties

    6. Click Test Connection.

      If the error message shows "Encryption not supported" on the client, TLS v1.1 and 1.2 may not be supported on the server.

      SQL Server Native Client Data Link Error

  2. Follow the procedures in the following article to update the Windows OS: Communication between OfficeScan (OSCE) and Smart Protection Server (SPS) using TLSv1.2.
  3. Update the OfficeScan server to OfficeScan XG SP1.
  4. Update the Microsoft SQL Server 2012 Native Client to at least build 11.3.6538.0. It can be downloaded from the following page: Microsoft® SQL Server® 2012 Native Client - QFE.

    Microsoft SQL Server 2012 Native Client

  5. Verify if the connection between OfficeScan and MSSQL server is working or not.
  6. If the issue persists, please contact Trend Micro Technical Support for assistance.
Premium
Internal
Rating:
Category:
Configure; SPEC
Solution Id:
1118930
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.