If you are using BigFix 7.2 or earlier, please see AirGap 7.2
On a computer that has internet access using the standard installation instructions, be sure to follow the airgap instructions in Step 8.
Go to the BigFix Server install directory (C:\Program Files\BigFix Enterprise\BES Server\BESAirgapTool.exe), and run the tool from there.
In order to make Fixlet content and product license updates available on the isolated network, the tool will need to be transferred in from a computer with internet connectivity using the following steps:
To keep the main BigFix Server up-to-date when new Fixlet content is released, repeat these steps periodically to update the Fixlet content on the main BigFix Server. You can join the new Fixlet mailing list to receive notifications on when Fixlets are updated.
Deploying Fixlets on the main BES Server will likely require downloaded patches and other files from the Internet. Included in the BES Air Gap Package is the BES Download Cacher utility. This utility will help you in downloading and transferring files to the main BES Server. The utility can help to download every patch in a Fixlet site or single file downloads from a url. You can download the current utility here.
Transfering all files from Fixlet sites
BES_Download_Cacher.exe -m <MyMasthead.efxm> -x downloads
If you need to download a single file (instead of all the files of a Fixlet site), use the instructions below:
Transfering a single file
BES_Download_Cacher.exe -u <url> -x downloads
You may need to increase the size of the cache on the main BES Server so that it does not try to empty any files from the cache. Use the BES Download Cacher to increase the size of the cache with the command:
BES_Download_Cacher.exe -c <Cache Size(Bytes)>
The default size is 1024 MB.
After the files are cached in the BES Server sha1 folder, they will be automatically delivered to the BES Relays/BES Clients when you click on an action in the Fixlet message that references a downloaded file. If the file is not cached, the BES Console will give you a status of "Waiting for Mirror Server" indefinitely after you deploy an action. More information about how the BES cache works is available here.