3 Replies Latest reply on May 27, 2010 11:14 PM by msl

    Updating ePO DATs - Minimum File Requirements

      Hi

       

      I have a new ePO installation to manage clients using only VS8.7i, on a network where an internet connection is not allowed. I have created a UNC share and have created a source site to point to it.

       

      I see from other posts that the files needed for DAT updates should be obtained from the contents of ftp://ftp.nai.com/CommonUpdater and put into the share. There are nearly 50 files in the ftp directory and some of those may not actually be needed for VS8.7 alone. In order to transfer the minimum of files over on a daily basis, can anybody advise which files in the ftp directory are needed specifically for a DAT update to VS8.7 via ePO.

       

      Many thanks.

        • 1. Re: Updating ePO DATs - Minimum File Requirements

          I would say all. First you have the incremental DAT update files which your endpoints will use if they are 'nearly up-to-date' and then there's the full package which older endpoints will use. Why can't you just replicate the entire folder, surely that must be simpler than picking individual files?

           

          Matt

          1 of 1 people found this helpful
          • 2. Re: Updating ePO DATs - Minimum File Requirements
            jstanley

            All of the files will be required; however, their is a way to reduce the amount of data here is how:

            1. Install an ePO server on an external network.
            2. Setup a UNC distributed repository on said ePO server. On the Package Types tab of the distributed repository only select the packages you want the site to contain (DAT, ENGINE, etc).
            3. Define a repository pull task to pull the updates from one of the McAfee public update sites (FTP or HTTP) and chain a repository replication task off it.
            4. Export the master repository public key on this ePO server (menu | configuration | server settings | security keys | edit) and import it on your internal network's ePO server.
            5. Copy the contents of the UNC distributed repository managed by your external ePO server to a UNC repository accessible by your internal ePO server.

             

            You can now control exactly what updates are provided to your internal EPO server by editing the Package Types you replicate to the UNC repository managed by your external ePO server.

             

            I hope that helps!

            1 of 1 people found this helpful
            • 3. Re: Updating ePO DATs - Minimum File Requirements

              Matt & Jeremy

               

              Many thanks for both your responses. The concensus is clearly that all the files need to be made available, so I just have to decide on the best way to get them across.