How can we improve the SMA (K1000)?

Patching alert improvements

Past experience shows that whenever a set of patches is applied, even if “No Reboot” is chosen that a large percentage of the time the workstation is booted anyway. We don’t use this option anymore. We have one schedule set to detect … and another schedule set to deploy. The deploy job has an alert and is set to force a reboot. This allows our users have a chance to consent to a reboot during the day (laptops).

I just spoke with a support person and they confirmed that a deploy job has a max timeout of 1 hour, no matter what is specified in the deploy job. Our business model really needs a longer alert.

It is our wish to present an alert and ask the user to leave it there for most of the workday, say 8 hours ... until it’s convenient to him/her to patch and boot. A good example would as they leave for lunch or a long meeting. They can click “OK” to the alert and then expect a reboot.

Support also mentioned that a “Detect and Deploy” job has a 3 hour timeout. This doesn’t fit our business model. We need to run a detect job and later a deploy job so that the alert timing is more predictable.

Thanks!

4 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Devin Meade shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base