1 of 1 people found this helpful
You usually want to wrap such things in a check / enforce type thing killing off applications.
And/Or you can use vulscan to do the same thing (it's the same shenanigans we need to go through for Flash updates, killing off browsers, for instance).
And you can use whatever you prefer to script with - we're not going to tie you down. Run with what you're more familiar, is usually my default advice.
NOTE - it also helps communicating stuff out to users. Doing it out of hours helps too. As does a warning that "we WILL hard-close any open processes - so please save your work before leaving" or some such. Some of it may stick (there's always "those special needs" guys who are immune to communications & such of course). But yeah - managing your users tends to be a big help on this (as this stuff is more of a "process / people" problem rather than a technical one. ).
Sounds great. Thanks.