The download size exceeds the maximum value set in the client setting

Usage and Config Platform
1

(imported topic written by koi9991)

The download size exceeds the maximum value set in the client setting _BESClient_Download_PreCacheStageDiskLimitMB, which can be modified through the Edit Computer Settings dialog.

What is the maximum of data that we can download to the client?

2

(imported comment written by BenKus)

Here is some info on this setting:

_BESClient_Download_PreCacheStageDiskLimitMB – default 250MB (Windows and Mac) 20 MB (Other).

Actions marked for pre-caching will report constrained if the total space used for downloads exceeds this limit.

Ben

3

(imported comment written by nagaraj.s)

Hi,

I have using patch management module in my envirnment,

i have 500 machine, if i deploy the patches in all clients the patches successfully executed.

but the clients “C:” drive in almost 20GB only, so can i thresold policy (like all the clients download limit only 10GB) after 10GB deployed the clients “C:” drive will not downloaded any file.so the 10GB size system performense needed.

it is possible or any fixlet relavanse there. please share the relavanse

Regards,

Nagaraj

4

(imported comment written by nagaraj.s)

Hi,

If any thresold policy for the download patches to the clients,

I tried the “_BESClient_Download_precachestagedisklimitMB == 100” in one machine, the change have been exicuted successfully.

after i deploy the 250MB size service pack in the same machine the patch will be download and installed the machine successfully,

but i want to that machine above 100MB patches deployed, the patches will not downloaded on the system.

If there is any policy please shere that.

Thanks

Nagaraj

5

(imported comment written by SteveHull)

You cannot prevent the download of patches beyond a certain size, but once the cache limit is exceeded, existing files will have to be removed in order to download new files. So if you’re limit is 100MB, you can download a 250MB file. But if you then need to download another file of any size, 100MB or just 1MB, the existing 250MB file will have to be deleted first. For files that are being pre-cached, they will not download until existing files in the pre-cache are used (by their actions running). For files stored in our normal download cache, they will be automatically removed to make room for the latest downloads.

6

(imported comment written by SystemAdmin)

koi99 - We have one client that, even though this setting is not set, reports back this error in the client log. Are you seeing the same issue?

7

(imported comment written by koi9991)

Where can I find this setting? " _BESClient_Download_PreCacheStageDiskLimitMB" I was in the edit mode, but I can’t see it.

8

(imported comment written by SystemAdmin)

It’s an optional setting, if you never set it before, you have to add it via the ADD button. Or you could write a task to set it too.

9

(imported comment written by koi9991)

Thanks for the fast responding.

Can we set it to the individual PC?

10

(imported comment written by SystemAdmin)

If you right click on just a single client and click edit, that will set a single client. You can select the same for multiple clients. Or the task option would let you target any combination.

11

(imported comment written by koi9991)

Thanks you, it works

12

(imported comment written by SystemAdmin)

Is there a way to have the client download as much as possible (until the local size limit is hit) and then pull the rest as the action executes? Seems strange that the entire action fails because the client doesn’t have enough space. Or perhaps a warning that the client will be contrained and that the precache needs to be expanded?

John

13

(imported comment written by SystemAdmin)

I’ll second jspanitz idea. It would be nice if the task, as it already knows the size of the download would verify it will not exceed the client precache size and offer a warning.