Workspaces in the sidebar menu > Configuration

The Raynet One agent is a lightweight service that runs on managed devices and performs inventory operations on the local machine. Once installed and enrolled, the agent communicates with the platform either directly through the backend server or through a runner, depending on how the serving endpoint is configured. The agent always initiates communication — the server places messages in the agent's queue that the agent picks up at the next sync (by default every 10 minutes). This architecture removes the need for any inbound network connection to the managed device.

Unlike agentless inventory methods, the agent does not require network connectivity from the runner to the managed device. The device only needs to reach the runner, which makes the agent the preferred choice for devices in isolated network segments, laptops used off-site, and environments where agentless scanning is not feasible.

Topics in this chapter

•Installation and deployment — how to prepare an enrollment token, obtain the installer, and roll out the agent using Group Policy, MECM/SCCM, Intune, or MDM.

•Supported platforms — operating systems, architectures, and package formats.

•Enrollment file — where the agent looks for the enrollment file on each platform and what happens when the file is not found.

•Agent settings — how agent settings are configured, serving endpoints, sync interval, and logging levels.

•Inventory operations — how inventory jobs use the installed agent and how duplicate jobs are handled.

•CLI reference — command-line commands available on the agent.

•Uninstallation — how to remove the agent from a device and what data is deleted.