Super IT RMM Agent installation guide

Previous Next

This guide provides comprehensive instructions for IT administrators to deploy the Super IT RMM agent across their organization's devices.

Prerequisites

Super IT Account Setup

  1. Organization Account: Ensure your organization has an active Super IT subscription
  2. Administrator Access: You need administrative access to the Super IT portal and to device installing the agent
  3. Installation key: You can generate a Installation Key inside the Super IT platform: Devices -> Install -> Create installer key

⚠️ Security Note: Installation keys provide device enrollment access. Protect them like administrative credentials.

Network requirements

Network Requirements

Before deployment, ensure your network infrastructure supports:

Required Outbound Connections:

  1. HTTPS (Port 443): For secure web communication
  2. NATS (Port 4222): For real-time messaging
  3. DNS Resolution: Access to Super IT service endpoints

Firewall Configuration: 

Direction: Outbound only
Destination: *.superit.ai
Ports: 443 (HTTPS)
Protocol: TCP

Direction: Outbound only
Destination: connect.ngs.global
Ports: 4222 (NATS)
Protocol: TCP

Required permissions

Required Permissions

Installation requires:

  • Local administrator rights on target devices
  • Domain administrator rights for Group Policy deployment
  • MDM administrative access for mobile device management

Download Agent Installer

Download the appropriate installer for your system architecture:

How to check your architecture

How to Check Your Architecture

Windows: 1. Open Settings → System → About 2. Look for "System type" 3. Choose x86/x64 version unless it specifically says "ARM64"

Command Line: 

echo %PROCESSOR_ARCHITECTURE%

⚠️ Note: Download links are version-specific. Contact Super IT support for the latest version if these links don't work.

https://updates.superit.ai/releases/v0.1.265/windows/superit-agent-amd64-0.1.265.msi
https://updates.superit.ai/releases/v0.1.265/windows/superit-agent-arm64-0.1.265.msi

Deployment Methods

Manual Installation

Recommended for testing and small deployments

Windows Installation

  1. Run as Administrator: Right-click installer → "Run as administrator"
  2. Installation Wizard: Follow the setup wizard
  3. Enter Installation Key: Provide the key when prompted
  4. Configure Options:
  5. Installation directory (default recommended)
  6. Complete Installation: Restart may be required

Command Line Installation: 

msiexec /i superit-agent-amd64-0.1.265.msi INSTALLKEY="your-key" /quiet /norestart

Automated Scripts

For bulk deployment scenarios

PowerShell Script (Windows)

# Download and install Super IT Agent
$installerUrl = "https://updates.superit.ai/releases/v0.1.265/windows/superit-agent-amd64-0.1.265.msi"
$installerPath = "$env:TEMP\superit-agent-amd64-0.1.265.msi"
$installKey = "your-installation-key"

# Download installer
Invoke-WebRequest -Uri $installerUrl -OutFile $installerPath

# Install silently
Start-Process msiexec.exe -Wait -ArgumentList "/i $installerPath INSTALLKEY=$installKey /quiet /norestart"

# Verify installation
if (Get-Service "SuperIT Agent" -ErrorAction SilentlyContinue) {
    Write-Output "Super IT Agent installed successfully"
} else {
    Write-Error "Installation failed"
}

Group Policy Deployment (Windows)

Recommended for Windows environments with Active Directory

Prepare Group Policy

  1. Create GPO: Create a new Group Policy Object named "Super IT Agent Deployment"
  2. Copy Installer: Place the MSI installer in a network share accessible by all computers
  3. Link GPO: Link the GPO to the appropriate Organizational Units

Configure Software Installation

Computer Configuration → Policies → Software Settings → Software Installation
1. Right-click → New → Package
2. Browse to \\server\share\superit-agent-amd64-0.1.265.msi
3. Select "Advanced" deployment method
4. Configure properties:
   - Install this application at logon: Yes
   - Uninstall this application when it falls out of scope: No

Configure Installation Parameters

Create a transform file (.mst) or use command line parameters: 

INSTALLKEY="your-installation-key-here"

Deploy and Monitor

  1. Apply GPO: Use gpupdate /force to apply immediately for testing
  2. Monitor Installation: Check Event Viewer for installation success/failure
  3. Verify Registration: Confirm devices appear Super IT -> Devices

Mobile Device Management (MDM)

Recommended for modern, cloud-managed environments

Microsoft Intune

  1. Upload App: Go to Apps → All apps → Add
  2. Select App Type: Choose "Line-of-business app"
  3. Upload Package: Upload the appropriate installer (.msi, .pkg, or .apk)
  4. Configure App Information:
  5. Name: Super IT Agent
  6. Description: Intelligent IT support monitoring agent
  7. Publisher: Super IT
  8. Configure Installation Commands: 
    Install: msiexec /i superit-agent-amd64-0.1.265.msi INSTALLKEY="key" /quiet
Uninstall: msiexec /x {product-guid} /quiet
  9. Assign to Groups: Deploy to appropriate device or user groups
  10. Monitor Deployment: Use Intune reporting to track installation status

