How do I stop Breeze RMM from rebooting machines during business hours?

In the client's configuration policy, set the Reboot Policy on the Patches tab to "During maintenance window", then give the client a window on the Maintenance tab. A patch that needs a restart outside the window waits for it. With "Reboot if a reboot is pending" switched on, Breeze restarts Windows and Linux machines that are still waiting, but only while the window is open.

What day does a weekly maintenance window open in Breeze RMM?

Sunday, at the start time you set, in the window's own timezone. The Maintenance tab has no day picker for weekly windows today. The patch install schedule on the Patches tab does let you pick the day of the week.

What does "Suppress patching" do in a maintenance window?

It skips any patch install scheduled inside the window, and that install waits for the next scheduled run. Leave it off when the window is when you want patching to happen, as in this demo.

How do I roll out updates to a pilot group first in Breeze RMM?

Create two update rings under Patches → Update Rings: Pilot with no deferral and Broad with a 7-day deferral, both auto-approving critical and important updates. Link Broad in a policy assigned to the whole client and Pilot in a policy assigned to a device group. The pilot machines get each update on the first Sunday after release, and everyone else a week later.

How do I check which policy a device actually gets?

Open the device and go to its Configuration tab. Each feature card names the policy it comes from and the level (Device Group, Organization), and the Inheritance Chain lists every policy that reaches the device.

How to Set Maintenance Windows and a Pilot Update Ring

Name: How to Set Maintenance Windows and a Pilot Update Ring | Breeze RMM
Uploaded: 2026-10-22
Duration: 3 min 26 s
Description: Breeze RMM lets you give each client a maintenance window that patch restarts wait for, and a pilot update ring that takes every critical and important update a week before the rest of the office. This video sets both up for one dental office, using configuration policies, without any scripts.

Breeze RMM lets you give each client a maintenance window that patch restarts wait for, and a pilot update ring that takes every critical and important update a week before the rest of the office. This video sets both up for one dental office, using configuration policies, without any scripts.

3:26 Captions: English Open on YouTube

What's in the demo

Patches → Update Rings: "Pilot - IT & Early Adopters" (deferral None, deadline 3 days) and "Broad - All Clients" (deferral 7 days, deadline 7 days), both auto-approving OS: Critical, Important. Both show 0 devices
The client policy "Harbor Point Dental - Patching & Restarts", assigned to the whole organization: Patches tab, Approval Ring "[2] Broad - All Clients (7d hold)", installs Weekly, Sunday, 02:00 AM, Reboot Policy "During maintenance window"
The Maintenance tab: Weekly, start 12:00 AM, Duration (hours) 6, timezone America/New_York, so the window covers the 2 a.m. installs
Reboot if a reboot is pending switched on (Windows and Linux, only while the window is open), Suppress patching left off, Suppress alerts on
A second policy, "Harbor Point Dental - Pilot PCs": same patch settings, but linked to the Pilot ring, and no maintenance settings of its own
Assignments → Level: Device Group → Front Desk Pilot (two front-desk PCs)
Update Rings again: Pilot now shows 2 devices, Broad shows 10 (the whole office)
The front-desk PC HPD-FD-01 → Configuration tab: Patch Management from the Pilot PCs policy (Device Group), Maintenance Windows from the client policy (Organization), and the Inheritance Chain listing both

Questions this video answers

How do I stop Breeze RMM from rebooting machines during business hours?: In the client's configuration policy, set the Reboot Policy on the Patches tab to "During maintenance window", then give the client a window on the Maintenance tab. A patch that needs a restart outside the window waits for it. With "Reboot if a reboot is pending" switched on, Breeze restarts Windows and Linux machines that are still waiting, but only while the window is open.
What day does a weekly maintenance window open in Breeze RMM?: Sunday, at the start time you set, in the window's own timezone. The Maintenance tab has no day picker for weekly windows today. The patch install schedule on the Patches tab does let you pick the day of the week.
What does "Suppress patching" do in a maintenance window?: It skips any patch install scheduled inside the window, and that install waits for the next scheduled run. Leave it off when the window is when you want patching to happen, as in this demo.
How do I roll out updates to a pilot group first in Breeze RMM?: Create two update rings under Patches → Update Rings: Pilot with no deferral and Broad with a 7-day deferral, both auto-approving critical and important updates. Link Broad in a policy assigned to the whole client and Pilot in a policy assigned to a device group. The pilot machines get each update on the first Sunday after release, and everyone else a week later.
How do I check which policy a device actually gets?: Open the device and go to its Configuration tab. Each feature card names the policy it comes from and the level (Device Group, Organization), and the Inheritance Chain lists every policy that reaches the device.

A note on the demo: Harbor Point Dental and its devices are fictional demo data. The device's Configuration tab shows one patch policy, but in this build the patch scheduler can create jobs from both overlapping patch policies, so the pilot PCs also get the client policy's job. The demo keeps both policies on the same Sunday 02:00 schedule and reboot policy for that reason, and the Broad count of 10 includes the two pilot PCs.

Do this on your own fleet

Everything in the video is in the product you get. Start the Cloud Beta in minutes, or self-host the open-source Community edition for free.

Start Cloud Beta Deploy for Free Book a Demo