As noted in my blog post, please, please do not do this. The links are in my blog post on why, but in short, Win32_Product is evil.
J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matthew Varnado Sent: Monday, October 17, 2016 3:54 PM To: firstname.lastname@example.org Subject: RE: [EXTERNAL][mssms] Live Meeting Uninstall Simple shell script solution (untested with this product, but works for other products regularly) wmic product where 'name like "%%Live Meeting%%"' call uninstall /nointeractive note the single quotes around the logic phrase, and the double quotes around the search string. Double % are used for the wildcards because if you do single % it tries to find a variable by that name. This also assumes only a single version would be installed at a time. Run multiple times for multiple installs (if possible), or work out a FOR loop to execute the command for each match found. Another option (requiring a lot more research) is to find all the PIDS and do a series of msiexec /x[PID] /qn commands. Matt Varnado | From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Brian McDonald Sent: Monday, October 17, 2016 2:27 PM To: email@example.com<mailto:firstname.lastname@example.org> Subject: [EXTERNAL][mssms] Live Meeting Uninstall Hello, Does anyone have a method or process for uninstalling ALL versions of Microsoft Live Meeting. In my environment we have approximately 9 different versions of Live Meeting. Since the installers are all MSI based, I was hoping there would be an easy way to script/automate the uninstall so I would only require 1 single package to get the job done in SCCM. When I say multiple versions, here is what I mean: 8.0.6362.187 8.0.6362.202 8.0.6362.215 8.0.6362.223 8.0.6362.229 8.0.6362.239 8.0.6362.249 8.0.6362.254 8.0.6362.259 What would be the best way to package an uninstall script to tackle this? I don't want to have multiple MSI uninstall packages. Can someone provide some insight on to a recommended approach? Thanks, Brian ________________________________ Confidentiality Warning: This transmission is intended only for the proper recipient and may contain information that is confidential and/or privileged. If you received this message in error or are not the intended recipient, (A) you are hereby notified that the dissemination, distribution or copying of this message is strictly prohibited, (B) please notify the sender at either the e-mail address or telephone number above, and (C) delete this email from your computer. Thank you.