I had a similar scenario where I had to make a source site available for one of our "secure" VLAN zone without internet access. We had an ePO server (A) in this zone and one in the internal network (B).
On server B we installed an FTP server and mirrored the master repository selectively (i.e. just DAT, engine, no agent etc.) within this server (i.e. ePO had the master and a local repository at the same time). From server A we pulled the content over via a ePO pull task (defined server B as source).
Alternatively you could use robocopy to mirror the content of a source (acquired via normal download of Mcafee update site or one VSE client mirror task) in your unsecure zone (run robocopy either in your secure zone or unsecure, whichever is allowed and technically possible). In either way your ePO or another server in the secure main zone should have a FTP server the home folder of which is populated via this robocopy mirroring.
Hope I was clear enough 🙂
When you use robocopy, you should define the sitelist as local repositories, not distributed, otherwise checking sitestat.xml by the agent will blow the whole thing.
Good idea, however i won't be able to transfer files from the non secure to the secure network as the only way to transfer files is to burn to CD for me. Which i think is what they do at the HQ.
However, how could i create Local repositories? I can't seem to figure that one out. Is it like creating a source site?
Just for an FYI this is the type of file i'm provided: http://download.nai.com/products/DatFiles/4.x/NAI/avvepo7049dat.zip however i don't download it from the web, someone else does and provides it via http download or ftp.
You create a local (or unmanaged) repository by adding one to the agent's list in the agent's ePO policy page Repository section. There is also a checkbox next to the list to enable (or disable - the logic has changed through versions) newly added repositories by default so be sure to tick (or untick) that afterwards.
(ePO 4.6 PG p. 91)