Post-Installation Verification

Checking the agent status

Windows: 

sc query "SuperIT"

Windows powershell: 

get-servce -name "SuperIT"

Reading the agent logs, these can be found here

Windows powershell: 

get-content -path C:\ProgramData\SuperIT\superit.log -tail 10

Agent startup / shutdown events are published to the windows event logs

Windows logs -> Application -> Source (Super IT)

Confirm registration through the Super IT dashboard

  1. Access Dashboard: Log in to Super IT portal
  2. Navigate to Devices: Go to Devices → Agent Status
  3. Verify Registration: Confirm new devices appear with "Online" status
  4. Check Data Collection: Verify system metrics are being collected

Troubleshooting

A guide to troubleshoot common errors that might be found.

no install_key or registration credentials found

When reading through the superit.log you might see this error:

failed to determine agent mode: no install_key or registration credentials found

The final configuration state will be displayed in the logs when the agent starts, here is an example:

{"time":"2025-10-15T00:30:18.4029593Z","level":"INFO","msg":"final configuration state","config":{"Log":{"Level":"INFO","FileName":"C:\\ProgramData\\SuperIT\\superit.log","MaxSize":100,"MaxBackups":3,"MaxAge":28,"Compress":true},"MetricsInterval":30,"StorageFile":"metrics.json","InstallKey":"","NATS":{"Server":"tls://connect.ngs.global","Creds":"C:\\ProgramData\\SuperIT\\ngs.creds"},"UpdateCheckIntervalSeconds":3600,"UpdateManifestURL":"https://github.com/GetSuperIT/subtechnica-agent/releases/latest/download/latest.json"}}

Check that the NATS.Creds file exists, in this case it is the value: 

C:\ProgramData\SuperIT\ngs.creds

Also check that the InstallKey is not empty, in the example above it is which is the cause of the error. The install key is provided as a system enviornment variable. You can check it's existence by 

get-childitem env:

And look for the SUPERIT_INSTALL_KEY value. If this exists, then restart the service to pick it up. 

restart-service -name "SuperIT"

If it does not exist then you can create the variable and restart the service.

Configuration Management

Windows: C:\ProgramData\SuperIT\config.yaml

The agent uses a YAML configuration file to customize behavior. Most settings have sensible defaults and only need to be changed for specific requirements.

Configuration Priority

Settings are applied in this order (highest to lowest priority):

  1. Environment Variables - Override everything
  2. Configuration File - Custom settings in config.yaml
  3. System Defaults - Built-in default values

Default Configuration File

# logs:
#   # options are DEBUG, INFO, WARN, ERROR
#   level: WARN

#   # forward slashes will need to be escaped
#   file_name: "C:\\ProgramData\\SuperIT\\superit.log"

#   # max_size is in megabytes, so 10 will be 10mb
#   max_size: 10

    # max number of log files to create
#   max_backups: 3

#   max_age: 28
#   compress: true


# metrics_interval: in seconds
# metrics_interval: 60

# storage_file: file to store metrics on disk between intervals
# storage_file: "C:\\ProgramData\\SuperIt\\metrics.json"

# auto update
# update_check_interval_seconds: 3600  # Check for updates every hour
# update_manifest_url: "https://updates.superit.ai/latest.json"

Common Configuration Changes

Note

These are the most common scenarios for modifying the config.yaml file.

Enable debug logging

Enable Debug Logging (Troubleshooting)

logs:
  level: "DEBUG"
  file_name: "C:\\ProgramData\\SuperIT\\superit.log"
Adjust Metrics Collection Frequency

Adjust Metrics Collection Frequency

# Collect metrics every 2 minutes instead of default 60 seconds
metrics_interval: 120
Disable automatic updates

Disable Automatic Updates

# Disable automatic updates (not recommended for production)
update_check_interval_seconds: 0

Environment Variables (Alternative Configuration)

For environments where editing config files isn't preferred:

# Set log level for troubleshooting
setx SUPERIT_LOG_LEVEL "DEBUG" /M

Log File Locations

Windows: C:\ProgramData\SuperIT\config.yaml

Unless modified inside the config.

Scaling and Performance

Large Deployments

Deployment Phases: 1. Pilot: Deploy to 10-50 test devices 2. Staged Rollout: Deploy in batches of 500-1000 devices 3. Full Deployment: Complete organization-wide rollout

Performance Considerations: - Stagger deployment times to avoid bandwidth spikes - Monitor network utilization during initial data collection - Plan for increased support portal load during rollout

Resource Planning

Network Bandwidth: - Initial registration: ~100KB per device - Ongoing monitoring: ~10KB per device per hour - Diagnostic data: Variable, typically <1MB per incident

Storage Requirements: - Agent installation: ~100MB per device - Log retention: ~50MB per device per month - Dashboard storage: Handled by Super IT infrastructure

Next Steps: After successful installation, learn about agent capabilities and user benefits to maximize your Super IT deployment.

How it works PSA Integration Overview