An analysis can contain many properties, so the clients donât check the value returned by the property and then only becoming relevant if that is true.
The clients first check the relevance clause(s) and if the relevance evluates to TRUE then the properties are evaluated.
For example, your property above is looking at the Windows registry, so will only give results on a Windows computer, so you might have relevance of windows of operating system
to stop it evaluating on Macs, Linux boxes etc.
What would you like to happen? Or what are you trying to do?
As explained above, and as youâve currently configured the analysis, it is expected that all computers in the organization are relevant to the analysis since you set the relevance of the analysis to true.
Iâll try to help, but first a couple of Forum usage tips -
You might have better results starting a new thread. This thread is already marked as Answered so some people may not open and see the new question.
The screenshots are very helpful, but itâs also helpful to copy & paste the relevance text and registry paths as text. Iâm reading on my phone, and retyping all of that path is a lot more error-prone than if I could copy & paste the path.
That said, for a registry search like this you can use the âkeys of keysâ property where the name of the subkey is not known. Here it would be something like
values "AccountTrackUsage" of keys "PrinterDriverData" of keys of keys "Software\Microsoft\path-to-servers-something-printers" of user keys of logged on users
`user keys of logged on usersâ will get you to the path of HKEY_USERS\SID, so the âpath-to-serversâ will be start with Software\Microsoft