Jason
My feedback
-
49 votes
An error occurred while saving the comment Jason
supported this idea
·
-
20 votes
An error occurred while saving the comment Jason
commented
That is the total opposite? If it is required, it can download and if available you have to wait until user Initiates the installation. What you can do is set it to required and set mandatory the same time as the expiration (Through SDK) and offer time prior to the mandatory and it will download.
-
15 votes
-
173 votesJason
supported this idea
·
-
3 votesJason
shared this idea
·
-
3 votesJason
shared this idea
·
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.
Example:
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.