Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Preparing for the ITMU – PatchStatus vs. PatchStatusEx – What’s all the fuss?

April 26, 2017blog fuss mom preparing SMS vs Windows

0

Posted

Preparing for the ITMU – PatchStatus vs. PatchStatusEx – What’s all the fuss?

1 Answer

0

Posted

If you (or someone in your environment) have created customized Queries, Collections, or Web Reports for security patch status, you may need to revise these customizations to obtain the data returned by the ITMU. The following classes were added with SMS 2003 Service Pack 1: PatchStatusEx PatchStateEx ApplicableUpdatesSummaryEx These views contain all data from their predecessor (e.g. PatchStatus -> PatchStatusEx), and also contain additional information to help uniquely identify updates. The newer SMS scanning tools (i.e. Inventory Tool for Dell Updates, and Inventory Tool for Microsoft Updates) require these newer fields, and do not update information in their predecessor. To clarify, if you have Web Reports, Queries, or Collections that depend on PatchStatus, PatchState, and/or ApplicableUpdatesSummary, all queries must refer to the new SQL/WQL fields to obtain data from the new scanners. Take a look at EricHoltz’s blog for an article titled “Which views should you use for patch sta