A software package or some sort of maintenance task needs to be deployed to client machines and will require a reboot. Since the task requires a reboot, it must be done during a specific maintenance window outside of business hours to reduce user impact. With task queuing enabled, the task will go into the task queue if an SDClient lock cannot be acquired.The failure to obtain an SDClient lock can be caused by running software distribution jobs or vulnerability scans.

Not being able to obtain an SDClient lock will cause the task that requires a reboot to wait until the other operations are finished before it can run. Depending on the current operation and other queued tasks, there is a potential for a reboot to happen at an undesired time.

To prevent the scenario above, simply disable task queuing for the task that requires a reboot. Now when the task is pushed during the specific maintenance window, it will fail if an SDClientlock cannot be obtained and will not go into the task queue for later processing. This was the default behavior before task queuing was implemented.