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, State, Version, Publisher, Target, Source, and Created. Package icons are displayed next to the package name when an icon is available for that package. This applies to packages imported manually, imported by AI, and imported from installer files. If no icon is available for a package, a generic Package Library icon is shown in its place.

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.

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

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

Supported Package Formats

The Package Library supports the following file formats for local package uploads, organized by target platform:

•Windows: .msi, .msix, .exe, .ps1 (PowerShell App Deployment Toolkit — PSADT packages)

•macOS: .pkg, .dmg

•Linux: .deb, .rpm, .flatpak, .snap, .AppImage

The supported maximum file size for all local uploads is 4 GB. Packages can also be imported directly from the Raynet Package Store without a file upload.

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 in one of the supported formats: .msi, .msix, .exe, or .ps1. Select the file using the file picker; the wizard reads the package metadata (name, version, publisher) from the file automatically where possible. Review and adjust these values before confirming. The supported maximum file size is 4 GB. For .msi packages, an optional MSI Transform (.mst) file can be applied. After upload, configure the install command, uninstall command, and working directory on the Installers tab in the package details view. PowerShell App Deployment Toolkit (PSADT) packages require uploading the entire source folder — see PSADT packages below for details.

•macOS package: Upload a macOS installer file (.pkg or .dmg). The supported maximum file size is 4 GB. After selecting the file, the wizard reads the package metadata automatically and displays the Bundle identifier and Minimum macOS version from the package. Review and confirm these values before adding the package.

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

Importing Linux Packages

Linux packages in the .deb, .rpm, and .snap formats can be imported into the Package Library. The import process follows the same steps as for Windows packages. This enables managing Linux software packages alongside Windows and macOS packages in a unified library.

Importing Packages from Package Store with No Installation Directory

When importing packages from the Raynet Package Store, packages where no installation directory is defined are handled gracefully. The import proceeds without requiring a defined installation path, and no error is raised for a missing installation directory.

PSADT packages

The PowerShell App Deployment Toolkit (PSADT) is a framework for deploying Windows applications using PowerShell scripts. A PSADT package consists of a main deployment script (Deploy-Application.ps1) together with supporting files in a standard folder structure.

To add a PSADT package, select Windows package in the Add package wizard and upload the main .ps1 deployment script. After the script is selected, use the Add folder option to upload the entire PSADT source folder. All files in the folder are uploaded as supporting files alongside the main script. The platform bundles them into a single package archive for distribution to managed devices.

An optional MSI Transform (.mst) file can also be attached by using the Add transform file option during the file selection step.

Package Details

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

•Details: Displays the package specification fields: State, Target, Publisher, Version, Architecture, Created, Last update, and Source. 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, in a tree structure that reflects the folder hierarchy. Because the display order is determined by the directory structure, column sorting is not available on this tab. 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. An operating system icon is displayed next to each device name to indicate the device platform.

2.Select packages: Select one or more packages to deploy. When all selected devices share the same operating system, the package list is filtered to show only compatible packages. When devices of different operating systems are selected, all packages are shown, and packages that are incompatible with one or more of the selected devices are labeled Incompatible. Only packages in the Ready state are available for selection.

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. Deployment progress can be monitored from the Deployments section.

Deployment Artifacts

Deployment artifacts allow you to collect files from managed devices after a package installation completes. The primary use case is collecting installation logs that the installer writes to disk, which enables you to review installation output after a deployment job finishes. Other file types can also be collected using the same mechanism. Artifact collection is configured per package in the package details view and can be reviewed during the deployment wizard.

To configure artifact collection paths for a package, open the package in the Package Library and locate the Deployment artifacts section in the Details tab. Click Edit to open the artifact path editor. Use Add path to add a new collection path. Each path has a Location type that determines how the path is resolved on the device:

•Absolute path: Specifies the full path to the artifact file on the managed device, for example C:\full\path\file.log on Windows or /full/path/file on Linux and macOS.

•Predefined location: Uses a known system folder (Base folder) as the starting point and appends a relative path to it. This allows artifact paths to resolve correctly regardless of the installation drive or user profile location.