This guide provides simplified step-by-step instructions for installing and running a DeNet Datakeeper Node on Windows systems.
- Quick Start Installation
- Configuring Node
- Running Your Node
- Running Multiple Nodes
- Advanced: Windows Service Setup (Optional)
- Reinstalling Your Node
- Useful Commands
# Download node executable
curl -LO https://github.com/DeNetPRO/Node/releases/download/v4.0.1-rc13/denode-windows-amd64.exe
# Create directory for the node executable and copy it
mkdir -Force C:\denet
Move-Item -Path "denode-windows-amd64.exe" -Destination "C:\denet\denode.exe"
Set-Location "C:\denet"
# Run the node (this will prompt for configuration)
.\denode.exe- Visit https://github.com/DeNetPRO/Node/releases
- Download the appropriate binary for your system:
- For AMD64 architecture:
denode-windows-amd64.exe
- For AMD64 architecture:
- Move the downloaded file to your desired location
-
Using powershell:
mkdir -Force C:\denet Move-Item -Path "C:\path\to\downloaded\denode-windows-amd64.exe" -Destination "C:\denet\denode.exe" Set-Location "C:\denet"
-
Or using File Explorer
-
Before proceeding with the installation, you'll need to open PowerShell to execute the commands. Here are several methods to open PowerShell:
- Press the Windows key on your keyboard
- Type "PowerShell" in the search box
- Click on Windows PowerShell (not "PowerShell ISE")
- If prompted by User Account Control, click Yes to allow the app to make changes
- Press Windows key + R to open the Run dialog
- Type "powershell" and press Enter
- Alternatively, you can type "powershell.exe" and press Enter
- Open File Explorer
- Navigate to the folder where you downloaded the executable (e.g., C:\denet)
- Hold Shift and right-click in the empty space
- Select "Open PowerShell window here"
- This opens PowerShell directly in the folder where your executable is located
- Press Windows key + R
- Type "cmd" and press Enter
- In the Command Prompt window, type "powershell" and press Enter to switch to PowerShell
- Right-click on the taskbar and select Task Manager
- Go to the File tab and select Run new task
- Type "powershell" and check Create this task with administrative privileges if needed
- Click OK
Important Notes:
- Always run PowerShell as Administrator if you encounter permission errors during installation
- To run as Administrator, right-click on the PowerShell icon and select "Run as administrator"
- The PowerShell window should display a prompt like
PS C:\Users\YourUsername>indicating it's ready for commands
After initial setup of all configuration parameters, simply run:
cd C:\denet
.\denode.exeTo run in background:
$env:DENODE_PASSWORD="your_password"
Start-Process -FilePath ".\denode.exe" -ArgumentList "--address", "your_datakeeper_address", "--license", "your_license_number" -PassThruAfter the node is installed, you can proceed with the configuration
- Instructions are here
When running multiple DeNet Datakeeper Nodes on the same machine, each node needs its own configuration directory and unique parameters to avoid conflicts:
-
Create separate directories for each node:
# Create directories for different nodes mkdir -Force C:\denet-node1 mkdir -Force C:\denet-node2 Copy-Item -Path "C:\denet\denode.exe" -Destination "C:\denet-node1\denode.exe" Copy-Item -Path "C:\denet\denode.exe" -Destination "C:\denet-node2\denode.exe"
-
Configure each node separately:
# Configure first node Set-Location "C:\denet-node1" .\denode.exe # This will prompt for configuration # Configure second node Set-Location "C:\denet-node2" .\denode.exe # This will prompt for configuration
-
Run each node with unique parameters:
# Run first node in background Set-Location "C:\denet-node1" $env:DENODE_PASSWORD="your_password" Start-Process -FilePath ".\denode.exe" -ArgumentList "--address", "your_address_1", "--license", "license_1" -PassThru # Run second node in background Set-Location "C:\denet-node2" $env:DENODE_PASSWORD="your_password" Start-Process -FilePath ".\denode.exe" -ArgumentList "--address", "your_address_2", "--license", "license_2" -PassThru
-
Monitor processes:
# List all denode processes Get-Process denode # View logs for each node Get-Content -Path "C:\denet-node1\denode.log" -Tail 10 Get-Content -Path "C:\denet-node2\denode.log" -Tail 10 # Kill specific node by PID Stop-Process -Id <PID> # Kill all denode processes Get-Process denode | Stop-Process
Important: Each node requires its own unique license id. When configuring each node, make sure to use a different license number for each instance.
For automatic startup on boot:
-
Create a dedicated user (recommended):
# Create a new user account for the service New-LocalUser -Name "denet" -Password (ConvertTo-SecureString "password" -AsPlainText -Force) -Description "DeNet Node Service User"
-
Create service file:
# Create a PowerShell script to run the node $serviceScript = @" #!/usr/bin/env pwsh cd C:\denet .\denode.exe "@ $serviceScript | Out-File -FilePath "C:\denet\run-node.ps1" -Encoding UTF8
-
Install the service:
# Install the service using NSSM (Non-Sucking Service Manager) # Download NSSM from https://nssm.cc/ nssm install denode "C:\denet\run-node.ps1"
-
Start the service:
Start-Service denode
If you need to reinstall your DeNet Datakeeper Node, follow these steps:
-
Stop the current node process:
Get-Process denode | Stop-Process
-
Remove the existing installation directory:
Remove-Item -Recurse -Force C:\denet
-
(Optional) Remove Windows service (if previously configured):
# Uninstall the service if it was created with NSSM nssm remove denode -
Follow the Quick Start Installation steps from the beginning to install the node again
- Check if node is running:
Get-Process denode - Stop node:
Stop-Process -Name denode - View logs:
Get-Content -Path "C:\denet\denode.log" -Tail 10 - Check status:
Get-Process denode
Output Example:
PS C:\denet> Get-Process denode
Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
123 12 1234 5678 10.5 1234 1 denode
PS C:\denet> Stop-Process -Name denode
PS C:\denet> Get-Process denode
Get-Process : Cannot find a process with the name "denode". Verify the process name and call the cmdlet again.