HTTP over SMB

HTTP has the ability to resume downloads, if interrupted. I think this is the primary advantage of HTTP over SMB/AFP.

are you aware of any major drawbacks?

Not to my knowledge. If anything, HTTP downloads are more flexible for deploying packages, especially over wireless connections. Search for HTTP on JAMFNation and you'll find a lot of discussions on the ups and downs with implementation. Personally, I found making the switch from AFP to HTTP rather straightforward.

Good Luck!

"Personally, I found making the switch from AFP to HTTP rather straightforward."

Would that be as straightforward as enabling WebDav in OS X 10.10.3 Server?

Thanks!

Corbin

https://jamfnation.jamfsoftware.com/article.html?id=116

Make sure to read the comments, especially the one by @donmontalvo at the bottom.

I've installed and configured many JSSes for clients.

I try to use http whenever possible. The big pro, as mentioned, is resumable downloads. The con is that http downloads are slower than AFP or SMB ones.

If your JSS is public-facing you most definitely want to use http, not exposing AFP or SMB shares to the Internet. Some ISP's by default block the mounting of SMB shares over the Internet...

Are there any additional networks that have to be open to use HTTP?

I've heard rumblings about issues with Imaging. Has anyone else experienced this or have any insight? Does it work but maybe more slowly? I've not tested yet.