McAfee EPOCDE-AA-BA Product Guide - Page 81
Repository list file and its uses, Current branch, Evaluation branch, Previous branch
View all McAfee EPOCDE-AA-BA manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 81 highlights
Setting up repositories Repository types and what they do 8 Current branch The Current branch is the main repository branch for the latest packages and updates. Product deployment packages can be added only to the Current branch, unless support for the other branches has been enabled. Evaluation branch You might want to test new DAT and engine updates with a small number of network segments or systems before deploying them to your entire organization. Specify the Evaluation branch when checking in new DATs and engines to the master repository, then deploy them to a small number of test systems. After monitoring the test systems for several hours, you can add the new DATs to your Current branch and deploy them to your entire organization. Previous branch Use the Previous branch to save and store prior DAT and engine files before adding the new ones to the Current branch. In the event that you experience an issue with new DAT or engine files in your environment, you have a copy of a previous version that you can redeploy to your systems if necessary. ePolicy Orchestrator saves only the most immediate previous version of each file type. You can populate the Previous branch by selecting Move existing packages to Previous branch when you add new packages to your master repository. The option is available when you pull updates from a source site and, when you manually check in packages to the Current branch. Repository list file and its uses The repository list (SiteList.xml and SiteMgr.xml) file contains the names of all the repositories you are managing. The repository list includes the location and encrypted network credentials that managed systems use to select the repository and retrieve updates. The server sends the repository list to the agent during agent-server communication. If needed, you can export the repository list to external files (SiteList.xml or SiteMgr.xml). Use an exported SiteList.xml file to: • Import to an agent during installation. Use an exported SiteMgr.xml file to: • Backup and restore your distributed repositories and source sites if you need to reinstall the server. • Import the distributed repositories and source sites from a previous installation of the ePolicy Orchestrator software. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 81