Assuming you are using the Shavlik Scheduler. If the scan didn't run yet, go to Manage > Scheduled Console Tasks (9.2). Look for the Scheduled Scan and right-click for more options. It's going to be very difficult to prevent the machine from rebooting if the scan and deployment already happened. Let me know what you see.
Yes tried all this but the option Delete doesn't do a thing. I can reschedule but it is not what I want to do.
If I select delete it doesn't complain or any thing but also does nothing.
These jobs are scheduled for next Thursday.
What version of Protect are you running?
Darn, Protect 9.2 uses the MS Scheduler and interfaces into it. My thought was to manually delete the patch scan jobs from the MS scheduler.
It the Delete isn't working, you need to create a case with support so they can take a look at logs, and possibly jump on a WebEx with an escalation engineer.
It would save time if you would collect logs and take screenshots of what you are seeing.
1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.
2. Close the Protect GUI.
3. Stop the following services
a.Shavlik Protect Console Service
b. ST Remote Scheduler Service
4. Delete all the logs from
a. Windows 7, 8, 2008, 2012 & Vista: C:\ProgramData\LANDesk\Shavlik Protect\Logs
b. Earlier OS’s: C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Logs
5. Start the console service and open the Protect GUI.
6. Attempt to reproduce the issue. Attempt to delete the scheduled jobs, please include screenshots of where you are deleting from.
a. Collect the logs from the Logs folder mentioned earlier in step 4 (please zip if possible)
b. Since we are dealing with the scheduler, please zip and attach a copy of the entire C:\Windows\Propatches folder and its contents (you can leave out the Patches sub-folder).
7. Zip and attach all the requested information.
Please reference this post in the case.