Skip to content

Install on Windows

The Windows sink runs as a Windows Service and survives reboots automatically. It supports self-updating — when your administrator publishes a new version, the service downloads and installs the update without manual intervention.


  • Windows 10 / Windows Server 2016 or later
  • The provided installer (nexomatic-remote-setup-windows-x86_64.exe), which bundles its runtime — no Python installation needed
  • Network connectivity to the Hub host and port (outbound TCP — no inbound rules needed)
  • Administrator privileges on the machine
  • A node created on the Nodes screen, with its Client ID and Client Secret (see Node Credentials)

The recommended approach is to use the Inno Setup installer provided by your administrator.

Double-click the .exe installer and follow the wizard. You will be prompted for:

FieldValue
Hub HostHostname or IP of the Hub (e.g. hub.example.com)
Hub PortPort the Hub listens on (default 50051)
Hub TLSCheckbox — encrypt the gRPC connection (required for the platform’s public Hub)
Client IDThe node’s Client ID from the Nodes screen
SecretThe node’s Client Secret (shown once when the node is created)
Script Root FolderOptional folder with your own shell scripts
Authentication Methodclient_credentials, entra_id, google, github, or none
Tenant IDYour tenant id
Update Base URLOptional self-update channel (e.g. https://releases.example.com/nexomatic-sink)
Node Tenant UUID (optional)Pin the sink to a single tenant
Node Tenant Secret (optional)Node registration secret

Open Services (services.msc), find Nexomatic Remote Sink, and confirm it shows Running.

You can also check from PowerShell:

Terminal window
Get-Service -Name NexomaticRemoteSink

Within a few seconds the sink should appear as ONLINE on the Sinks screen in Nexomatic.


If you need to install without the wizard (e.g. in a scripted deployment), follow these steps.

Copy the sink files to a directory, for example C:\Program Files\Nexomatic Remote Sink\.

The service reads its configuration from the Windows Registry under:

HKLM\SYSTEM\CurrentControlSet\Services\NexomaticRemoteSink\Environment

Set the following values (type REG_SZ):

Terminal window
$svcKey = "HKLM:\SYSTEM\CurrentControlSet\Services\NexomaticRemoteSink\Environment"
New-Item -Path $svcKey -Force | Out-Null
Set-ItemProperty -Path $svcKey -Name HUB_HOST -Value "hub.example.com"
Set-ItemProperty -Path $svcKey -Name HUB_PORT -Value "50051"
Set-ItemProperty -Path $svcKey -Name HUB_TLS -Value "true"
Set-ItemProperty -Path $svcKey -Name CLIENT_ID -Value "<node-client-id>"
Set-ItemProperty -Path $svcKey -Name CLIENT_SECRET -Value "<your-secret>"
Set-ItemProperty -Path $svcKey -Name AUTH_METHOD -Value "client_credentials"
Set-ItemProperty -Path $svcKey -Name ROOT_FOLDER -Value "C:\Program Files\Nexomatic Remote Sink"
Set-ItemProperty -Path $svcKey -Name TENANT_ID -Value "<your-tenant-id>"
Set-ItemProperty -Path $svcKey -Name UPDATE_BASE_URL -Value "https://releases.example.com/nexomatic-sink"

CLIENT_TYPE defaults to REMOTE when unset. The tenant-pinning values (TENANT_UUID, TENANT_SECRET) are optional.

Terminal window
sc.exe create NexomaticRemoteSink binPath= "C:\Program Files\Nexomatic Remote Sink\sink_service.exe" start= auto
sc.exe failure NexomaticRemoteSink reset= 60 actions= restart/5000/restart/5000/restart/5000
sc.exe failureflag NexomaticRemoteSink 1
sc.exe start NexomaticRemoteSink

When your administrator publishes a new version, the Hub signals the running service to update. The service will:

  1. Finish any in-progress tasks
  2. Download the new installer silently
  3. Apply the update and restart

No manual action is required. The service will be briefly unavailable during the update (typically under 30 seconds).


Terminal window
# Stop
Stop-Service NexomaticRemoteSink
# Start
Start-Service NexomaticRemoteSink
# Restart
Restart-Service NexomaticRemoteSink
# View recent log entries (Event Viewer)
Get-EventLog -LogName Application -Source NexomaticRemoteSink -Newest 20

Run the uninstaller from Add or Remove Programs, or from PowerShell:

Terminal window
sc.exe stop NexomaticRemoteSink
sc.exe delete NexomaticRemoteSink
Remove-Item -Recurse "C:\Program Files\Nexomatic Remote Sink"

SymptomLikely causeFix
Service fails to startMissing or wrong credentialsCheck registry values with Get-ItemProperty
Sink shows OFFLINE in UICannot reach HubCheck firewall — outbound TCP to Hub host:port must be allowed
Tasks not runningCredential mismatchConfirm CLIENT_ID matches the node registered in Nexomatic
Update stuckInstaller running silentlyWait 60 seconds; if still stuck, manually restart the service