that is how I do it. I have a script for it if you want it. 7 lines. Have used it for a few years now to both install and remove updates.
On Wed, Aug 3, 2016 at 12:03 PM, Chris Carbone < [email protected]> wrote: > You could always use the application model and this would only run if > those updates are detected. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Murray, Mike > *Sent:* Wednesday, August 03, 2016 11:29 AM > *To:* [email protected]; Patch Management Mailing List < > [email protected]> > *Subject:* [mssms] Easy way to remove MS16-087 > > > > We’ve already deployed this update, now I’d like to remove it. Would there > be any issue just deploying one removal batch file to all workstations > (rather than trying to identify which workstations have each one)? > > > > BAT: > > > > @echo off > > wusa /uninstall /kb:3172985 /quiet /norestart > > wusa /uninstall /kb:3163912 /quiet /norestart > > wusa /uninstall /kb:3170455 /quiet /norestart > > > > > > Best Regards, > > > > Mike Murray > > Desktop Management Coordinator - IT Support Services > > California State University, Chico > > 530.898.4357 > [email protected] > > > > Remember, Chico State will NEVER ask you for your password via email! > > For more information about recognizing phishing scam emails go to: > http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml > > > > > > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > >
