I am tasked with administering patches using BigFix in an AirGapped environment, so in the last week or two I have been giving myself a crash course in the BESAirGapTool. I have a few questions regarding this tool to clear up my understanding of it and put together a good patching strategy.
Question 1: Should the internet facing “Site Gathering” computer remain a singular computer each time the patching process is performed? I ask this because I am noticing the “Airgap.db” and “AirgapCache.db” files that reside in the airgaptool’s directory. Do these DB files track the Content/download file history of the SiteGathering computer?
Say airgap tool moved to a different computer next patching cycle because maybe it was performed by a different operator, it’s then going to download the whole SiteContent history instead of just what’s new from the last time the AG tool was run before, correct? I believe this is the case in my environment. In order to get things up to date would it be recommended to do an initial airgap request from the BigFix server ?
Question 2: When you select the option “A” for your sites to gather site content and download fixlet update files, you then move the airgapresponse file to the server and ingest it to update site content. How do you get the downloaded update files moved over to the server as well?
Question 3: Is there a reason that you would need to separate the “Site Gathering” computer that gathers site content and the “Patch Download” computer into two different machines?
Any other general advice tips and tricks would be appreciated to get me up to speed on this process.
Thanks in Advance!