Score:0

SCCM collection evaluates major version numbers in unexpected way

in flag

Why do SCCM collections based upon the logic Installed Applications (64).Version is less than "100.0" not evaluate to true for applications of version 99.* and below?

The full WQL query statement is as follows, (linebreaks for legibility)

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client 
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 "Mozilla Firefox%" and SMS_G_System_ADD_REMOVE_PROGRAMS_64.Version < "100.0"

Mozilla Firefox recently went from version 99.* to version 100.0, and this has caused collections to stop evaluating lower versions as "less than" 100.0; there are stopgaps in place to get around this, but would prefer to better understand why it is occurring and how to remediate it properly.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.