Fixlet debugger evaluates to True, client evaluates to False

Content Authoring
1

(imported topic written by SystemAdmin)

Seeing some weird behavior with a simple relevance to detect Adobe Reader clients with JavaScript enabled. Relevance looks for a registry entry and if its value is “1”, then JavaScrip is enabled and machine needs a reg change pushed out to it via BF. When I evaluate my relevance via Fixlet Debugger, it evaluates to True, however all machines I sent this to are reported back as “not relevant”, including the one I’ve tested with debugger on.

I downloaded BigFix Client API tester to test via native client directly, and it too evaluates to False, while Fixlet debugger evaluates to True.

Fixlet debugger: http://tinypic.com/r/11tmo1y/7

API Tester: http://tinypic.com/r/2dimzht/7

I suspect it has something to do with client running under System context and unable to access HKEY_CURRENT_USER? Is this really the case? If yes, how do you get around this limitation?

P.S. In case anyone needs to see it, here’s the entire relevance:

(name of operating system starts with “Win” AND (exists regapp “besclient.exe” whose (version of it >= “7.2.4.60”)) AND exists regapp “AcroRd32.exe” AND exists key “Software\Adobe\Acrobat Reader\10.0\JSPrefs” whose (value “bEnableJS” of it as string = “1”) of key “HKEY_CURRENT_USER” of registry or exists key “Software\Adobe\Acrobat Reader\9.0\JSPrefs” whose (value “bEnableJS” of it as string = “1”) of key “HKEY_CURRENT_USER” of registry)

2

(imported comment written by jeremylam)

Your suspicion is most likely correct. Since the Client runs as the System User, checking HKCU will check the System User’s registry keys, not normal users.

However, since it is a problem for all users and not just the current one, you probably want to check all the users on the system (all branches in HKEY_USERS), not just the currently logged on user. This also avoids the problem of requiring a user to be logged on in the first place.

3

(imported comment written by SystemAdmin)

Hi Jeremy,

Thank you for replying. So do I understand this correctly: BF cannot parse HKEY_CURRENT_USER hive in relevance at all? I know that in action I can use “RunAsaCurrentUser.exe” utility to get this to work, but in relevance, there’s really no way to do it?

Thanks!

4

(imported comment written by nberger91)

this example should work for you -

value “valuename” of key “keyname” of current user keys (logged on users) of registry