How Does a Cron Schedule with Daily Recurrence Based on a Monthly Calendar Work?

When using cron schedules for tasks with a daily recurrence based on a monthly calendar, the schedule is defined by specific cron expressions. Here’s how it works:

Example Cron Expression: 0 4 3 1/3 * ? *

  • 0: Seconds field, meaning the job runs at the start of the minute.
  • 4: Minutes field, meaning the job runs at 4 minutes past the hour.
  • 3: Hours field, meaning the job runs at 3 AM.
  • 1/3: Day of the month field, meaning the job runs every 3 days, starting from the 1st day of the month.
  • *: Month field, meaning the job runs every month.
  • ?: Day of the week field, meaning no specific day of the week is selected.
  • *: Year field, meaning the job runs every year.

It Means
The above cron expression, the job will run at 3:04 AM on the 1st, 4th, 7th, 10th, 13th, 16th, 19th, 22nd, 25th, and 28th of every month.

Additional Examples:

  • Running Every 7 Days: If a job is configured to run every 7 days, it will execute on the 1st, 8th, 15th, 22nd, and 29th of each month.
  • Running Every 9 Days: If set to run every 9 days, the job will run on the 1st, 10th, 19th, and 28th of each month.

How can I find the missing patches for the devices?

Create and a run a missing patches request job to identify missing patches. After the completion Missing Patch Scan job, users can view the Missing patches under Configuration Management → Patch Management 2.0 → Menu → Missing Patches.

You can view the Missing Patch list for each device under Infrastructure→ Resources → Select Resource → Patches.

What are the different types of approvals?

  • Auto approval: Automatically approve patches. Auto approval is applicable to Windows only.
  • Manual approval: Manual approval is needed to install a patch.

What happens when the device fails during the patch windows?

To perform any patch related tasks, the agent should be up and running on the device. If the Patch installation fails, alerts will be generated. The failure details including patch and device information will be available under Configuration Management → Patch Management 2.0 → Menu → Installed.

What happens when the device needs to be rebooted after patching?

If configured to reboot servers after patching, the following message is displayed: "Patching completed and need to reboot"

You can ignore the reboot if automatic reboot is not enabled.

What is the reason to create a Patch Scan Schedule?

Use a job to gather missing patch details from the servers configured at the device.

What is the reason for the mismatch between local machine patches and server patches?

Confirm that the server settings are a Microsoft server or WSUS server, local.

Are incidents created during patching?

No, Incidents are not created during patching. However, if there are requirements to create incidents, then users can deploy Alert Escalation Policies by defining the filter criteria to look for Patch related alerts for escalation.

Where can I find the Windows Defender patches installed by the OpsRamp Agent?

Windows Defender patches will not be displayed in the Control Panel, whether it is installed by a third-party application such as OpsRamp Agent or by Windows Defender itself.

You should navigate to Event Viewer to view the information about Windows Defender patches installed by the OpsRamp Agent or any third-party applications.