system
15
Honestly, if the console message that obsolete clients are still in use on your network had a “fix it!” button that scheduled a new job, to silent deploy, with the force reinstall (existing) option set, scheduled imediately, with the selected computers already populated via the list that show up in the console message… That would probably solve 99% of the deployment issues.
In doing some experimentation, that job with the forced reinstall, worked for most of my problem cases. YMMV.
I just wish that instead of giving the user a rather unfriendly - your system will now restart - message, with no real opportunity to save work before it is lost, there was a more friendly way of doing the “forced” restart. I’d suggest a 4 or 5 minute timer on that message window (your computer will restart in n:nn, please save your work) with either a “postpone” or “restart” button instead of the it will happen message with an “ok” button. Unattended machines will restart after the timer reaches 0:00, machines with users in the middle of something can save and hit reboot, or hit postpone, and have the message show up again in 5, 10 or 15 minutes, until they are ready to take a break and let the computer restart.