Nintex System Manager release notes

Latest release: Nintex System Manager 2.1.0

As part of: Nintex RPA release 26.6

Release date: June 2026

The latest release expands on the previous release with new features and enhancements.

  • When configuring the user account to your database, the account no longer requires the sysadmin role. The db_owner role is sufficient to perform a schema upgrade during the installation and upgrade processes. This change provides greater flexibility by allowing more database user accounts to be used, as database owners are not necessarily system administrators and vice versa.

For new features, enhancements and bug fixes to Nintex RPA, see Nintex RPA release notes.

Download link Installation guide
Download the latest version from Nintex Customer Central (login required).

Nintex System Manager installation guide

Previous releases

Issue More details

When you restart an upgrade process after it was unsuccessful, the Repair button is displayed.

If an upgrade process was interrupted or unsuccessful, Nintex System Manager displayed a Repair button. This button has now changed to Upgrade.
Auto login is not working when SSO and User Federation options are used. Nintex RPA version 25.11 uses an upgraded Keycloak version. This in turn requires Java SE 17+. AES encryption type is now used to maintain compatibility with Java SE 17+.
After installing or upgrading the Nintex RPA server on a virtual machine, conflicting information appears when starting Nintex RPA, particularly if the upgrade involved moving from .NET Framework 4.7 to 4.8. In such cases, the system incorrectly reported that it is still running .NET Framework 4.7 even though it has already been upgraded to 4.8. As a best practice, the virtual machine should be restarted after installing or upgrading Nintex RPA. The latest version now includes a prompt to remind users to restart the virtual machine.

  • As a precautionary measure, you will not be able to cancel the installation or upgrade process after the Stopping services step (during installation) or the Backup step (during an upgrade). The following is an example of this:

  • If you are upgrading from RPA v23.11 or earlier, Nintex System Manager will now retrieve the parameters you used previously and automatically populate the same fields to ease your upgrade experience.

  • If you do not meet the minimum memory requirements, Nintex System Manager will now raise a warning and allow you to proceed with the installation or upgrade process instead of preventing it:

    • During installation: A warning will be raised if your available memory is within 10% below the minimum requirement.

    • During upgrade: If you do not meet either the minimum disk or memory requirement but your existing installation is working, a warning will be raised and you will be able to proceed with the upgrade process.

  • Nintex System Manager can now detect whether a previous installation or upgrade was performed and will adjust its behavior accordingly:

    • If your installation failed and you try to install again, you will see the Repair button.

    • If your upgrade failed and you try to upgrade again, you will see the Upgrade button.

  • Better handling to prevent installation and upgrade failures related to Security Support Provider Interface (SSPI):

    • If you select Without SSL/TLS in the Security protocols field in the Security Options section of the Configurations page, and SSPI in the Authentication Method field in the MSSQL (Database Server) section of the Third parties page, Nintex System Manager will no longer attempt to locate CA certificates.

    • If you enable Encrypted database connection, and set the Authentication Method to SSPI in the MSSQL (Database Server) section of the Third parties page, Nintex System Manager will now allow the installation or upgrade to proceed.

Issue More details
At the Install step, the installation or upgrade will fail at Aerobase service stage.

An error will occur when the testuser user is not found in the Aerobase environment. This will cause the process to fail if the testuser user is entered in the Username field during the Keycloak configuration step on the Third parties page.

An error will occur if you configure the following settings in the MSSQL (Database Server) section on the Third parties page:

  • Encrypted database connection: Switched to On

  • Authentication Method: SSPI

  • Upgrade your Nintex RPA easily with our new Nintex System Manager upgrade feature. It's now the primary tool for upgrading your product, replacing the previous upgrade methods. Use the Nintex System Manager to effortlessly configure and install updates through the user interface.

 

  • The System Manager is now available as the primary tool for installing the product, and replaces the previous installation tools. Use the System Manager to configure and install the product using the user interface.