I am leaning towards removing this patch too… I’ve had a case open for 5 days and the problem has been known for almost three weeks with no repair or workaround even being hinted at. For our part, it is only affecting new computers because the universal print drivers cover 95% of our printers and users would have already added one printer covered by the UPD –so other printers using the same driver happily use it.
Recently, the print server team updated one print driver and all hell broke loose because no one could download the updated drivers from the print server. I see a lot of people suggesting to do this with a custom task sequence, but I can’t figure out why. Why can’t this be a sourceless package that just runs the wsua command as the program instead of building a TS around it? What is gained by having it be a one step task sequence that calls a command line? I guess if you did do it as a task sequence you could filter TS steps based on applicability. From: [email protected] [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, August 03, 2016 12:44 PM To: [email protected] Subject: RE: [mssms] Easy way to remove MS16-087 That’s pretty cool! Thanks! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Wednesday, August 3, 2016 10:05 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Easy way to remove MS16-087 This doesn't answer your question--but as long as a kbarticle id (well, the ci_id) isn't yet expired... here's cheat way to get collection queries for "machines which have <kb whatever> installed". It won't work forever, though. the second that article goes expired, the data isn't there anymore to build the collection query. You first run the sql query against your cm database to learn the exact ci_id that something is in YOUR environment (everyone will be different). Once you know the exact ci_id; you can make a collection query--just remember it ain't perfect. with hotfix Tuesday coming up in a less than a week, it's highly likely it'll go expired, and the collection query will then be useless. --#This is where you put in the specific articleID you want to get the unique ci_id for Declare @ArticleID varchar(10) = '3139923' -------------------------------------------- select ucs.ci_id, ucs.status, case when ucs.status=3 then 'installed' when ucs.status=2 then 'required/missing' else 'other' end as 'result', ui.title, ui.articleid ,count(distinct fcm.resourceid) [Count] from v_updateComplianceStatus ucs join v_updateinfo ui on ui.ci_id=ucs.ci_id join v_FullCollectionMembership fcm on fcm.resourceid=ucs.resourceid where ui.ArticleID=@ArticleID<mailto:ui.ArticleID=@ArticleID> --and fcm.collectionid='ThatSpecificcollectionIDYouWantedToLookAt' --and ucs.status=3 --well, you could leave this out; to get all status' group by ucs.ci_id, ucs.status, ui.title, ui.articleid order by ucs.status Once you *know* the exact specific ci_id that is the one you want to build a collection for, here's the trick: --WQL / Collection Query for Machines WITH that particular ci_id Select SMS_R_System.ResourceID from SMS_R_System Where resourceid in ( Select MachineID from SMS_UpdateComplianceStatus Where CI_ID=The value in the ci_id column from the above query for that particular articleid and Status=3 ) --EXAMPLE Select SMS_R_System.ResourceID from SMS_R_System Where resourceid in ( Select MachineID from SMS_UpdateComplianceStatus Where CI_ID=16783193 and Status=3 ) On Wed, Aug 3, 2016 at 11:29 AM, Murray, Mike <[email protected]<mailto:[email protected]>> wrote: 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<tel:530.898.4357> [email protected]<mailto:[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 -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________
