Fixlet is not related (individual relevance is true)

Usage and Config Patch
1

(imported topic written by Satoshi_Kawamoto91)

I contribute it for the first time. I would be grateful for your help.

I wonder that following Fixlet is not related to a computer.

When I confirm it with a Relevance debugger, about the individual Relevance , the client who becomes all true exists.

If there is advice, Please give me it.

Fixlet:

MS10-060: Vulnerabilities in the Microsoft .NET Common Language Runtime Could Allow Remote Code Execution - Microsoft Silverlight 2/3 (Japanese)

Relevance1:

if( name of operating system starts with “Win” ) then platform id of operating system != 3 else false

Relevance2:

(language of version block of file “kernel32.dll” of system folder contains “Japanese”) AND ((not exists key “HKLM\System\CurrentControlSet\Control\Nls\MUILanguages” of registry) OR (not exists value of key “HKLM\System\CurrentControlSet\Control\Nls\MUILanguages” of registry))

Relevance3:

not exists values “PROCESSOR_ARCHITECTURE” whose (it as string as lowercase = “ia64”) of keys “HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment” of registry

Relevance4:

exists key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight” whose (exists value “Version” whose (it as string as version = “3” OR it as string as version = “2”) of it) of registry

Relevance5:

exists key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight” whose (value “Version” of it as string < ") of registry

2

(imported comment written by BenKus)

Hello Satoshi,

If all of the Fixlet’s relevance returns “True”, then the Fixlet is supposed to become relevant in the BigFix Console. If it is not showing relevant, it may be related to some other issue. Here are two things to try:

  1. Send a refresh to the agent (right-click “Send Refresh”). This generally shouldn’t be necessary, but it is a good technique to make sure the agent is reporting the latest info.

  2. You might want to try to clear your console cache because it might be corrupted (File > Preferences > Clear Cache). Then restart your console.

Ben

3

(imported comment written by Satoshi_Kawamoto91)

Mr Ben,

Thank you for your reply.

I carried it out according to your advice, but the symptom was not improved.

And I found that an evaluation license of the test environment reached expiration.

I did not notice carelessly.Because there is few clients,

and the custom analysis relevance(incorporated Relevances of this Fixlet) was reported.

Thank you for support.

Satoshi