Silent installation

Choose a silent installation using the System Manager command-line interface (CLI) to create configuration and secrets files, encrypt/decrypt secrets files, and install or uninstall components. This method is useful for large-scale deployments, and it enables easy reinstallation with minor configuration adjustments using the config file, streamlining the process for quick modifications.

Here's why you might consider a silent installation:

  • Efficiency: It speeds up the installation process by skipping manual prompts and interactions when deploying software across multiple systems.

  • Consistency: It uses predefined settings to create a standardized deployment across systems.

  • For headless systems: If you're working with systems without a graphical user interface (GUI) or in a headless environment, silent installations allow for installations without the need for user interaction.

  • Customization: Tailor installations to your specific environment requirements by editing the command-line parameters or configuration files.

Before proceeding, keep these points in mind:

  • Silent installations may need specific configurations. Make sure that you have the necessary details to successfully install the product.

  • It's important to check logs in Seq if any errors occur. The command prompt window provides basic information, but see the Seq logs for troubleshooting.

  • You need to have a good understanding of the CLI to choose this installation method.

To use the CLI for an installation, the following prerequisites apply:

  • Configured Nintex RPA server.

  • Microsoft SQL Server Management Studio on the Nintex RPA Server.

  • MSSQL Server 2016 or later installed on a remote server.

  • Ensure that you have access to the server hosting the MSSQL database and that you have full credentials, including usernames and passwords, for this database.

    Establish an open connection between both servers to ensure optimal functionality.
  • The Nintex System Manager executable (NintexSystemManagerSetup.exe) installed.
  • The installation bundle zip file (e.g., nintex-rpa-server-23.11.0-full.zip).
  • (For TLS/SSL installation) The certificate files, such as the Personal Information Exchange file (e.g., kryonaws_full_chain.pfx).
    • We support different certificate file options: PFX (PKCS#12), CERT, KEY, and PEM files. Make sure you have the necessary files for your environment and ensure that each server in a multi-server installation has a certificate installed.
  • Run Powershell as an administrator to execute any commands.
Before proceeding with the CLI installation, ensure that you have run the System Manager executable file (NintexSystemManagerSetup.exe). This step is necessary to set up the required configurations and dependencies for a successful CLI installation.

The steps below show the order an installation must follow. See the full reference to commands and arguments, with descriptions and examples, in the CLI Commands table below. The command syntax is nintex-sysmgr-cli <command> <arguments>.

  1. (Optional) Store the installation bundle and Nintex System Manager executable file in the same directory. While this step is optional, it can help with easier management. You can do this by specifying the destination directory using the appropriate command arguments.

  2. Run PowerShell as administrator.

  3. Navigate to the folder that contains the Nintex System Manager executable (NintexSystemManagerSetup.exe).

  4. Run the configTemplate command to generate a config.prod.properties.json file.

  5. Edit the config.prod.properties.json file as required, referring to the list of parameters and their descriptions. Make the necessary changes based on your environment's requirements.

  6. Run the secretsTemplate command to generate a config.prod.properties.secured.json file.
  7. Edit any secrets you want to change and set the relevant secrets for remote third parties, referring to the list of parameters and their descriptions. By default, all passwords are set to a random string that you can change to human-readable passwords. Changing the passwords for third-party applications makes it easier to remember when you log into their user interface.

  8. Run the encrypt command to create an encrypted secrets.zip file.

  9. (Optional) Use the --remove argument to delete the decrypted secrets JSON file after encryption for security. If you don't, you'll receive a prompt to delete the decrypted secrets file, which you can recreate using the decrypt command.

  10. (Optional) Run the validate command to perform data validations.
  11. Run the install command to perform the installation using the bundle, edited configuration file, and encrypted secrets files.

When using the install command (--command=install), only the all-in-one server type is available.

In the command examples listed below, the nintex-sysmgr-cli, installation bundle zip file, config.json, and secrets.json files are in the C:\sysmgr directory. You can use any directory you want but edit the commands below to match your environment.

The home directory path is what the Nintex System Manager executable uses as the working directory and is where the components are installed.

Command syntax: nintex-sysmgr-cli <command> <arguments>
Command Arguments Example and Description
--command=configTemplate
  1. --h - home directory path
  2. --z - zip bundle path
  3. --d - destination to save the config template file (with file name)
Copy 
nintex-sysmgr-cli --command=configTemplate --h=C:\nintex --z=C:\sysmgr\nintex-rpa-server-23.11.0-full.zip --d=C:\sysmgr\config.json
The config.json file generated by this command contains values used to install components and connect to the various servers required for installation. Edit the config.json file for your environment. Other default values are preconfigured for you.
--command=secretsTemplate
  1. --h - home directory path
  2. --z - zip bundle path
  3. --d - destination to save the secrets config template file (with file name)
Copy 
nintex-sysmgr-cli --command=secretsTemplate --h=C:\nintex --z=C:\sysmgr\nintex-rpa-server-23.11.0-full.zip --d=C:\sysmgr\secrets.json
The secrets.json file generated by this command contains connection credentials for the various servers and components in plain text. Edit secured.config.json credentials as required for connections to 3rd party servers like your MSSQL server.
--command=encrypt
  1. --h - home directory path
  2. --f - unencrypted secrets file
  3. --d - destination where to save the encrypted secrets file (with file name)
  4. --remove or --rm - delete decrypted secrets file
Copy 
nintex-sysmgr-cli --command=encrypt --h=C:\nintex --f=C:\sysmgr\secrets.json --d=C:\sysmgr\secrets.zip --secrets-pass-env=SYSMGR_SECRETS_PASS

This command encrypts your JSON secrets file using the environment variable you set up earlier. For security purposes, we recommend deleting the JSON secrets file after the encrypted file is generated, using the --remove argument.

Copy 
nintex-sysmgr-cli.exe --command=encrypt --secrets-file=C:\sysmgr\secrets.json --dest-file=C:\sysmgr\secrets.zip --remove
--command=decrypt
  1. --h - home directory path
  2. --f - encrypted secrets zip file
  3. --d - destination where to save the decrypted secrets file (with file name)
Copy 
nintex-sysmgr-cli --command=decrypt --h=C:\nintex --f=C:\sysmgr\secrets.zip --d=C:\sysmgr\secrets.json --secrets-pass-env=SYSMGR_SECRETS_PASS
The decrypt command uses the same environment variable as the encrypt command to decrypt the secrets zip file.
--command=validate
  1. --z - zip bundle path
  2. --s - server type
  3. --external-config - config file
  4. --f - encrypted secrets zip file
  5. --output - log the output
Copy 
nintex-sysmgr-cli --command=validate --z="C:/sysmgr/nintex-rpa-server-23.11.0-full.zip" --s=allInOne --c="C:/sysmgr/config.json" --f="C:/sysmgr/secrets.zip" --output
--command=install
  1. --h - home directory path
  2. --z - zip bundle path
  3. --s - server type
  4. --c - config file
  5. --f - encrypted secrets zip file
Copy 
nintex-sysmgr-cli --command=install --h=C:\nintex --z=C:\sysmgr\nintex-rpa-server-23.11.0-full.zip --s=allInOne --external-config=C:\sysmgr\config.json --secrets-file=C:\sysmgr\secrets.zip --secrets-pass-env=SYSMGR_SECRETS_PASS
The install command uses the previously generated and edited files (config template and secrets template), and the installation bundle zip file, to install the product and components. All output is logged to Seq. The only currently supported server type is all-in-one.
--command=uninstall
  1. --h - home directory path
  2. --z - zip bundle path
  3. --s - server type
  4. --wipe - should wipe all data (backups, cache, etc.)
Copy

Regular Uninstall Package

nintex-sysmgr-cli.exe --command="uninstall" --s="allInOne"
Copy
Uninstall Wipe package
nintex-sysmgr-cli.exe --command="uninstall" --wipe --s="allInOne"

To uninstall using the CLI, you have two options:

  • Regular uninstall: This option removes the product assets, but cache files will remain. If you want to reinstall, the product uses the previously stored data.

  • Uninstall with wipe: This option removes all product data.

    Data in remote databases and Seq are not removed automatically. For instance, Aerobase data in the database must be manually deleted.

When you use directories containing a space such as C:\sysmgr home folder\subfolder\file name.txt, you must enclose it in inverted commas, for example "C:\sysmgr home folder\subfolder\file name.txt".

A: You can cancel the installation in PowerShell like you do with any script by pressing CTRL + C. If that fails, you can stop the Nintex System Manager Agent Windows service, which will cancel the installation.

To stop a Windows service:

  1. Press Win + R to open the Run dialog.

  2. Type services.msc.

  3. Click OK.

  4. Find the Nintex System Manager Agent Service in the Services list.

  5. Right-click on the service.

  6. Click Stop from the context menu.

A: You can follow the steps in this topic from the beginning, reconfigure values in the configuration template, and then reinstall.

A: After completing the System Manager installation, proceed with the installation of the Clients (Studio and Robot). Once the client installation is complete, test the products by launching and interacting with Console Plus.