Repositories Repositories house your security software packages and their updates for distribution to your managed systems. Security software is only as effective as the latest installed updates. For example, if your DAT files are out of date, even the best anti-virus software cannot detect new threats. It is critical that you develop a strong updating strategy to keep your security software as current as possible. The McAfee ePO repository architecture offers flexibility to ensure that deploying and updating software is as easy and automated as your environment allows. Once your repository infrastructure is in place, create update tasks that determine how, where, and when your software is updated. What repositories do The agents on your managed systems obtain their security content from repositories on the McAfee ePO server. This content keeps your environment up to date. Repository types and what they doTo deliver products and updates throughout your network, McAfee ePO software offers several types of repositories that create a strong infrastructure for updating. Repository branches and their purposesYou can use the three McAfee ePO repository branches to maintain up to three versions of the packages in your master and distributed repositories. Using repositoriesDistributed repositories work as file shares that store and distribute security content for your managed endpoints. Setting up repositories for the first timeFollow these high-level steps when creating repositories for the first time. Manage source and fallback sites best practiceYou can change the default source and fallback sites from the Server Settings. For example, you can edit settings, delete existing source and fallback sites, or switch between them. Verify access to the source site best practiceYou must make sure that the McAfee ePO Master Repository and managed systems can access the Internet when using the McAfeeHttp and McAfeeFtp sites as source and fallback sites. Configure settings for global updates best practice Global updates automate repository replication in your network. You can use the Global Updating server setting to configure the content that is distributed to repositories during a global update. Configure agent policies to use a distributed repository best practiceCustomize how agents select distributed repositories to minimize bandwidth use. Use SuperAgents as distributed repositoriesCreate and configure distributed repositories on systems that host SuperAgents. SuperAgents can minimize network traffic. Create and configure repositories on FTP or HTTP servers and UNC sharesYou can host distributed repositories on existing FTP or HTTP servers, or UNC shares. Although a dedicated server is not required, the system must be robust enough to handle the load when your managed systems connect for updates. Using UNC shares as distributed repositoriesFollow these guidelines when using UNC shares as distributed repositories. Use local distributed repositories that are not managedCopy contents from the Master Repository into an unmanaged distributed repository. Work with the repository list filesYou can export the repository list files. Change credentials on multiple distributed repositoriesChange credentials on multiple distributed repositories of the same type. Doing so is valuable in environments where there are many distributed repositories. Pulling tasksUse pull tasks to update your Master Repository with DAT and Engine update packages from the source site. Replication tasksUse replication tasks to copy the contents of the Master Repository to distributed repositories. Repository selectionNew distributed repositories are added to the repository list file containing all available distributed repositories. The agent of a managed system updates this file each time it communicates with the McAfee ePO server. The agent performs repository selection each time the agent (McAfee Framework Service) service starts, and when the repository list changes.