Disk limited error on BF 9.2.6.94

Usage and Config
1

All, howdy and thanks in advance for the assistance. I’m fairly new to big fix, and I’ve noticed that with machines that are using a new KACE image (as in one that was stood up 2 weeks ago) ALL the machines that have that image are showing ‘disk locked’. Any ideas? I understand it’s a cache issue, but I need to know, a, how to fix it, and b, what caused it.

Again, TIA.

Tim

2

Bump, anyone? I’ve noticed that a few of the disk errors have cleared (especially after the job expired) but many still remain.

Thanks,

Tim

3

What do you mean by a “disk locked” ? where is this showing this in BigFix?

4

Thanks, Alan. It’s actually ‘disk limited’, I misnamed it originally. It’s in the results pane for actions we have run; screenshot below.

In BigFix, it’s in the actions > summary pane > reported computers tab > under last reported status.

From what I’ve been able deduce, this is only occurring on newly imaged machines with KACE. None of the other machines were affected by this.

Thanks again,

Tim

5

The Problem is the size of the Bigfix Buffers… By default its set to 256mb… Because many fixlets or actions often exceed that, you have to right click each group of machines affected and either edit or enter the
_BESClient_Download_PreCacheStageDiskLimitMB and increase that to however many GB you want ( I have used 5120 for large windows updates and also the same for

_BESClient_Download_NormalStageDiskLimitMB