Problem with location of Software to be pushed by BigFix

Usage and Config Platform
1

(imported topic written by deschodt91)

As you know you can either upload software via a wizard or place it directly in the same folder and build a task that point to that location… We are running out of space on our BF server, and until it’s redone, we created a second share with exactly the same privileges as the primary, and put more software there… our parent company has several such shares, so we know it works…

So instead of BF going to download from :

download http://LALFIxxxx.MARRIOTT.COM:52311/Uploads/xxxxxx for instance, it now goes to download http://LALFIxxx.MARRIOTT.COM:52311/Uploads1/xxxx, uploads 1 has 100% identical permissions

The odd thing is that this works for about 30% of packages, the smaller ones it seems… For the rest, the pushes end up in deploy limbo with “pending download”, Attempt 4 of 200, or something similar…

It’s not a sha1 issue with size being different on another drive, I’ve blanked that out for now…

Any idea why it works on some and not others ?

2

(imported comment written by jessewk)

if it works for some files and not others, it’s probably a problem with the share. SMB shares are notoriously unreliable. This would fit the symptoms where small files tend to work but not the larger ones. Is there any chance you can host the files on an HTTP server instead?