I would love to be able to assign priority to items that are being or have been deployed. Similar to the idea of distribution priority. This would ideally be an option for anything deployable, such as software updates, task sequences, and/or applications.
I do a lot of testing. We have various things deployed to collections that computers will always be a part of. It's very frustrating to get stuck behind a string of security updates when I am rebuilding a machine to test it fresh. It would be nice to attach a higher priority to an item so it will install ahead of patches. Could save some time.
I know there are plenty of ways to accomplish this such as exclusion rules, I would just like to assign a higher priority to a deployment or item.
Machines that are offline and have multiple deployments, SCCM will randomize the deployment to install. There seems to be no order in which they will install. We would like the ability to determine during deployment time a priority. This would be similar to when packages are deploying content to the distribution points.
Software Updates | Zero Day – High Priority
Important\Regulatory – Medium Priority
Regular Deployments – Default Setting Low Priority
If we had the ability to set the priority, when a machine is offline and has multiple deployments to install, we have the ability to have the high-profile deployments install and not waiting days to install due to waiting. We have maintenance windows during the daytime to reduce the amount of downtime for our end users. We have users that are not connected for weeks at a time and have multiple deployments and updates to install.
Marko Mård commented
And when you are deploying an image to a machine that has a lot of updates and apps on queueu, it would be nice that the opeating system deployment task would always be the number one in the list, so time is not spent installing apps that are going to be installed again anyway.