I’m in the process of migrating our data center to ConfigMgr 2012 R2 CU3 and am tired of having to manually run SQL queries and copy the results into a collection direct membership to push a remediation script for various software update issues.
For example as I migrate machines from the ConfigMgr 2007 to ConfigMgr 2012 site some of the systems are failing to update their local policy to reflect the new Update Source resulting in a ‘Group policy conflict’ scan error. This is easy enough to fix with a script but I’m unaware of any way to access the contents of v_UpdateScanStatus via WQL to create the target collections (and manually changing the SQL behind a query rule in the DB is not something I can do here). This is just one of a dozen common issues that I’d like to be able to simply automate away an initial remediation attempt. My question to the group is what strategies are you employing to automate the remediation of software update scan / client issues when Microsoft exposes the data we need via SQL but is not making that available to us in the console via WQL? Is there some way that I can use Compliance Items to check for scan errors and then have the collections build off of those? Thanks! P.S. Anyone know the reasons behind not exposing more of these diagnostic views available in SQL so they are available in WQL for use within the console outside of reporting?
