Review the pre-installation checklist

Ensure that you have reviewed, understand, and completed all of the sections in this part of the Quick Start Guide.

Review system requirements

The latest system requirements are included in the Nintex RPA LE Release Notes. Be sure to review the system requirements for your application and version.

Note: System requirements are subject to change without notice. Be sure to apply all critical updates and service packs issued by Microsoft® for your operating system. To obtain these updates, visit Microsoft's online Windows® update service.

Review domain requirements

Nintex RPA Central must be installed as follows for authentication and security purposes. If installing on a computer that is not connected to a domain, the installation will fail.

  • All machines with a Nintex Bot and Nintex RPA Central component must be joined, part of, and connected to an Active Directory Domain Services domain and not as a workgroup.
  • Machines with a Nintex Bot and Nintex RPA Central 2.6.0 or below component must be deployed in the same domain. Machines with a Nintex Bot and Nintex RPA Central 2.7.0 or above component can be deployed in multiple properly-trusted domains. Installing Nintex RPA LE in multiple properly trusted domains is particularly beneficial if you are installing Nintex RPA Central on a parent domain and have users in child domains. This type of domain architecture is common at companies that have multiple locations or branches that manage users at the location or branch level. To add users from trusted domains or add and validate users from unknown domains so that they are known, go to Add a user.
  • If remote or off-site, the computer needs to be connected to a domain via a VPN and the DNS and AD servers must be accessible in order for Nintex Bot and Nintex RPA Central to be installed and the license be activated. To add additional VPN IP addresses to the configuration and ensure that the connection is successful, go to Verify Machine Name and Configure Nintex Bot VPN and Nintex RPA Central Firewall IP Addresses.
  • The user account on the machine where the Nintex Bot resides must have at least standard user permissions to the Nintex RPA Central machine.

Important: In a trial deployment, the machine needs to be on a domain during installation and have access to a domain during activation. During deployment where Nintex Bot and Nintex RPA Central are installed on the same machine, a self-signed certificate will be automatically generated and installed onto the machine. Once activated, the machine does not need access to the domain for Nintex Bot and Nintex RPA Central to function. In this setup where Nintex RPA Central will only run on localhost and will not be accessible by other computers, communication to the domain server is not required (such as VPN), as the certificate will not be required to be verified by a Certificate Authority. The use of self-signed certificates outside of development and testing environments is forbidden in most organizations by policy.

If your Active Directory supports domain distributed machine certificates, the Nintex RPA Central machine must be connected to the domain (directly or via VPN) to request a certificate from the Certificate Authority. Once the certificates exist, there is no need to have communication to the domain, either in localhost or machine certification.

Nintex RPA Central uses Windows Authentication and Active Directory to verify the identity of users. This creates a trusted and seamless sign-in experience without prompting users with a sign-in screen while

  • Starting the Nintex RPA Central browser-based application from a domain joined computer.
  • Starting the Nintex Bot desktop-based application on a domain-joined computer linked to a trusted Nintex RPA Central instance.

Nintex RPA Central uses Windows Authentication, Active Directory, and Windows Domain DNS services to verify the identity of Nintex Bot installed on domain-joined computers, preventing third-party applications on the network from acting as a known bot and compromising data from Nintex RPA Central.

Check your firewall settings

Ensure that your firewall settings are prepared for use with Microsoft Windows 10.

  1. Navigate to System and Security > Windows Defender Firewall > Advanced settings.
  2. Click Inbound Rules on the left pane.
  3. Click New Rule on the right pane.
  4. Click Port and then click Next.
  5. Select TCP and, based on the format of your Nintex RPA Central URL, type the following number in the Specific local ports field.
  6. Note: The port number can be different depending on your machine and network environment. Consult with your Network Administrator.

    • If your Nintex RPA Central URL ends in a number, such as 8080, type that number.
    • If your Nintex RPA Central URL does not end in a number, type 443.
  7. Click Next.
  8. Select Allow the connection and click Next.
  9. Select Domain.
  10. Ensure Private and Public are not selected.
  11. Click Next.
  12. Type a rule Name, and optionally, type a rule description.
  13. Click Finish.
  14. Click Outbound Rules on the left pane.
  15. Complete steps 4-13 again.

Obtain a valid license

To complete the installation, have your license key ready. The license key is emailed to you after you purchase Nintex RPA Central and is in the following format: XXXXX- XXXXX- XXXXX- XXXXX- XXXXX

Please contact Nintex Support with any questions.

Download the latest release

Ensure you download the files that are correct for your licensing needs available on the Product Releases page.

Note: Nintex customer registration is required to use the Product Releases download page.
Ensure you review the Release Notes for your release for important release information.

Next step:

Install Nintex RPA Central and activate license key