RPA server GUI installation

Currently, you cannot uninstall the RPA Server through the System Manager's GUI installer. However, you can uninstall using the Uninstallation process.

Nintex System Manager provides a comprehensive solution for managing the installation of RPA.

Jump to:

Perform the following actions before starting the installation:

  • Create a restore point for the server VM.

  • Ensure that you have installed the latest version of Nintex System Manager (Nintex RPA) (NintexSystemManagerSetup.exe).

  • Check server requirements according to Nintex RPA server.

  • Ensure that the latest version of the RPA installation bundle zip file (e.g., nintex-rpa-server-<latest version>-full.zip) is ready and available for use during the upgrade process.

  • Verify that no conflicting versions of .NET are present in the PATH environment variable. See Known issues below.

  • Database-related items:

    • Ensure the user account that will run the installation process is able to log in to the MSSQL Server.

    • The user account should have the Server role sysadmin for the MSSQL Server.

      If the RPA and MSSQL servers are installed on different machines, you must establish an open connection between both servers to ensure optimal functionality.

  • Authentication-related items:

    • (For TLS/SSL installation) Different certificate file options, such as Personal Information Exchange file (e.g., kryonaws_full_chain.pfx or PKCS#12), CERT, KEY, and PEM files, are supported. Ensure you have the necessary files for your environment and that each server in a multi-server installation has a certificate installed prior to the upgrade process.

Make sure you have the latest System Manager installed for best performance and access to new features.

The primary method of installing RPA is through System Manager, which provides a user-friendly graphical interface. This is the recommended method for most users.

To install System Manager, follow these steps:

  1. Locate and run the System Manager executable file: NintexSystemManagerSetup.exe.

  2. Click Install.

  3. (Optional) Select the Run NintexSystemManager checkbox to launch the application immediately after installation.

  4. Click Finish.

After installing System Manager, you can run it. It will guide you through the RPA installation process. The System Manager GUI guides you through the following steps:

Page Description
Welcome Page to select the ZIP file that you want to install.
Setup Page used to enter server details and specify the desired destination folder.
System check Verifies that your system meets the requirements for installing the software.
Configurations Page to configure the preferred connection option and specify the desired port.
Optional features Page to enable or disable key features.
Third parties Page to configure settings for various external components used in the system.
Install Page that shows the progress of the installation process.
Completion Indicates the successful completion of the installation process. Choose to launch the System Manager immediately or exit the installer.

When System Manager starts, do the following:

  1. Drag the RPA installation bundle ZIP (.zip) file into the designated box or select the ZIP file by clicking Select file.

  2. Click Start to begin the installation process.

> Next step: Setup

Following are recommended actions after you have performed the installation:

  1. Proceed with the Client installation (Studio and Robot).

  2. Run the Dynamic Advanced Commands installer on each client machine (Studio and Robot).

    This step is only required the first time after installation. After installation, use the distribution system for updates.

  3. Log in to the Admin Tool to Activate your RPA license and manage the Nintex RPA platform.

  4. Log in to the Console Plus to create and manage robots, tasks, and triggers.

  5. To validate Single Sign-On for Client Server Authentication, log in to the client machine using an Active Directory user account that has been imported into Aerobase (and synchronized in the Admin tool). Start a client application (Studio or Robot), and if the setup is successful, it will log in automatically without requiring manual credentials.

  6. (Optional) Change configuration parameters: If you need to make changes like enabling or disabling TLS, simply rerun the System Manager installation with the same RPA bundle zip file and select Repair. There is no need to uninstall the previous version.

.NET Core path conflict

  • Issue: When installing the RPA Server, the process may fail at the RPA Services step due to the Nintex Server - Authentication Service being stuck in a Paused state. This is typically caused by a conflict with the .NET Core installation path.

  • Explanation: The failure occurs because the installation process installs .NET Core 6 in C:\Program Files\dotnet. However, if the PATH environment variable has an entry for C:\Program Files (x86)\dotnet before the correct path, the system cannot find the installed .NET Core version. This conflict may occur on virtual machines (VMs) that come with .NET already installed in the wrong location and architecture (x86/x64).

  • Workaround: To resolve this issue, follow these steps:

    1. Check that .NET Core 6 is installed in C:\Program Files\dotnet.

    2. Remove C:\Program Files (x86)\dotnet from the PATH environment variable. To do this:

      1. Open System settings.

      2. Click Advanced system settings.

      3. Click Environment Variables in the Advanced tab.

      4. Select Path from the System variables.

      5. Click Edit.

      6. Delete the entry C:\Program Files (x86)\dotnet.

    3. Restart the machine.

    4. Run the installation or upgrade again.