@liorme remember that the BigFix agent running on the local endpoint uses root or Local System accounts. These accounts typically do not have any permissions nor privilege to access a network share on a foreign computer unless the network share allows anonymous access (generally a bad idea from a security point of view). You “can” leverage action script to map the network drive using an account and some credentials, but then you need to fuss with passing the credentials securely and you need to consider concurrent load that this might bring to your network share if your BigFix agents all decide to copy a file off of the network share all at the same time.
Relays and URL downloads avoid all of that mess.
The best approach is to upload your msi file to a URL accessible path and use the regular prefetch commands in your action script.
One of the neat things about the BigFix server is that it comes with a web server built in @ wwwrootbes. If you copy your MSI to
C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\Uploads\MyTest\zoom.msi
then you could use action script to download from that URL.
prefetch FakeZoom.msi sha1:b6553a307dc1752a5089159dfad18d567d00e538 size:15 https://127.0.0.1:52311/Uploads/MyTest/FakeZoom.msi sha256:3da21c6c90133d6c7960caec3ecc82f52539019cb04ce56a6aabe70c4dd7f222
If your file changes frequently and you want to deal with the sha1/sha256/size validations outside of the Fixlet/Action you can check out the dynamic downloads feature here: