How come this relevance query doesn’t pick up every Win10 system that actually IS relevant to this query?
version of operating system < "10.0.15063.502"
I’ve opened a case with Support, but they sent me here. I am pretty certain it’s not an issue with my relevance query, but hey, I’m open to learning…
So the relevance is picking up some endpoints? If the relevance is working against some, it’s obviously valid. The clients that aren’t reporting correctly would have to be looked at individually.
Are you using a 9.5.3 or later client? The 4 position OS version wasn’t present until then.
Current version using 9.5.6.
In this comparsion, does “version of operating system” get cast as a string, or does the string “10.0.15063.502” get cast as a version? String comparison versus version comparison could make a difference, and I’m not sure which occurs here.
Try
version of operating system < version "10.0.15063.502"
You might try this: version of operating system < "10.0.15063" which may be sufficient.
What can you say about the systems that don’t seem to work the way you expect?
We were using 9.5.2 actually before…looks like things are working now. Thanks all.
Yes 9.5.2 wouldn’t have supported the 4 place versions on Windows OS versions.
what about 9.2.7 version, is this has option to check Win10 OS buildlabEx option.
Because some customer wants 15063.502 and so on, as they check cumulative updates not similar to all the systems. example some systems win10 version with 15063.502 and some 15063.786. Why is this difference??
suggest Please .
9.2 agents are not supported on these versions of Windows 10 that added the build number. For Windows 10 Anniversary Update & Creators Update the Minimum Agent level is 9.5.3. For Windows 10 Fall Creators Update or later the Minimum Agent level 9.5.7.94
thanks for the confirmation.