I have seen multiple threads on this issue, but have not been able to resolve. Our JDS is what we were using before I believe. I don't have any HTTP active in File Distribution Setting. We use our JDS instance to push out our policies. Would this still be going thru http? the error i am getting for failed policies is Error: Could not connect to the HTTP server to download "xxx" package. This is occurring for all policies. I am still awaiting JAMF to contact me back for the webeX. we've had one already and made a new .DAVlogin file because i was getting an error saying My CapserShare could not mount. That process via command line fixed the mounting issue, but not the HTTP error. Any guidance is greatly appreciated. Methods Ive tried out via other threads:
Recreated symlink
trying to clean out /Library/Application Support/JAMF temp or incomplete packages
rebooting server
editing and creating new policies and specifying the JDS instance as the Distribution Point
No Luck.
I did look at older packages that were successfully deployed and it does say the same things as the failed ones, as far as where it is downloading the file from. https://school.jamf.org/CasperShare/package name.
So this literally was an overnight thing. Could it be possible we were using HTTP for file sharing and it got deleted? How can I check this?
