Release 2.12

August 05, 2024

What's New?

Reporting on Patching

With this release, we introduced a new tab, the Reports tab, which provides a unified view of reports generated from the Patch Management UI.

Reports tab.

Additionally, you can generate exclusive reports for Windows, Linux, and Mac platforms based on a wide range of parameters or selections, such as the required QQL queries, timeframe or period, and patch installation status. Depending on these selections, you can get vital information like whether the patch installation is successful, which assets are part of how many jobs, and so on. 

Important to Know!

  • You can generate the report using the required Patch and Asset QQL queries, which is optional.
  • You can include patches with Failed, Success, or both statuses, but selecting at least one is mandatory. You can group by the report based on the statuses mentioned earlier, which is also optional.

For more information, refer to the Online Help

Example: Mac Report Generation 

Create Report from Reports tab.

Import Assets from the CSV file in the Deployment Job Workflow

Before this release, you could only manually select the assets while creating or editing a deployment job. With this release, you can also import assets from the CSV file. This option is available for all platforms: Windows, Linux, and Mac. 

Refer to the following screenshot: (Windows Deployment Job Creation Workflow)

Import Assets from the CSV file.

Important to Know!

  • You can import a maximum of 5000 assets from the CSV file.
  • The asset names are case-sensitive. Hence, you must include the correct asset name in the CSV file. Incorrectly spelled assets or assets not available in your subscription are not considered for import.
  • The CSV file is validated during the import process, and the reasoning or error for skipped assets is also recorded. You can download the validated file and get these details. Note that the CSV file validation and import process might take longer based on the number of assets included, which increases the file size.  

Ubuntu 24.04 Support

We have provided patching support for Ubuntu 24.04 Linux assets.

ubuntu 24 patching support.

Ubuntu 14.04 ESM Support

We have provided patching support for Ubuntu 14.04 ESM Linux assets.

ubuntu 14 patching support.

EUS Support for RHEL 8.6 and 8.8 Versions

The RHEL Extended Update Support (EUS) patches are supported for the RHEL 8.6 and 8.8 versions. These patches are also published in the patch catalog. You can deploy patches on your Linux assets from your EUS repository.

Report Generation for Linux and Mac Assets

Before this release, you could generate the report for Windows assets. With this release, you can generate the report for Linux and Mac assets.  

Example: Generate Report for Linux Assets

Linux Assets Report Generation.

Asset_IP Column Added to the Job Progress Report

With this release, we have added the "ASSET_IP " column to the Windows, Linux, and Mac job progress reports, which provides the asset's IP address. This valuable insight enables more comprehensive tracking and analysis of the process.

Asset_IP column added to the job progress report.

API Enhancements

We have updated the following APIs:

  • Download Report in the CSV Format: The API has been enhanced to extend downloading the Linux job progress report, like the Windows job progress report. In addition, we have added the "ASSET_IP" column to the job progress report for both Windows and Linux platforms. 
  • Get the List of Reports: The API has been enhanced to include the “Name” and “Description” attributes, enabling more comprehensive tracking and analysis of the reporting process in the back end.
  • Get Assets Tab Report: The API has been enhanced to enable downloading the Linux Asset report, like the Windows assets report.

 For more information, see PM 2.12 API Release Notes.

Issues Addressed

See the summary of customer CRMs fixed in this release.

Component/Category Description

PM - Job Windows

An issue was observed wherein the email notifications were not sent as expected for deployment jobs where only the job completion email notification was configured. The expected email notifications are now sent when the agent sends the 'Job Failed' status.

PM - UI

We fixed the issue wherein instead of 'Pending Manual Reboot' and 'Pending Auto Reboot' statuses,  incorrect patching statuses were shown for assets.

PM - Job Windows

We fixed the issue where, although the patch job was in the disabled status, it was being changed to enabled without any manual intervention and vice versa.

PM - UI

We fixed the issue where the Patch Management application crashed when cloning a patch job on a macOS device.