VERISCO Alertio Administer
Deploy agents
Bring machines under monitoring, one at a time with a guided install, or across a whole Active Directory domain with a generated deployment bundle.
Open Deploy Agent in the Investigate group. It has three modes: Guided Install, Active Directory and Audit Trail.
Supported platforms#
| Operating system | Packages |
|---|---|
| Linux | RPM and DEB, for amd64 and aarch64. |
| Windows | MSI, 64-bit and 32-bit. |
| macOS | Intel and Apple silicon. |
The install command always uses the current agent version, so a new machine never starts out of date.
Guided Install#
Four steps, for enrolling one machine.
-
Platform
Choose the operating system and the package format.
-
Configuration
Choose the agent group the machine will join, confirm the address it reports to, and optionally give it a name. A name already in use is rejected as you type. Select Generate enrollment.
-
Command
The install and start commands appear, each with a copy control. Run them on the machine. The command carries an enrolment token bound to the group and operating system you chose. Regenerate issues a fresh token; uninstall commands are provided too.
-
Verify
A live checklist follows the new agent through registration, connection, group policy and its first check-in. When it completes, Open in Endpoints takes you to the new machine, or Deploy another agent starts again.
Enrolment tokens#
An enrolment token is what lets a new machine join, so it is short-lived and limited by design.
| Property | Default |
|---|---|
| Lifetime | 24 hours. Up to 30 days. |
| Uses | One machine. Up to 1,000 for a mass rollout. |
| Visibility | The full token is shown once, when it is created. |
Tokens can be listed and revoked at any time. Generating a token requires the Administrator role.
Active Directory#
For enrolling many Windows machines at once. Supply the domain, the domain controller, an LDAP bind account, an optional search base and the address of your Alertio server, then map organisational units to agent groups.
Alertio generates a deployment bundle you download as a single .zip. It contains an inventory that reads your machines from Active Directory and the configuration to install and enrol the agent on each, ready to run from an Ansible control node. Machines are grouped by the organisational unit they sit in.
What the deployment account needs
The account the bundle uses to reach Windows machines must be able to install software on them, which in practice means local administrator rights on the targets. Remote management must be enabled on the targets, and they must be on a network profile that allows it.
Audit Trail#
Every enrolment and every bundle generated, with the person responsible and the time. Filter by all, active or failed.
After enrolment#
New machines appear on Endpoints within a minute of their first check-in. Classify the important ones in asset criticality so their alerts are weighted correctly.
Something missing or wrong on this page? Tell us and we will fix it.