Hi Brian, and let me apologize for not getting back to you earlier (I somehow “missed” your original post, sorry
I believe ADNM has a feature that is designed EXACTLY for the cases your describing.
When you open the scanning task’s properties, you’ll notice the “Processing” page. This page offers three controls, one of which is called “Task Session Expiration”. This is the option you’ll want to modify. It basically tells the management server for how long the session will be held in the “Waiting” state before it actually starts executing. In other words, if the client doesn’t start execution of the task before this period expires, the session simply becomes invalid (gets a FAILED status, with the appropriate “Timeout” error code) and will not be run on the machine anymore.
By default, the expiration period is set to 1440 minutes which is equivalent to 24 hours. If you change this to e.g. 30 minutes, you’ll confine the scan only to the machines that will be online between 12:00 and 12:30. If a machine is not turned on during this period, the task will not start.