Allow the Deployment of a Task Sequence to have a "Available" date and a "Deadline Date" .
I'm deploying a Task Sequence to update our company's machines Bios to mitigate the Meltdown/Spectre. It would be helpful for the enduser, that SCCM would be able to deploy the Task Sequence with a "Available" time/date and a "Deadline" time date, this way the end user is not surprised by the TS being deployed as "Required" and the auto reboot catch's them by surprise.
Stephen K. commented
Are you sure SCCM doesn't have this already? Both packages and task sequences have this in the deployment wizard, although it's called "assignment schedule" rather than "deadline."
The available time is under "Schedule when this deployment will become available"
The required/deadline time is under "assignment schedule" which can be as soon as possible, or once at a future time, or even on a scheduled recurrence interval.
Or is there some other side effect of this wizard that makes the behavior different from what you're asking?
It is similar story with Windows 10 OSD Upgrade TS, in a scenario of deploying 1809 Feature Pack user notification is suppressed/not available unless they go to Software Centre to see pending TS deployment with a deadline set for 30 days (for their convenience).
How many users are going to Software Centre if they are not notified?? - ZERO
That feature would be useful for forcing users to update their computers after set deadline. Currently it's available only Application/Updates deployment - not for TS.