First-Run Walkthrough
From first login to one device under management with a policy applied.
First-Run Walkthrough
This chapter takes you from your first login all the way to a managed device that is online, labelled, and has a policy applied. It assumes the server is already running (whether cloud or self-hosted).
The steps below use the terms introduced in Core Concepts.

Step 1 — Sign in
Open the Console in your browser. The login screen accepts your username and password, or a configured single-sign-on provider if your organisation has enabled SSO.
- Enter your username in the
Usernamefield. - Enter your password in the
Passwordfield and sign in. - If your account has two-factor authentication enabled, enter the current code from your authenticator app on the next screen.
- If your organisation uses SSO, click the SSO button on the login page instead and complete the provider's flow.
You land on /account/home, a small personal dashboard showing your profile information, navigation order menu and email signature configuration for the ticketing system.
Note: On a new self-hosted deployment, sign in with the username
adminand the passwordadmin. The Console makes you choose a new password at the first sign-in.
Step 2 — Complete the Setup Wizard
The first time an administrator visits the Dashboard page, the Setup Wizard opens automatically. Every step is saved as soon as you continue. It walks you through the basic settings:
- Choose your design.
- Check the connection to the backend.
- Set the date and time format.
- Set how many agent installations and updates may run at the same time.
- Optionally turn on two-factor authentication for your account.
- Enter your personal information.
- On a self-hosted deployment, enter the backend address the agents connect to. The Console then generates the agent installers for every tenant and location.
The last screen offers Deploy your first agent, which opens Agent Installers with the ready-built installers. Tenants, locations and groups are created on the Tenants page (Step 3).
Tip: Choose the name of your first tenant with care. It is common to use the company or customer name. You can rename it later, but external integrations (for example reports emailed to stakeholders) use the name you set here.
Step 3 — Create a tenant, location, and group
Create the tenant hierarchy on the Tenants page:
- In the left-hand navigation, open
Tenants. - On the
Tenantspage, click the add button and fill in the tenant name and basic details. Save. - Open the new tenant with the row action
Manage. TheManage tenantpage opens. - In its
Locationstable, add a location, typically a physical site such as "Berlin HQ" or "Remote Workers". - Open the location with the row action
Manageand, on theManage locationpage, add one or more groups. Groups should reflect how devices will be configured; a good starter set isWorkstations,Laptops, andServers.
See Chapter 4 for the full reference on the tenant page and its dialogs.

