This topic covers the full process of installing and deploying the Raynet One agent: preparing the enrollment token in the platform UI, obtaining the installer, and rolling out the agent to devices using standard enterprise software distribution tools.
Before you begin: enrollment tokens
Every agent installation requires an enrollment token. The token authorizes the agent to register with the platform and determines the scope — the segment of the IT landscape — in which the agent will operate. Without a valid enrollment token, the agent cannot enroll after installation.
Enrollment tokens are managed in the platform under Configuration > Infrastructure > Agent enrollment. To create a new token, click Add enrollment token and complete the wizard: assign the scope, link the token to the appropriate agent settings, and set a token expiry duration. After the wizard completes, copy the token value — you will need it when building the enrollment file that accompanies the installer. Refer to Agent enrollment configuration for full details.
The enrollment token is embedded in the enrollment file that you distribute alongside the installer. All deployment methods described in this topic require that a valid enrollment file be present on the device before or during installation. Refer to Enrollment file for details on file locations and security considerations.
Obtaining the installer
The agent installer can be downloaded directly from Configuration > Infrastructure > Downloads. Select the appropriate package for the target platform. See Supported platforms for the full list of available package formats.
Deployment methods
The agent can be deployed to devices using standard enterprise software distribution tools. The following sections describe the recommended rollout strategies and the installer properties used for silent deployments.
Silent install property
When deploying the Windows .msi package silently, use the ENROLLMENT_FILE_PATH property to supply the path to the enrollment file. The installer copies the file to the default location automatically.
Property |
Type |
Description |
|---|---|---|
ENROLLMENT_FILE_PATH |
String (file path) |
Full path to the enrollment file to copy to the agent's data folder during installation. Optional — if omitted, the installer completes without placing an enrollment file, and enrollment must be performed manually afterward. |
Group Policy (GPO)
Use Group Policy to deploy the agent .msi package to Windows domain-joined devices. GPO software installation supports .msi packages natively and applies the installation at device startup before the user logs on.
To deploy the agent via GPO:
1.Place the agent .msi installer in a network share that is accessible by domain computers.
2.Place the enrollment file in the same share or in a separate secured share accessible by domain computers.
3.Open the Group Policy Management Console (GPMC) and create or edit a Group Policy Object linked to the organizational unit (OU) containing the target computers.
4.Navigate to Computer Configuration > Policies > Software Settings > Software Installation and add the agent .msi as a new package. Set the deployment type to Assigned.
5.Under the package properties, in the Modifications or Advanced settings, add a transform or command-line property to set ENROLLMENT_FILE_PATH to the UNC path of the enrollment file. Alternatively, deploy the enrollment file to the default path on each device using a separate GPO startup script before the agent installs.
6.Apply the GPO. The agent installs on target devices at the next Group Policy refresh cycle (typically at startup).
|
Tip: |
Software deployment tools (MECM/SCCM, Intune Win32, third-party)
Enterprise software deployment tools such as Microsoft Endpoint Configuration Manager (MECM/SCCM), Microsoft Intune Win32 apps, and third-party tools (e.g. Ivanti, Baramundi, Matrix42) can distribute the agent installer and the enrollment file as a deployment package. The general approach is the same regardless of tool:
7.Create a deployment package containing both the agent installer and the enrollment file.
8.Define a silent install command that passes the ENROLLMENT_FILE_PATH property to the installer. A typical silent install command for the Windows .msi is:
msiexec.exe /i RaynetOneAgent.msi /qn ENROLLMENT_FILE_PATH="path\to\enrollment.json"
3.For Linux and macOS, use the package manager commands appropriate for the package format (rpm, dpkg, or installer). Copy the enrollment file to the default path either before running the installer or as a post-install step in the deployment script.
4.Deploy to the target device collection. The agent installs silently and, if the enrollment file is present, the agent automatically enrolls at the next scheduled sync.
MDM-based rollout
Mobile device management (MDM) solutions can deploy the agent to managed devices as a managed application. This approach primarily applies to macOS (using the .pkg package) and Windows (using the .msi package).
To deploy the agent via MDM:
9.Upload the agent installer package to your MDM solution as a managed app or a custom application.
10.Deliver the enrollment file to each device using a configuration profile or a file distribution policy before the agent package is installed. Place the file at the default enrollment file path for the target platform.
11.For Windows, pass the ENROLLMENT_FILE_PATH property in the install command if the MDM solution supports MSI properties.
12.Assign the agent app to the target device group and deploy. Confirm that the enrollment file is present on the device before the agent app installs to avoid a failed enrollment.
|
Note: |
