Skip to Main Content
Patch My PC Ideas & Feedback

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:

3 VOTE
Status SUBMITTED
Created by Christopher Dine
Created on Aug 17, 2025

Group multiple UPDATES and run them together instead of one by one.

We are currently performing a monthly desktop publisher sync following our month end processes in the business.

The result of this is that 7 days later when our next general population ring group becomes eligible... The users get a number of patches one after the other at the whims of the Intune processes.

The toast popups are rather discrete and easily missed.
Also the restart grace period somewhat compounds this as again its hidden until later on.

We would like to bring in the restart grace period so that users are not attempting to use half installed software. But that may result in them being asked to restart multiple times a day.

My idea is that the installation of deployed packages occurs as a group instead of one by one.
How I imagine this may work is that as packages flagged to be grouped together arrive, they instead cache their contents locally and attach themselves to a scheduled task.

As each new package arrives, they check for an existing schedule and cache and add themselves to this to be processed.

Understanding that Intune attempts and timeout thresholds do exist... The schedule would need to run within a certain time.
Perhaps configured to run within X hours since first package or Y hours since the last package added to the list? Or at a fixed time later that day. Or if the device was shut down before any of those could occur, on the next startup.

The schedule would then alert the user with a popup on screen, not just toast, the full list of apps that are being patched and that they need to save their work and exit out of them.

The usual timeout and conflicting apps would apply. Snoozing on a group package would result in the schedule either sleeping in the background or rescheduling itself to run later with a new trigger.

Ideally there would also be ongoing communication with the user. At the very least a confirmation that everything is done and ready to go. But ideally the initial prompt kept on screen and updated with its ongoing progress.

My overall goal with this is to reduce user disruption for requiring multiple device restarts in the day.
Improve user communication with prominent on-screen popup prompts.
As well as the ability to schedule apps to run at specific times instead of at the whims of the IME process.

  • Attach files
  • +2