Skip to main content

My Google-foo is failing me today. I'm outside of my wheelhouse trying to convert our distribution points from SMB to HTTP. I've got my clients connecting successfully, but every policy is failing with



Error: Package was not successfully downloaded. -1001


I can't find anything on error 1001. Does anyone have any insight?

For anyone that happens to come across this, I discovered that the hostname for my distribution points as hostname.local instead of hostname.ourdomain.com. Changing it from .local to ourdomain.com fixed the issue.

I'm now getting an error: -1003??



Any ideas

I'll throw in -1004 from JamfCloud



Error: Package was not successfully downloaded. -1004

I did this myself back in Fall 2018. After I defined the new distribution point (which in my case is AWS), I followed the process in Jamf Pro to copy all of the contents from my SMB distribution point to the cloud distribution point. If the packages are not loaded on the new distribution point, they won't download to clients.

I'm just curious - what are you using as your HTTP distribution point? Apache on *nix? IIS? A NAS?



I'm trying to get a NAS to do it, and it's not working. I think it's because the NAS is redirecting (302) Basic Auth HTTP(S) to a form-based login page.



Would love to hear how you got around that...

I'm getting an error "Package was not successfully downloaded. -1202" Does anyone know what might be the issue?

Error:

Executing Policy AppPortal_Firefox 72.0.2.pkg Jamf Cloud_12_Install
Downloading Firefox 72.0.2.pkg...
Downloading https://--------/jamf_share/Packages/Firefox%2072.0.2.pkg...
Error: Package was not successfully downloaded. -1202
The network connection was interrupted while downloading the package from https://-----------------/jamf_share/Packages/Firefox%2072.0.2.pkg. Attempting to reconnect...
Downloading Firefox 72.0.2.pkg...
Downloading https://-------------------/jamf_share/Packages/Firefox%2072.0.2.pkg...
Error: Package was not successfully downloaded. -1202
Error: Firefox 72.0.2.pkg is not available on the HTTP server.
Terms & ConditionsCookie settings