False Disk Space Reporting

(imported topic written by cstoneba)

My BigFix Console is showing the fixlet “WARNING: BES Client Computer is Low on Free Disk Space” is applicable on a server, but my managed property “Free Disk Space on System Drive” is showing that ther eis ~5GB free. I logged into the server and there is in fact 5gb free on c:, and c:\ is where the BigFix client is installed on. Any ideas why this fixlet is relevant?

Q: ((free space of it / 1000000) of drive of client folder of site “bessupport”) < 100

E: Singular expression refers to nonexistent object.

q: ((free space of drive of system folder)/(1024 * 1024)) as string & " MB"

A: 4842 MB

T: 0.269 ms

q: parent folder of regapp “BESClient.exe”

A: C:\Program Files (x86)\BigFix Enterprise\BES Client

T: 2.655 ms

(imported comment written by Lee Wei)

Yes, that would not make sense.

To get the first statement to run correctly.

Use the later versions of the Fixlet Debugger.

Go to Menu --> Debug --> Evaluate Using --> Local Client Evaluator

Then run the statement and it will be sent to the actual Client which understands the “site” keyword.

This way you can double check the results again.

Lee Wei

(imported comment written by cstoneba)

I changed the QnA as you suggested, and the relevance is coming back as False. However, the fixlet is still showing as applicable on this server in the console. I looked at a second console session and it is applicable for the server in that console too…

Q: ((free space of it / 1000000) of drive of client folder of site “bessupport”) < 100

A: False

T: 3438.082 ms

q: ((free space of drive of system folder)/(1024 * 1024)) as string & " MB"

A: 4637 MB

T: 3267.930 ms

q: parent folder of regapp “BESClient.exe”

A: C:\Program Files (x86)\BigFix Enterprise\BES Client

T: 32597.761 ms

(imported comment written by Lee Wei)

I think we have determined that the relevance is evaluating correctly, but the endpoint might have gotten the reporting mixed up.

So this is more of a general problem with server not reporting the actual state of the endpoint.

I would do a “Refresh” from the Console by right-click on the computer.

If the computer is not directly accessible by the server, then try running an Action with the ActionScript:

notify client ForceRefresh

Lee Wei

(imported comment written by cstoneba)

sending a refresh to the client seemed to fix the issue. That fixlet is no longer showing as applicable. Within the last 24 hours though, wouldn’t the client have run its own ‘refresh’ ?

(imported comment written by Lee Wei)

By default, the Client will check in with the Server for new instructions (we call this Gather) once in 24 hours.

However, it does not send up all the info, because that would generate unnecessary network traffic.

Send Refresh tells the Client to resend all the Properties, Fixlets and Actions.

Lee Wei

(imported comment written by cstoneba)

Gotcha. thanks Lee.