Our SQL DBAs are working to move most/all our SQL connections to SSL. They have asked if Adaxes can support this.
Hello,
Yes, it is supported. However, per Microsoft documentation SSL support in SQL was stopped starting with version 2016 and now TLS is used. For details, have a look at the following article: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-ver15.
For information on how to enable logging to an external MS SQL database, have a look at the following help article: https://www.adaxes.com/help/EnableExternalDatabaseLogging.
Thank you, yes, I did mean TLS. It looks like the communication is not using TLS. If we disable the ability on the SQL server to accept non-TLS connections will it start using that connection method?
Yes, that should work just fine.
Can the logging database be run on SQL 2019?
Dear Adaxes team, Please confirm if Adaxes 2019.1 support SQL server 2017 for logging database. Also suggest Adaxes steps to perform if we are migrating our logging database from SQL server 2012 to SQL server 2017
We're looking to migrate our Adaxes console to a new VM/Server, and we'd like to use Server 2022, and we want to verify that it will work before we stand the server up. Our current one is Windows Server 2016.
We are in the process of updating our Active Directory Domain Controllers to server 2022 and the Domain/Forest function level. Our concern is that we still have Adaxes ... version of Windows server for our DCs and the Domain/Forest function level of 2016?
The only reference I can find to running adaxes on server core is several years (6?) old. Has there been any update to supporting adaxes on Windows Server core? Thank you.