- 4 minutes to read

Step 7: Install the Generated Package

Use the generated ZIP bundle to create databases, configure IIS (if you install on Windows), install Core Services, and deploy selected agents. The current runtime entry point is Nodinite.Installer.Cli.exe. This is a .NET 10 based installer.

Before You Start

  • Complete the installation Prerequisites.
  • Extract the ZIP bundle.
  • Keep the folder structure intact after extraction.
  • Open PowerShell 7 with administrative privileges.
  • Run all commands from the bundle root folder.

ZIP bundle content

After extraction, the root typically contains:

  • InstallationMedia
  • one folder per server, for example localhost
  • Nodinite.Installer.Cli.exe

Per server folder, you get generated configuration input such as config.cli.json that the CLI consumes.
ZIP bundle with CLI
Example of the extracted ZIP bundle root with InstallationMedia, a server folder, and Nodinite.Installer.Cli.exe.

You do not need to unblock the ZIP bundle or any of its contents. The installer is signed and trusted by Microsoft Authenticode.

Review bundle files before execution

Before running installation commands:

  • Review config.cli.json values for paths, ports, and selected agents.
  • Verify SQL package paths and ZIP-related paths if placeholders are still present.
  • Keep the extracted structure unchanged so media paths resolve correctly.

CLI help and discovery

Use CLI help to inspect available commands:

.\Nodinite.Installer.Cli.exe --help
.\Nodinite.Installer.Cli.exe --version
.\Nodinite.Installer.Cli.exe install --help
.\Nodinite.Installer.Cli.exe deploy-environment --help
.\Nodinite.Installer.Cli.exe install-agent --help
.\Nodinite.Installer.Cli.exe uninstall --help
.\Nodinite.Installer.Cli.exe uninstall-agent --help
.\Nodinite.Installer.Cli.exe teardown-environment --help
.\Nodinite.Installer.Cli.exe validate --help
.\Nodinite.Installer.Cli.exe status --help
.\Nodinite.Installer.Cli.exe diagnose --help

Use this recommended workflow:

  1. Validate the package without changing the machine.
  2. Run a dry-run to check install/update actions.
  3. Deploy after validation and dry-run are clean.
.\Nodinite.Installer.Cli.exe validate --config .\localhost\config.cli.json
.\Nodinite.Installer.Cli.exe deploy-environment --config ".\localhost\config.cli.json" --dry-run
.\Nodinite.Installer.Cli.exe deploy-environment --config ".\localhost\config.cli.json"

Installation Progress
Example of installation progress output while the CLI configures the environment.

Config DB backup confirmation prompt

During deploy-environment, if the Configuration Database does not have a verified backup state, the CLI prompts for intent before applying schema changes.

The prompt offers these choices:

  • Back up now - the installer tries to create a verified backup and then continues.
  • Continue - proceed because you already have a verified backup.
  • Abort install - stop execution without applying changes.

Config DB backup confirmation prompt
Example of the CLI safety prompt shown when database upgrade is pending and a backup confirmation is required.

Use this prompt as an explicit safety gate in production environments.

Passing arguments when needed

You can provide secrets and connection strings using config values, command arguments, environment variables, or CLI prompts.

Common runtime overrides:

  • --database-connection-string <ConnectionString>
  • --agent-connection-string AgentType=ConnectionString
  • --agent-connection-string AgentType#Id=ConnectionString
  • --service-password <Password>
  • --oauth2-webclient-secret <Secret>
  • --oauth2-agentinstall-secret <Secret>

For prompt-required database values, you can also use environment variables such as:

  • NODINITE_DATABASE_CONNECTION_STRING
  • NODINITE_AGENT_<TYPE>_CONNECTION_STRING

For duplicate agent types, pass each connection string with AgentType#Id=ConnectionString.

Common CLI commands

Validate configuration file:

.\Nodinite.Installer.Cli.exe validate --config .\localhost\config.cli.json --strict-file-locks --output report.json --format json

Deploy environment:

.\Nodinite.Installer.Cli.exe deploy-environment --config .\localhost\config.cli.json --verbose

Install using the install command:

.\Nodinite.Installer.Cli.exe install --config .\localhost\config.cli.json --non-interactive

Install one agent:

.\Nodinite.Installer.Cli.exe install-agent --config .\localhost\config.cli.json --agent AzureLogicApps

Proxy overrides

If proxy behavior must be changed at execution time, pass proxy options on installer commands:

  • --proxy-mode <system|none|manual>
  • --proxy-url <Url>
  • --proxy-use-default-credentials or --proxy-no-default-credentials
  • --proxy-bypass-local or --proxy-no-bypass-local
  • --proxy-bypass <Pattern>

Important behavior notes

  • uninstall removes core services only.
  • teardown-environment removes agents first and then core services.
  • gMSA accounts do not require passwords.

Troubleshooting

Run with --verbose for deeper diagnostics:

.\Nodinite.Installer.Cli.exe deploy-environment --config .\localhost\config.cli.json --verbose

For deeper failure analysis, continue with Complete Installation Troubleshooting Guide.

Next Step