Workspaces in the sidebar menu > Endpoint Management

The Package Library section of the Endpoint Management workspace is the central repository for all software packages that can be deployed to managed devices. You can add packages from the Raynet Package Store or upload them from local files. Once packages are available in the library, they can be deployed to one or more managed devices through a guided deployment wizard.

Access: Open Workspaces > Endpoint Management > Package Library in the left sidebar.

Package List

The package list displays all packages available in the library. You can filter packages by operating system using the sidebar sub-navigation:

•All packages: Shows the complete package inventory regardless of target platform.

•Windows packages: Filters the list to show only packages targeting Windows devices.

•Linux packages: Filters the list to show only packages targeting Linux devices.

•macOS packages: Filters the list to show only packages targeting macOS devices.

The list shows the following columns for each package: Name, Version, Publisher, Platform, Source, and State.

Package States

Each package in the library carries a state that reflects its readiness for deployment:

•Draft: The package has been created but has not yet been confirmed as ready for deployment. Installer commands may still need to be configured.

•Processing: The package is currently being processed by the platform (e.g., after upload or packaging job initiation).

•Ready: The package is fully configured and available for deployment to managed devices.

•Tested: The package has been tested and confirmed to work correctly in the target environment.

•Invalid: The package has a configuration error. Review the installer configuration to resolve the issue before deploying.

Only packages in the Ready or Tested state can be deployed to devices.

Adding Packages

Use the Add package action to add a new package to the library. The following package types and sources are supported:

•Package Store: Import a pre-built package directly from the Raynet Package Store. Select the application, choose the target platform and version, and configure optional settings such as installation behavior, desktop shortcuts, and startup preferences before adding the package to the library. Requires an active Package Store integration.

•Windows package: Upload a Windows installer file (.msi, .msix, .exe, or .ps1). The supported maximum file size is 4 GB. An optional MSI Transform (.mst) file can be applied. For PowerShell App Deployment Toolkit (PSADT) packages, the entire source folder must be provided.

•macOS package: Upload a macOS installer file (.pkg or .dmg). The supported maximum file size is 4 GB.

•Linux package: Upload a Linux package file (.deb, .rpm, .flatpak, .snap, or .AppImage). The supported maximum file size is 4 GB.

Package Details

Selecting a package from the list opens the package details view, which contains the following tabs:

•Details: Displays the package specification, including name, version, publisher, platform, architecture, language, source, description, and licensing information. This tab also shows the deployment artifacts configuration and a summary of the installer commands.

•Files: Lists the files associated with the package, including the installer file. This tab is available once the package processing is complete.

•Installers: Shows and allows editing of the installer commands used during deployment — install command, uninstall command, and repair command — as well as the working directory and the product code.

Deploying Packages

Use the Deploy action on a package or from the package list to start the deployment wizard. The wizard guides you through the following steps:

1.Select devices: Choose one or more managed devices to deploy the package to. Only devices with an installed and active agent are available for selection.

2.Select packages: Select one or more packages to deploy. The package list is filtered to match the operating system of the selected devices.

3.Summary: Review the deployment configuration — selected devices, selected packages, and artifact collection settings — before starting the deployment. Packages incompatible with the target device operating system are marked accordingly.

After confirming the deployment, the platform creates installation jobs for all valid device-package combinations. Job progress can be monitored from the Jobs section.

Deployment Artifacts

Deployment artifacts allow you to collect files from managed devices after a package installation completes. Artifact collection paths specify where on the device the platform should look for output files, such as installation logs. Paths can be defined as absolute paths or relative to predefined system locations. Artifact collection is configured per package in the package details view and can be reviewed or overridden during the deployment wizard.