SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceID = SMS_R_System.ResourceId where (SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like “Google Chrome%” or SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName like “Google Chrome%”) Great post - I have used this now to build the search group using both 32 and 64 bit. This same technique can also be used to query for versions greater than a specific version and has helped me more reliably query application versions. This does, however, only find 64-bit versions of Chrome, so we may want to duplicate these same statements for 32-bit by using the SMS_G_System_ADD_REMOVE_PROGRAMS table. SELECT * FROM SMS_R_System INNER JOIN SMS_G_System_ADD_REMOVE_PROGRAMS_64 ON SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId WHERE SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName LIKE "Google Chrome%" AND (SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version LIKE ".%" OR SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version LIKE ".%" OR SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version LIKE "9.%" OR SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version = ".79" OR SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version = ".88")Īll stable Chrome versions less than. We’ll use equal operators (=) to explicitly address each of these: WHERE SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version = ".79" WHERE SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version = ".88"įinally, the query is complete with a little formatting: Google’s stable release history for Chrome shows that only two stable sub versions of 79 have been released prior to our target. Next, some version insight helps reduce some work. Note that we also have to use two sets of brackets since each set only addresses a single character. This statement gets nearly all of that: WHERE SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version LIKE ".%"īut we’ll also need this to compensate for versions 19, 29, 39, 49, 59, and 69: WHERE SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version LIKE "9.%"Īs before, the wildcard (%) is used to ensure we get all sub versions. Next we need to capture versions 10 – 78. The percent sign wildcard (%) is used after the period in order to get all sub versions. This is accomplished with the partial SQL query statement: WHERE SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version LIKE ".%" LIKE allows the use of brackets () to specify a range or set of characters, as well as a percent sign (%) as a wildcard to specify a string of zero or more characters.įirst, we’ll need to query for all version 1 – 9 (single digit versions). The LIKE operator is what we’ll leverage to get the results we need. The less than operator (<) will evaluate the Chrome version.
My solution is a bit tedious, but it does reliably work.ĭespite its appearance, the following partial WQL query statement will not work: WHERE SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName LIKE "Google Chrome%" AND SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version < ".117" Say we want to query all stable versions of Google Chrome that are less than version. More info from Microsoft on WQL can be found here: Recall that WQL (subset of SQL) is used to query data from SCCM, so we are restricted by WQL’s limitations when comparing String values. This is because version numbers are stored as Strings in the SCCM database.
Creating a query for a specific version works great using the equal operator (=), but searching for version greater than (>) or less than (<) a specific version becomes difficult. One challenge IT techs may face is trying to query application versions within SCCM. Successfully Tested On: Microsoft System Center Configuration Manager versions 2012 R2 - 1906, Microsoft Endpoint Configuration Manager versions 1910 - 2010
0 kommentar(er)
