We run that software too and I wouldn't wish that mess on anyone... If they've become so bad that they didn't introduce a new MSI product code with the update, then I would run with Sherry's idea to get more information.
However, we have had success (with older versions) by pulling the MSI product code for the patches from the SMS_InstalledSoftware WMI namespace for reporting purposes and you can create collections based on the existence of the MSI product code. Everything else being equal, you could create an application deployment that using the MSI product code and something else (dll version number or file size) for the detection rules. Create a collection based on the base version and then use the "update" as the application that's being deployed to it. Have the base version as a "requirement" of the base application. Those computers that already have the update won't re-run the update (because the detection rules will establish it as compliant) and those that don't have it (that fail the detection) will install the patch. Having the base version listed as a requirement just makes it possible for you to deploy the "update" application to new computers without having to also deploy the base application. The option is also there to use a custom script as the detection rule as well. This isn't necessarily a great option, but it's gotten me around some messy configurations in the past. Thanks, Charlie From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, December 15, 2015 1:04 PM To: [email protected] Subject: [mssms] RE: Collection Based on Installed Update Exactly. I'm trying to find all the computers that do not have this patch installed so I can install it. Not all computers that have it for it from CM either. I think I'm going to try what Sherry suggested. Thanks for input everyone. ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kelley, Matthew Sent: Tuesday, December 15, 2015 11:17 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Based on Installed Update Nevermind, I see you are looking to create a collection - likely to target the advert at! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kelley, Matthew Sent: Tuesday, December 15, 2015 12:14 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Based on Installed Update Ah, there you go. Just check the status message from the package/program/advertisement. It should get you close, as long as the install actually returns a legitimate execution result and doesn't just exit with 0 for everything. I have seen some installers or wrappers that do just that. Failed - exit with success. Makes things interesting! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, December 15, 2015 12:01 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Based on Installed Update "This includes updates installed using enterprise management systems like WSUS<http://social.technet.microsoft.com/wiki/contents/articles/add.aspx?WikiParentPageID=4197&WikiPageKey=WSUS> or ConfigMgr<http://social.technet.microsoft.com/wiki/contents/articles/28576.configmgr.aspx> but excludes any updates installed manually or using custom management scripts." This particular app is updated using a package and program to install an msp, not via software updates. It doesn't show up in these results. And yes, it's a HORRIBLY written piece of software! ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kelley, Matthew Sent: Tuesday, December 15, 2015 10:51 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Based on Installed Update http://social.technet.microsoft.com/wiki/contents/articles/4197.how-to-list-all-of-the-windows-and-software-updates-applied-to-a-computer.aspx $Session = New-Object -ComObject "Microsoft.Update.Session" $Searcher = $Session.CreateUpdateSearcher() $historyCount = $Searcher.GetTotalHistoryCount() $Searcher.QueryHistory(0, $historyCount) | Select-Object Title, Description, Date, @{name="Operation"; expression={switch($_.operation){ 1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"} }}} From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, December 15, 2015 11:45 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Based on Installed Update Doesn't seem to be. ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of James Massardo Sent: Tuesday, December 15, 2015 9:28 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Collection Based on Installed Update Is there a key for it under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall ? Thanks, James Massardo From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, December 15, 2015 8:07 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Collection Based on Installed Update The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. I have an application that, when updated, does not change its version number or anything else easily identifiable. It does however list the update as being installed in the "Installed updates" portion of add/remove programs. I can't seem to recall where that info is stored. Anyone know? The MS updates are in QF Engineering but not the third party ones. ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
