Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 47723 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Windows server 2019 standard

Judcom

Has anyone been able to install PureMessage on Windows server 2019 (standard)?

The latest version of Sophos PureMessage for Exchange can not connect to SQL server (neither SQL server express bundled, or SQL Server Standard edition 2014) on Windows 2019 standard during PureMessage setup/installation on the server.

The message is:

"Unable to connect to "[hostname]". Please ensure that the selected SQL Server instance is available and that you have the access rights to connect to it."

I have checked all the connections, and SQL server is running and receiving connections. The SQL server is on the same server as the PureMessage installation (localhost).

Is there is preview version that might work with Windows Server 2019?



This thread was automatically locked due to age.
  • 0

    I played a bit with the installer. Turned out that the installer uses an application named DBAdmin with which the database is accessed. This application uses the native ODBC drivers. While creating the connection string to the database, OLEDB wants to use parameters that are used by TLS 1.0 and/or TLS 1.1. Both protocols are by default disabled on Windows Server 2019. Enabling them allowed me to install PureMessage on Windows 2019.

    If you want to try this path, then enable the protocols in the registry:

    for TLS 1.0:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]
    "Enabled"=dword:00000001
    "DisabledByDefault"=dword:00000000
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]
    "Enabled"=dword:00000000
    "DisabledByDefault"=dword:00000001
     
    and for TLS 1.1:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
    "Enabled"=dword:00000001
    "DisabledByDefault"=dword:00000000
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server]
    "Enabled"=dword:00000001
    "DisabledByDefault"=dword:00000000
    After this, the installer runs without any issues.
  • +1

    I used Nartac Software - IIS Crypto to set TLS to 1.0. TLS 1.1 did not solve the issue.

  • 0 in reply to Judcom

    I realise this is not a supported solution, was there anything else that need changing to enable Puremessage to install on Server 2019? I have enabled both tls 1.0, 1.1 and 1.2, the installation still fails on the database selection due to not being able to connect. I see that the SOPHOS instance has been created and can be access via sql management console, but not by the installer.

     

    It seem strange that Sophos are no longer supporting on premise installations on the most recent Server version, I presume like all other vendors they want everything cloud based.

  • 0 in reply to Rob Jones

    Hi  

    Unfortunately, it is not supported as of now. Please check this article for the systems supported for Puremessage. Also, kindly refer this article which provides information of platforms and operating systems supported by PureMessage.  

    Shweta

    Community Support Engineer | Sophos Technical Support
    Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
    The New Home of Sophos Support Videos! - Visit Sophos Techvids
  • 0 in reply to Shweta

    I realise this is not supported, I was asking those that had already got it running successfully on Server 2019.

  • 0 in reply to Rob Jones

    As in the above post, It worked fine for me after I set TLS 1.0.

    Stock Windows Server 2019 Standard, Install .NET etc and enable TLS 1.0. It should work.

Unfiltered HTML