Release 2.10

April 24, 2024

What's New?

Windows Job to Initiate System Reboot on Priority

Before this release, if any of your Windows assets were waiting for a system reboot, you needed to reboot such assets manually. Also, if the suppress reboot option is enabled, the asset reboot is suppressed unless you manually reboot it.

However, with this release, you are no longer required to do it. You can now automate a system reboot by creating a Windows job that includes such assets and only a "System Reboot" pre-action.

Dependency

Windows Cloud Agent 5.6 and later

When you create a job, make sure that you select only a "System Reboot" pre-action and don't select any other pre-action, post-action, or patch options. Such a job will be prioritized, and the system reboot is automatically initiated when the job reaches the agent at the scheduled job time, even if it's waiting for another reboot.

Job with only a System Reboot pre-action.

Capability to Recognize OS changes for activated assets

With this release, Patch Management recognizes and honors the operating system upgrade on the already activated Windows, Linux, and Mac assets.

If the operating system of any activated assets is upgraded to a version Patch Management doesn't support, the scanning is automatically stopped, and the following warning message is shown until Patch Management supports the operating system version.

After Patch Management starts supporting the upgraded operating system version, the warning message is no longer shown, and scanning and patch deployment activities resume.

Warning message: Unsupported OS upgrade.

If you create a deployment job for any such assets, the job is not sent to them. You can see the status "Not Applicable" and the warning message for such assets from the Job Progress page. You can view the reason by clicking the count under the Skipped column.

Status and Warning Message on the Job Progress Page.

Reason for patches skipped.

Subscription-level Setting: Download Patches from the Internal Repository

With this release, we introduced a subscription-level setting, Download Patches from the Internal Repository.

At times, it's not possible to open the vendor URLs to download patches due to some constraints, one of which is the Air Gap Network. Also, despite using a proxy configuration like a VPN, it's not possible to download patches from the vendor URLs.

In such cases, you must enable the Download Patches from the Internal Repository setting to allow cloud agents to download the patches from the internal repository server. For more information, refer to the Subscription Level Settings for Patch Management section from the Online Help.

This setting applies only to Windows and Mac platforms.

Download Patches from the Internal Repository.

If this setting is enabled, when you create or edit the Windows or Mac job, you can enable the Download Patches from the Internal Repository setting from the Additional Job Settings section on the Deployment and Reboot Communication Options page.

Then, you can select the name of the internal repository server from the Select Name list. The URL associated with the server is auto-populated. Note that you can add only one internal repository server. For more information, refer to the Creating Patch Job for Windows Assets and Creating Patch Job for Mac Assets topics from the Online Help.

Additional Job Settings section - Job Creation page.

Patch Tuesday Support for All Three Platforms

Before this release, scheduling Patch Tuesday jobs was supported only for the Windows platform. Moreover, the job could be run only after Patch Tuesday.

With this release, scheduling the Patch Tuesday jobs support is also extended for Linux and Mac platforms. In addition, you can create a deployment job that can run on the specified day before Patch Tuesday. For more information, refer to the Online Help.

Run Patch Tuesday job before Patch Tuesday.

Amazon Linux 2022 and 2023 Support

We have provided patching support for Amazon Linux 2022 and 2023 Linux assets.

Amazon Linux 2022 and 2023 Support.

Ubuntu 16.04 ESM Support

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

Prerequisite

The ESM repository must be configured on your Ubuntu 16.04 systems. Ubuntu 16.04 support for Linux Assets.

macOS M3 Support

We have provided patching support for macOS M3 architecture.

Rows Shown Selection Retention

With this release, your "Rows Shown" selection is retained until you log out of the Patch Management session.

Before this release, the "Rows Shown" value selected from one tab was reset to the default value of 50 when you navigated to any other tab.

Rows shown selection.

New Tokens

Token

Tab

Description

customPatchUrlConfigured

Jobs > Windows

Jobs > Mac

To find Windows and Mac jobs for which the Download Patches from the Internal Repository setting is enabled and the URL from which to download the patches is added. The cloud agent downloads the patches from that URL.

Supported values: true and false.

rebootOnly

Jobs > Windows

To find Windows jobs to which only the "System Reboot" pre-action is added. Apart from this pre-action, no other pre-action, post-action, or patch options are added to such jobs.

Supported values: true and false.

Issues Addressed

The following reported and notable customer issues have been fixed in this release.

Component/Category	Description
PM - Job Windows	We fixed the issue where the deployment job was not sent to some of the assets from the linked job.
PM - Mac Agent	Before this release, the macOS software packages were not excluded using the not vendor:`Apple` query while creating a Mac deployment job. To address the issue, we have added guidance to the respective job creation step and updated the documentation to include examples of the recommended QQLs.
PM - Job Notification	We fixed the issue where the customer received the job start and completion emails twice for the same job run.