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:
As of now one group can only be assigned one time in an application deployment. I would like a way to allow an exclusion group to be applied multiple times in a deployment. IE Zoom is deployed as required with 3 update rings. In order to troubleshoot an issue I need zoom removed and to not get reinstalled so I create a group "zoom troubleshooting". To ensure zoom would not get reinstalled I had to create a separate group for each ring of my deployment and add my troubleshooting group as a member. Ideally i would like to just have the troubleshooting group be able to be excluded from each "ring" of the deployment.
We took note of this limitation in our Portal.
You can only exclude a group (let’s call it Group A) one time across all Rings. So if you exclude Group A in Ring 1, that same group can’t be excluded again in Ring 2 or Ring 3.
Here’s what happens:
When a new version of the software is packaged, the Ring 1 assignments (including the exclusion of Group A) move from the old version (n-1) to the new version (n). So Group A stays excluded in Ring 1 for the new version n.
But the old version (n-1) still has assignments for Ring 2 and other Rings. However, Group A is no longer excluded there, as it was moved to version n.
Until we handle such scenarios better in our product, here’s what we suggest:
Create separate groups for each Ring (like Group A, Group B, Group C, etc.).
Make sure all these groups have the same membership.
Then, exclude each group in its own Ring:
Ring 1 → exclude Group A
Ring 2 → exclude Group B
Ring 3 → exclude Group C
and so on...
We know this isn’t perfect, but it’s the best workaround for now until we improve how this works.