Registry Relevance for keys that may or may not exist

(imported topic written by brady_admin91)

I am deploying XP SP3 and we have several machines in our environment that need to be excluded from the action. I have created a custom fixlet which creates HKLM\Software\BigFix\Exclusions\XPSP3Exclude with a value of “Excluded” in the registry.

My problem is this:

Only machines who need to be excluded with have this key in their registry

What is the correct relevance to look for a key that may or may not exist?

Currently I am using this at the end of my relevance:

AND (not exists value “XPSP3Exclude” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Exclusions” of native registry)

This evaluates to True on machines where this key exists but fails where this key is not present. I get an error in the relevance debugger stating that “singular expression refers to nonexistent object.” Any help here is appreciated.

(imported comment written by jessewk)

A little pluralization usually goes a long way…

not exists value “XPSP3Exclude” of keys “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Exclusions” of native registry

(imported comment written by brady_admin91)

Great Scott that’s it. It’s always the small details. Thank you.