Announcement!
This is a notification for product news or an alert. If you have a question, please start a new discussion

ALERT: Changes to SafeX3 Console in 2023 R2

This article provides an overview of changes in the Installation process in 2023 R2 when compared to previous Releases.

Powershell SQLServer module version

Since 2022 R4, Powershell and its "SQLServer" module is a pre-requisite for installing or upgrading.

As of 2023 R2, the version of SQLServer Module required by the Powershell installation has now been upgraded to 22.1.1.

To install the SQLServer Module:

Run a Powershell in "Run as Administrator" mode.

If you are upgrading from 2022 R4 or higher, an earlier version of the SQLServer Module will have been installed, so please un-install that version using

pwsh -Command "Uninstall-module SQLServer -Force -Verbose"

before installing the updated version

pwsh -Command "Install-Module -Name SqlServer -Scope AllUsers -Force -RequiredVersion 22.1.1"

The alternative is to use the -AllowClobber option, and overwrite the old version

pwsh -Command "Install-Module -Name SqlServer -AllowClobber -Scope AllUsers -Force -RequiredVersion 22.1.1"

Runtime Connection Security

Two new security settings for the runtime connection have been added to the Sage X3 Management Console in 2023 R2:

Connection Encryption

Specifies whether the connection to the database is TLS encrypted. If this is enabled and TrustServerCertificate is set to no, SQL Server will require a valid trusted certificate chain. You can install the certificates through a PowerShell script that the Console will provide (Action menu).
If TrustServerCertificate is set to Yes, SQL Server will trust the connection by default and no additional certificate is needed.

Trust server certificate

You may set this option to 'True' to bypass the TLS/SSL certificate chain validation check for the SQL Server database connection, if you have chosen to implement encryption.
In this case, the connection will be trusted by default.
When this is set to 'No', the certificate chain will be controlled by SQL Server and will require valid certificates to be installed.
The 'No' value is recommended on production instances for maximum security. If your certificate chain is not valid, SQL Server will issue an error stating that the certificate chain is not trusted.

SQL Server Certificate Creation script

To support the new "Trust server certificate" setting, a new Action, "Save SQL Server Certificate Creation Script" has been introduced.

Please bear in mind that SQL Server will need to be configured to take advantage of these new settings.

** Additional information is available in the Online Help **