Step 4 — Get an agent installer
With the tenant and location in place, the Console has installers ready that register the agent into that tenant and location. NetLock RMM ships the agent as a single self-contained executable per platform and architecture, with the server configuration embedded.
- Open Agent Installers:
Deploy Agentin the navigation, orInstall Agenton theDevicespage while no device is enrolled. - Select the Tenant and Location.
- Under Automatic device authorization, choose whether new devices of this location are authorized automatically and until which date. Devices that register later, or while the option is off, wait in
Unauthorized Devices. - In the installer table, pick the row of the target platform and architecture (
win-x64,win-arm64,linux-x64,linux-arm64,osx-x64,osx-arm64). Once it shows Ready, click Download installer for the.zip, or Copy command for a one-line install that downloads and runs it on the device. - Optionally download or copy the installation script of that row (
Install-NetLockAgent.ps1for Windows,Install-NetLockAgent.shfor Linux or macOS), which installs the agent only where it is missing.
Details, including proxies and installing with parameters, are in Deploy your first agent.
Warning: Treat agent installers like secrets: anyone who has one can register a device into the configured tenant and location. If an installer authorizes devices automatically, set an end date; after that date, devices that register with it wait in
Unauthorized Devices.
Step 5 — Install the agent on a device
On the target device, copy the .zip, extract it, and run the binary with administrator or root privileges.
Windows (PowerShell, elevated):
Expand-Archive .\NetLockAgent.zip -DestinationPath .\NetLockAgent
.\NetLockAgent\NetLock_RMM_Agent_Installer.exeFor silent, unattended deployment via GPO, Intune, or Ansible, add flags:
.\NetLock_RMM_Agent_Installer.exe --hidden --no-log--hidden/-h: hide the console window (Windows only).--no-log/--nolog: delete installer logs after completion.--temp <path>/-t <path>: use a custom temporary directory.
Linux / macOS (Bash, with sudo):
unzip NetLockAgent.zip -d NetLockAgent
chmod +x NetLockAgent/NetLock_RMM_Agent_Installer
sudo ./NetLockAgent/NetLock_RMM_Agent_InstallerWith no arguments the installer uses its embedded config; on macOS (3.3.0.11 and later) it uses the server_config.json next to it in the package. For manual re-configuration or repair, the installer also accepts positional modes: clean "<path-to-server_config.json>" for a fresh install with an external config, fix "<path>" to repair while preserving the existing server config, and uninstall to remove the agent.
The installer registers the agent as a background service (Windows service, systemd on Linux, LaunchDaemon on macOS) and starts it. On macOS the agent additionally registers the User Process and the tray icon as LaunchAgents in the session of every signed-in user (agent 3.3.0.11 and later). Within a minute or two the agent contacts the server.
Note: NetLock RMM does not ship native
.msi,.deb,.rpm, or.pkgpackages; a single binary is used across all distributions.
Back in the Console, a device that registers before the location's Automatically authorize devices until date appears directly in Devices. After that date it appears in Unauthorized Devices instead, and an administrator must approve it before it is managed.
Step 6 — Approve the unauthorized device
- In the navigation, open
Devices → Unauthorized Devices. - Locate the new entry. It shows the device's hostname, operating system, and the tenant / location / group the agent was configured for.
- Select the entry and approve it. Optionally adjust the target group before approval if the agent was configured against the wrong one. An entry marked Name already exists belongs to a device you already manage (its operating system was reinstalled) and is continued with the row action Adopt as reinstall instead; see Chapter 3.2.
- Give the new device a human-readable label using the Edit Label dialog, for example
MARKETING-LAPTOP-01becomesAnna's laptop.
The device now appears in the main Devices list and reports status in real time. See Chapter 3 for the full Devices reference.

Step 7 — Create a policy and route it with an automation
With the device authorised, give it a policy. This takes two pieces in NetLock RMM: the policy itself (what should be enforced), and an automation rule that routes the policy to the right devices.
7a — Create the policy
- Open
Policiesfrom the navigation. - On
Manage Policies, click Add. Enter a name and description, for exampleStarter Workstations. Save. - Click Manage on the new row to open
Policy Settings. - The default settings enforce the agent configuration but do not yet configure Antivirus, Application Control, Patch Management, or any other opt-in feature. Configure the settings you need now; you can add sensors and jobs later.
- Save.
7b — Route the policy with an automation
- Open
Automationsfrom the navigation. - Click Add. Fill in:
NameandDescription.- Under
If …, leave the condition type atGroupand pick the group you created in step 3, for exampleWorkstations. - Under
Then …, select the policyStarter Workstations. - Leave
Priorityat the value the dialog proposes (400 for a group rule).
- Confirm.
The server immediately re-evaluates the devices of that group against the new automation and pushes the matching policy. The device receives the policy within the agent's next poll interval.
Note: When several automations match a device, the one with the lower priority number wins. At equal numbers, the rule with more conditions wins, then the older one. The dialog proposes a priority from the rule's most specific condition, so a rule for one device beats a rule for its group, which beats a rule for its tenant. See Chapter 5.
See Chapter 6 for the full Policies reference, Chapter 5 for the Automations reference, and Guide H.4 for a step-by-step walk-through.
Step 8 — Verify the policy arrived
Confirm that the device received the policy:
- Open
All devicesfrom the navigation. - The column called
Policyindicates what policy is currently assigned to the device.
If the expected policy is not displayed there, check on Automations which rules match the device and which one has the lowest priority number.
For further diagnostics, see Troubleshooting.
What you have now
At the end of this walkthrough you have:
- A tenant with one location and at least one group.
- One managed device, labelled and approved.
- A policy routed to the group by an automation.
That is the smallest meaningful deployment of NetLock RMM. Patch management, scripts, reporting, and the other features build on this foundation. The next chapter, Navigating the Console, describes the Console layout.