Managing Patch Jobs for Windows Assets

You can deploy jobs to install patches that are missing or remediate any identified vulnerabilities. Based on your preference, you can deploy a patch job from any of the following tabs:

  • Jobs
  • Assets
  • Patches

The difference between the two options is when creating a job from the Jobs tab, you select the assets while creating the job, where as when creating job from Assets tab, you select the Assets first and then create deployment job to deploy patches on those assets. The assets are pre populated for the job when creating deployment job from the Assets tab.

Job title for each job must be unique. You cannot have the same job title as a Linux job. For example, if a Linux job titled Security Patches is created, you cannot have a Windows job titled as Security Patches.

About Zero-Touch Patch Jobs

All QQL-based recurring jobs are known as the Zero-Touch Patch jobs. All zero-touch patch jobs are denoted with the zero-touch icon Zero-Touch Icon.

The Zero-Touch Patch Job option allows you to create an automated job to proactively patch current and future Windows vulnerabilities.

Zero-Touch Patch Job List

Want to create patch jobs for Windows assets?

See Creating Patch Job for Windows Assets.

Want to roll back patches?

See Roll back patches from assets.

Good to Know

User Roles and Permissions

List of Asset Statuses