Workspaces in the sidebar menu > Endpoint Management

The Patching section of the Endpoint Management workspace provides a consolidated view of software products installed on managed devices for which newer versions are available. It enables you to identify outdated software across the managed estate and initiate update deployments directly from the list.

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

How Patching Data Is Computed

Raynet One automatically calculates patching data in the background by comparing installed software versions on managed devices against the latest available versions in the Raynet Catalog and the connected Raynet Package Store. This computation runs periodically (approximately every two hours) and updates the patching list accordingly. The refresh can also be triggered manually using the refresh button in the toolbar.

Patching List

The patching list shows all software products detected on managed devices that have a newer version available. Each row represents a software product with an outdated version installed on one or more managed devices. The list can be filtered by device using the device selector in the toolbar, allowing you to focus on the update status of specific managed devices. When a device filter is active, the Installations column is hidden because the list already reflects the selected devices only.

The following columns are available:

•Application: The name of the software product with an available update.

•Manufacturer: The software vendor responsible for the product.

•Platform: The operating system platform on which the software is installed.

•Version: The version of the software currently installed on the managed devices.

•New Version: The newer version that is available for the software product.

•Patch Source: The source from which the update package is obtained. This column shows a value only when a package is available for the update:Library: An update package for this version is already present in the Package Library and is ready to deploy.

•Package Store: An update package is available from the connected Raynet Package Store and must be downloaded before it can be deployed.

Column Chooser

The patching list supports the Column Chooser, which allows you to show or hide columns to tailor the view to your needs. Click the Column Chooser button in the list toolbar to open the panel. You can drag columns between the list and the Column Chooser panel to add or remove them from the view. For a general description of the Column Chooser, see Lists.

In addition to the default visible columns described above, the Column Chooser exposes a set of internal identifier columns that are hidden by default. These columns contain system-level reference data and are not required for everyday patch management operations. They may be useful for advanced inspection or troubleshooting purposes:

•ID: The internal system identifier of the patch entry.

•Parent Catalog Version ID: The internal identifier linking a child entry to its parent catalog version row in the tree view.

•Catalog Version ID: The internal identifier of the matched Raynet catalog version entry for this patch row.

•Package Store Package Version ID: The internal identifier of the associated Package Store package version, when a Package Store source has been matched.

•Library Package ID: The internal identifier of the associated Package Library package, when a Library source has been matched.

•Has Children: An internal flag that indicates whether a row has child entries in the tree view. A value of true means the row can be expanded to show child entries.

•Catalog Product ID: The internal identifier of the catalog product associated with this patch entry.

Catalog Recognition and Ready-to-Patch Entries

The patching list is organized as a hierarchical tree view. Top-level (parent) rows represent software products for which a newer version has been detected across one or more managed devices. Where a product has multiple version entries, expanding the parent row reveals the individual child rows for each version.

Patching data relies on catalog recognition: Raynet One compares installed software versions against the Raynet catalog to identify newer versions. When an installed version is successfully matched to a catalog entry, the system can precisely determine the available update version and, where a corresponding package exists, link the update to either the Package Library or the Package Store.

Entries that display a value in the Patch Source column (Library or Package Store) are ready to patch: an update package has been identified and the entry can be deployed (Library) or downloaded and then deployed (Package Store) directly from the patching view. Entries where the Patch Source column is empty have been detected as having a newer catalog version available, but no corresponding update package has been linked yet. These entries are shown for informational purposes and cannot be deployed directly from the patching view.

Software Details

Clicking a row in the patching list (without clicking the expand arrow or the selection checkbox) opens the software product detail page in the Asset Management workspace. The page opens directly on the Installations tab, which lists all devices where the outdated version of the software product is installed. When navigated to from the patching view, the list is automatically filtered to show only devices that have the Raynet One EPM agent installed.

The software product detail page also contains the following tabs, which you can switch to for a broader view of the product:

•Details: General information about the software product sourced from the Raynet catalog, including the product name, manufacturer, platform, and catalog metadata.

•Versions: All versions of the software product detected in the managed environment, along with version-level catalog and lifecycle information.

•Vulnerabilities: Known security vulnerabilities (CVEs) associated with the software product as sourced from the Raynet catalog.

•Installations: The full list of devices where the software product is installed. Columns include IP Address, Name, Domain, Source, Product, and Version. Additional device attributes such as Corporate Identifier, Corporate State, Scope, Model, BIOS Serial Number, UUID, and others can be added to the list via the Column Chooser.

Filtering by Device

Use the device selector in the upper-right area of the toolbar to narrow the patching list to one or more specific managed devices. Select one or more devices from the drop-down to apply the filter. To clear the filter, remove the selected devices from the selector. The active filter state is preserved between sessions.

Initiating a Software Update

The steps to initiate a software update depend on the patch source of the selected entry.

Deploying from Library

If the patch source is Library, the update package is already available in the Package Library. Select one or more entries with a Library patch source and click Deploy in the toolbar. The deployment wizard opens, allowing you to select target devices and review the deployment configuration before proceeding.

Downloading and Deploying from Package Store

If the patch source is Package Store, the update package must first be downloaded from the Raynet Package Store before it can be deployed. This option is only available when a Raynet Package Store connection is configured and active. To download and then deploy a Package Store package:

1.Select an entry with patch source Package Store in the patching list.

2.Click Download package in the toolbar. A confirmation dialog appears. If a download for this package version is already in progress, you are notified before proceeding.

3.Confirm the download. The package is fetched from the Package Store and added to the Package Library as a background job.

4.Once the download is complete, the patch source for that entry changes to Library. You can then select the entry and click Deploy to open the deployment wizard.

For entries with the Package Store patch source, a Download action is available directly in the patching list. Use this action to download the latest available version of that package from the Package Store into the local Package Library without leaving the Patching view.

Update deployments created through the Patching section can be monitored from the Deployments section, or from the Jobs tab within the individual managed device details.