Install the Monitic agent
One lightweight agent covers monitoring, patching, remote access, and security. This guide takes you from a fresh workspace to a fleet reporting live — in one sitting. The installer is generated inside your workspace and is unique to your company: it is pre-bound to your tenant and enrollment token, so a deployed agent enrols into the right place automatically. That is why there is no download button on this page — you get your real package from the console. The commands shown here are illustrative; copy your exact ones from Agent Download.
Before you begin
A short checklist keeps the rollout clean. You need a workspace, admin rights on the target machines for unattended methods, and outbound network access from each device to the platform.
- Supported systems — Windows 10/11 and Windows Server 2016 or newer; major Linux distributions (Debian/Ubuntu, RHEL/Alma/Rocky) on current releases.
- Network — the agent needs outbound HTTPS (443) to the platform; no inbound ports and no public exposure of the endpoint.
- Privileges — interactive install needs a local admin; silent and GPO methods run as SYSTEM or a deployment account.
- A workspace — the source of your company-specific installer and token. If you do not have one yet, start a free trial — it takes a couple of minutes.
Step 1 — Create your workspace
Sign up and create your organization. From that moment you are in the console, and Monitic can generate an installer bound to your company. Multi-company structure, units, and team invitations are available from minute one — set up as much or as little as you want before you deploy. Start free trial.
Step 2 — Get your installer
Open Agent Download in the console. Monitic builds a package unique to your company, carrying your workspace binding and enrollment token so the agent enrols into the correct tenant with no manual keying. Download the MSI (Windows) or the install script (Linux), or copy the silent-install command shown on that screen. Because the package and command carry your token, treat them like a credential — do not post them in public channels.
Step 3 — Deploy it
The same package installs three ways. Pick by scale.
Interactive — a test machine. Run the downloaded installer and click through. Best for a first look before you push to a fleet.
Silent — scripts and RMM push. Your workspace shows a ready command; it is shaped like the line below, but yours carries your own token, so copy the exact one from Agent Download rather than this example:
msiexec /i MoniticAgent.msi /qn ENROLL_TOKEN=<your-workspace-token>
On Linux, the console gives you an equivalent one-line install script. Push either with the tooling you already use.
GPO — Windows fleets. Two supported patterns: assign the MSI through a Software Installation policy so domain machines install it at next boot, or run the silent command as a startup/logon script. Point the package at a share the target machines can read, scope the policy to the right OU, and let it roll out on the next Group Policy refresh.
Step 4 — Verify, then set a policy
Devices appear in the console within a minute of install — hardware and software inventory, health metrics, and patch status stream in as each agent enrols. Once you can see a device, you have a managed endpoint. Confirm the count matches what you deployed, then set your first patch policy and a baseline alert rule against a small test group before rolling fleet-wide. The module documentation covers policies, maintenance windows, and alert thresholds in depth.
Your fleet, reporting in minutes
Start free trial to create the workspace and generate your installer — full-featured, 14 days, no credit card. Prefer a guided walkthrough? Get a demo and an engineer will deploy alongside you.
See Monitic on your own fleet
Full-featured 14-day trial · no credit card · your real fleet in the console on day one.