Well, curl refers error 33 (not sure if that's what's being returned here) as a server that doesn't support byte ranges. I think this has something to do with resumable downloads. You may want to have a look in the /Library/Application Support/JAMF/Downloads folder and see if there's a partial download there that you can clear out.

Thanks Jared

I managed to, finally, get around to getting access to the clients machine and to no surprise sitting there was the incomplete download for the policy. Deleted and it's now working!

We're seeing similar errors with HTTP downloads, and if we look at that Downloads folder we find partial downloads. Clearing them out solves the problem.

Is there a jamf verb to delete these out? We though that jamf flushCaches might do the trick, but it seems not.

Posted Today at 3:11 PM by andyparkernz

We're seeing similar errors with HTTP downloads, and if we look at that Downloads folder we find partial downloads. Clearing them out solves the problem.

Is there a jamf verb to delete these out? We though that jamf flushCaches might do the trick, but it seems not.

Hi Andy

I've found that just running the following from terminal or write it into a shell script file and bundle it into a casper policy works wonders.

This will delete everything in the JAMF Downloads folder, but leave the folder intact.

#!/bin/sh

rm -rf /Library/Application Support/JAMF/Downloads/*.*

exit 0

Edit; updated script command.

Thanks Sean for the script.
We were also getting the 33 error and found there were temp files in JAMF folder.

One small typo about the script as it didn't work when I ran it.

rm -rf /Library/Application Support/JAMF/Downloads/.*
(changed on the end, should be *.)