Agent Configuration

Tune agent behavior using Windows Registry keys under HKLM\SOFTWARE\MaxRMM\Agent.

Registry Path

All agent configuration is stored in the Windows Registry at:

HKLM\SOFTWARE\MaxRMM\Agent

Changes to registry values take effect on the next telemetry cycle (within the configured ReportInterval) or after restarting the MaxRMM Agent service.

Configuration Values

Value Name Type Default Description
ReportInterval DWORD 60 Telemetry reporting interval in seconds. How often the agent sends CPU, RAM, disk, and service status to the server. Minimum: 15. Maximum: 300.
LogLevel String info Log verbosity level. Values: debug, info, warn, error. Use debug for troubleshooting, then set back to info.
WatchedServices Multi-String (empty) List of Windows service names to monitor. The agent will report if any watched service stops and can trigger alerts. Each service name goes on its own line.
ServerUrl String wss://agents.maxrmm.com WebSocket server URL. Set during installation. Do not change unless directed by MaxRMM support.
AgentId String (auto-generated) Unique agent identifier assigned during registration. Do not modify.
TokenHash String (auto-generated) Hashed authentication token. Do not modify.

Changing the Report Interval

To change how often the agent reports telemetry (e.g., every 30 seconds):

Set-ItemProperty -Path "HKLM:\SOFTWARE\MaxRMM\Agent" -Name "ReportInterval" -Value 30 -Type DWord

Note: Lower intervals provide more granular data but increase network traffic slightly. For most environments, the default of 60 seconds provides a good balance.

Changing the Log Level

To enable debug logging for troubleshooting:

Set-ItemProperty -Path "HKLM:\SOFTWARE\MaxRMM\Agent" -Name "LogLevel" -Value "debug" -Type String

After troubleshooting, set it back:

Set-ItemProperty -Path "HKLM:\SOFTWARE\MaxRMM\Agent" -Name "LogLevel" -Value "info" -Type String

Warning: Debug logging generates significantly more log data. Only use debug temporarily while investigating an issue. Leaving it on will grow the log file much faster.

Configuring Watched Services

To monitor specific Windows services and receive alerts when they stop:

# Monitor SQL Server, IIS, and a custom app service
$services = @("MSSQLSERVER", "W3SVC", "MyAppService")
Set-ItemProperty -Path "HKLM:\SOFTWARE\MaxRMM\Agent" -Name "WatchedServices" -Value $services -Type MultiString

Use the actual Windows service name (not the display name). To find service names:

Get-Service | Select-Object Name, DisplayName, Status | Format-Table

When a watched service stops, the agent reports a service category alert. You can pair this with an alert rule to get notified immediately, or with an event trigger to auto-restart the service.

Viewing Current Configuration

To see all current agent configuration values:

Get-ItemProperty "HKLM:\SOFTWARE\MaxRMM\Agent" | Format-List

Example output:

AgentId         : cl8f2k9x0001abcdef012345
ServerUrl       : wss://agents.maxrmm.com
TokenHash       : a1b2c3d4...
ReportInterval  : 60
LogLevel        : info
WatchedServices : {MSSQLSERVER, W3SVC}

Applying Configuration Remotely

You can change agent configuration remotely from the dashboard using the Run Command feature:

  1. Navigate to Agents → select the agent → Terminal
  2. Run the PowerShell command to update registry values
  3. The change takes effect on the next telemetry cycle

For fleet-wide configuration changes, create a script with the registry commands and schedule it to run on all agents.

Log File Location

Agent logs are stored at:

C:\Program Files\MaxRMM\logs\agent.log

Logs are rotated automatically. The agent keeps the current log file and up to 5 archived log files (each up to 10 MB). Total maximum log footprint is approximately 60 MB.