(imported topic written by murtasma91)
I’m trying to create a custom client property that will be used to determine the support level for a workstation. What we want is a task that has 3 actions that sets the custom property to a certian value depending on the action selected. From these 3 actions will will create a standing offer so users can select what support level they want their workstation to be placed in.
This all works correctly but once a setting has been chosen for the custom setting we want all three of the tasks to show up as not relevant. If a user wishes to change their support level in the future they will need to contact the support staff so they can remove the custom property from the client workstation thus making the 3 standing offers relevant again.
We thought it would be as simple as editing the computer settings, selecting the custom setting and pressing the delete button. This however doesn’t work as inteded because the delete button only removes the “value” subkey but leaves the effective date subkey behind (I’m sure this is by deisgn).
The other 2 actions still show up as relevant after a user selects a support level so in order to change this behavior I am working on creating some custom relevance for the tasks that actually look for the precesne of the “value” subkey instead of the following relevance
not exists setting
"_Support_Level" of client
(This expression returns false even if you use the delete button under computer settings since it leaves behind the effective date subkey under the Client settings section in the portion of the registry that contains BigFix client information)
I am testing on Windows 7 64 bit
The following expression works as intended
not exists value
"value" of key
"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\EnterpriseClient\Settings\Client\_Support_Level" of registry
however the following expression retruns results incorrectly
not exists value
"value" of key
"HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\Client\_Support_Level" of registry
I need to evaluate both of these keys since the BigFix client stores information in the registry at a different location if it’s a 32 or 64 bit OS.
The syntax for both of these expressions are the same, the 64 bit path works as inteded but when I manually create these Keys and Subkeys in my registry hive for where the 32 bit version would be stored I keep getting incorrect values. When I view the graphical breakdown of the following expression on a 64 bit OS
not exists value
"value" of key
"HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\Client\_Support_Level" of registry
I get a undisplayable result message under the “value” and “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\Client_Support_Level” portions of the expression
Why is this happening? This is just a simple query to test for the existances of a key.
UPDATE: Just tested the following code on a Win 7 32 bit machine
not exists value
"value" of key
"HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\Client\_Support_Level" of registry
On a 32 bit Win 7 machine this returned the correct value. Looks like there may be a bug in the BigFix client when evaluating keys under the Software\BigFix key on a 64 bit os.