Patching "run now" is just the most dangerous thing I have seen
There is zero validation dialog on "run now" for both windows and dell patches. AND it is right next to the edit button.. that being said.. has anyone come up with a way to not inadvertently restart all your servers in the middle of the day? I guess I could do a 1 hr notification with a cancel option on it. Id have to scramble to all my servers and cancel manually.. But then my schedule would be weird because Id need to take that into consideration.. Is this what people are doing to avoid being fired for one errand click? Anyone have a script to abort a patch?
Im not even going to think of recommending a validation dialog.. kace has been around for years and they have just left the run now as is. How completely insane.
well, "Run Now" just starts the task.
If you have "wrong" reboot option for you it is a config setting.
And tbh in the last >10 years I never accidentally clicked this button. (in other tools this happens more often that I click the wrong one by accident I need to confess)
I definitely agree with your statement. It could be really great to add a step to confirm the run now (with eventually a resume of targeted computers).
If you launch it by mistake, you can try to applly the following KB :
Something similar happened to me last year after SMA upgrade : A Dell patch schedule was set but with no targetted device. Despite of this, it started to patch all of my computers and servers. Indeed, there was the OS filter set on "All OS" and if it is set like this it will target every computer and server matching this OS filter with no regards that you didn't explicitely define a device as target. In other module of KACE, there is a complementary button that you can check to select "All Devices" and which prevent this to happen if it is unchecked.