If you have Software distribution as part of the Lifecycle Module, then when you use the “Manage Software Distribution Dashboard” and delete the files or packages from there, I have watched the files and their sha1 named folders be deleted from from the C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\Uploads folder in real time.
If you delete the fixlet directly from the console, then if the fixlet was created with the dashboard, the files remain until the besadmin tool cleanup is run…
HOWEVER if you use the Windows or Mac distribution wizard to create and upload files , then if you delete the fixlet or task, the upload becomes orphaned and remains in the upload folder till you manually delete it.
This , in the hands of un-informed admins, leads to the disk filling up of totally useless files.
There is session relevance you can run in the presentation debugger and in conjunction with an analysis, “Bigfix Server - Uploads Directory - Windows” you can get a list of the Sha1 folders that dont appear to have a fixlet available for them. This works well for single file uploads but multiple files in folder upload , it shows the contents of those folder uploads as ophaned with the exception of one file. Its easy to accidentally delete the files to a current fixlet or task if this scenario is not carefully watched.