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:
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:
In certain sections of our business, some specific changes are made on specific days on the week. This includes some app updates.
Whilst we could adjust the sync schedule for everyone, we'd rather not move away from daily syncs. Instead, it would be better to be able to set specific days that updates are released for certain app deployments, that still follow any set update ring cadence.
For example, only deploy App A updates on a Wednesday. If an update to App A comes along on Monday, wait until Wednesday until it deploys to it's first update ring. From then on every update ring should also deploy on a Wednesday.
Another way this could work is to have an option that only deploys updates on the first "specific day of the week" after an update releases, and then subsequent deployments to any update rings would be at set intervals on the same "specific day of the week".
I appreciate this is a niche request, but it would be nice to have :)
Currently using on-prem Publisher with SCCM. To have better change predictability, and reduce possible impact on users (such as having to restart an application or restart a device), we have enabled a daily sync of the Publisher, and created a series of automatic deployment rules to run (i) once a month and grab most updates released in the last 30 days, and create multiple staged deployments, and (ii) once a day for select critical softwares such as web browsers, with a single deployment.
Looking at PMPC Cloud capabilities, it appears like such a methodology cannot be replicated. Update rings seem to be necessarily calculated on a per-app basis, and rings are delayed on each application's release date. That could result in having apps updates multiple times per week.
Would be great -- especially for predictability -- if one could set on a per-app basis when Ring 0 gets created, and then have the following rings delayed based on Ring 0 deployment time. For example:
set NonCriticalApp update rings deployment evaluated on Second Tuesday of every month. If a new version of NonCritialApp has been released since last Second Tuesday, then proceed with Ring 0 assignment, followed by Ring 1 assignment on Second Tuesday+X days, Ring 2 assignment on Second Tuesday+Y days, etc.
set NotSoCriticalApp update rings deployment evaluated on Monday of every week. If a new version of NotSoCritialApp has been released since last Monday, then proceed with Ring 0 assignment, followed by Ring 1 assignment on Monday+X days, Ring 2 assignment on Monday+Y days, etc.
set SuperCriticalApp update rings deployment evaluated every 1 day. If a new version of SuperCritialApp has been released since last 1 day, then proceed with Ring 0 assignment, followed by Ring 1 assignment on N+X days, Ring 2 assignment on N+Y days, etc.