(imported topic written by HVS5_Kenneth_Hockin)
I am running into an issue where I have a large installation that is being used as an offering. So rather than having a user have to accept the offering, then have to wait for the package to copy locally, I turned on the option in the fixlet for “Start client downloads before constraints are satisfied”.
The download starts, it puts all the files in the named folder, the offer is then visible, so I accept the offer. The fixlet then errors out saying “download failed”, and then deletes all the files.
If I turn off the “Start client downloads before constraints are satisfied” checkbox, the fixlet runs through fine.
(imported comment written by jgstew)
I’m not certain I understand where the “named folder” is coming from.
Could any of the SHA1’s for the prefetch commands be incorrect?
(imported comment written by HVS5_Kenneth_Hockin)
The named folder is created by TEM, it seems when it downloads the files, it then moves them to the named folder, then it checks the SHA1 and size values.
I don’t believe the SHA1 values can be incorrect as when I turn off this option the fixlet works perfectly fine.
(imported comment written by jgstew)
That is a good point about the SHA1s, that does suggest they are correct.
What is the _BESClient_Download_NormalStageDiskLimitMB on the client? I would suggest increasing this to 20GB so that the files do not get deleted on failure.
I’m not really certain what is happening. Is there anything helpful in the client logs? Once the offer is available, you could verify the SHA1 and Size of the files to make sure they are correct.
http://bigfix.me/analysis/details/2994646
https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/Tivoli%20Endpoint%20Manager/page/Configuration%20Settings
(imported comment written by Tim.Rice)
In the past I’ve handled this situation with two Fixlet’s. The first Fixlet downloads the files, verifies them, then moves them into a holding folder. The second Fixlet detects the files in the holding folder, verifies their signatures again just in case. This way you avoid having the BESClient cleanup routines deleting your files.
just remember to delete the files when you are done with them.