Getting started · Windows & Linux agents · Per-tenant database

Get started in minutes

Login to your tenant, verify your license and agent key, deploy the agent, and start collecting operational insights across your Windows and Linux estate. This page explains what you need, what to do first, and how to verify everything is working.

Before you begin

You’ll typically need: access to the VectraOps portal, local admin rights for installation on target systems, and outbound internet access from those systems to reach the platform. If you’re operating multi-customer (MSP), make sure you’re working inside the correct tenant before enrolling any agents.

Quick checklist Ready

Check license key / agent key

Verify your license status and copy the tenant-scoped agent enrollment key.

Download & install the agent

Deploy on servers/workstations (Windows and/or Linux) with local admin rights.

Verify Connectivity

Confirm the host checks in and inventory/metrics start populating.

Start using the features

Enable alerts, run safe tasks, review patch posture and generate reports.

Tip: For first rollout, start with 2–5 pilot systems (one server + one endpoint per OS) to validate policies and alert thresholds.

Get started in three simple steps

VectraOps is built for operations teams who need fast visibility and safe remote actions across their Windows and Linux estate. Below is a clearer walkthrough of what to do and what “done” looks like.

Login and select the right tenant

Sign in and confirm you are working inside the correct Organization/Tenant. This tenant is the security boundary: all systems, alerts, tasks and reports remain scoped to that tenant.

If you manage multiple customers or business units, double-check the tenant context before enrolling agents.

Verify license and agent key

Confirm your subscription/license is active, then locate the tenant-scoped agent enrollment key (API key / token). Keep this key private and treat it like a password.

This key ensures agents register into the correct tenant and start sending inventory and telemetry.

Install the agent and validate check-in

Download and install the lightweight VectraOps agent on Windows and/or Linux. Agents connect outbound to the platform, so you typically don’t need inbound firewall changes.

After installation, verify the host shows online and that initial inventory/metrics appear. Then start enabling features.

Detailed walkthrough

What to do, in order

Use this as your “operator runbook” for the first deployment. The goal is to get a first host online, confirm data is flowing, and then scale to a larger rollout.

Docs

Sign in, select the correct tenant, and confirm you can open the tenant dashboard. For MSP setups, repeat this per customer and keep enrollments strictly tenant-scoped.

Check license key / agent key

Verify the license/subscription is active for this tenant, then copy the tenant agent enrollment key. Treat the key as sensitive—share it only with admins who perform deployments.

Download & install the agent

Start with 1–2 pilot systems. Use local admin rights and provide the enrollment key during install/config. Prefer a representative set (e.g., one server and one endpoint, and both OS types if applicable).

Verify Connectivity

Confirm the system appears in inventory with a recent check-in. Validate hostname/OS and that health metrics (CPU/memory/disk) are visible. If it doesn’t show up, use the troubleshooting checks on this page.

Start using the features

Enable one capability at a time: start with low-noise alert rules, then controlled tasks, then reporting and policy-based workflows. This keeps rollouts safe and predictable.

Recommended first success criteria

The pilot host appears in inventory with correct OS/hostname and recent check-in.
At least one health snapshot (CPU/mem/disk) is visible.
You can trigger a safe test task (e.g., “refresh inventory” if available, or a non-disruptive task).
One alert rule can be created and produces predictable results (no alert storm).

Troubleshooting

If a host doesn’t show up

Most onboarding issues are connectivity or enrollment related. Use the checks below before digging deeper.

1) Enrollment key

Confirm the key belongs to the intended tenant and was copied correctly into the installer/config.

2) Agent service status

Confirm the agent service is installed and running on the target system. If it stops immediately, review local logs and permissions.

3) Outbound network access

Ensure the system can reach the VectraOps platform over outbound HTTPS. Corporate proxies may require configuration.

4) Time sync

Large clock drift can break TLS and cause check-in failures. Verify NTP/time sync on the host.

Contact support Docs

What happens after onboarding?

Once agents are connected, you can expand into the workflows that matter most for daily operations. Start small, validate, then scale.

Goal	What you do	What “good” looks like
Inventory accuracy Know what runs where	Roll out agents to your core system groups. Validate naming conventions, tagging, and owner/tenant scoping.	Systems show consistent identifiers, recent check-ins, and stable hardware/network snapshots.
Health visibility Spot issues early	Review baseline CPU/memory/disk behavior, then enable alert thresholds that match your environment.	Alerts are actionable and low-noise; you can quickly identify the “real” problem host.
Patch posture Reduce update gaps	Track pending updates and reboot-required hosts. Use maintenance windows to batch remediation.	Clear lists for “pending updates” and “pending reboot” reduce patch cycle friction.
Controlled remediation Execute safe tasks	Start with non-disruptive tasks, then expand to reboots/renames/uninstalls with approvals and auditing.	Tasks show reliable status and history; changes are traceable and tenant-scoped.

Want a guided rollout? Use the docs for step-by-step instructions, or contact support for a tailored onboarding plan.