McAfee EPOCDE-AA-BA - ePolicy Orchestrator - PC, Руководство по эксплуатации продукта

Страница: 80 / 328

FTP repositories
You can use an FTP server to host a distributed repository. Use FTP server software, such as Microsoft
Internet Information Services (IIS), to create a new folder and site location for the distributed
repository. See your web server documentation for details.
HTTP repositories
You can use an HTTP server to host a distributed repository. Use HTTP server software, such as
Microsoft IIS, to create a new folder and site location for the distributed repository. See your web
server documentation for details.
UNC share repositories
You can create a UNC shared folder to host a distributed repository on an existing server. Be sure to
enable sharing across the network for the folder, so that the McAfee ePO server can copy files to it and
agents can access it for updates.
Unmanaged repositories
If you are unable to use managed distributed repositories, ePolicy Orchestrator administrators can
create and maintain distributed repositories that are not managed by ePolicy Orchestrator.
If a distributed repository is not managed, a local administrator must keep it up-to-date manually.
Once the distributed repository is created, use ePolicy Orchestrator to configure managed systems of a
specific System Tree group to update from it.
Refer to Enabling the agent on unmanaged McAfee products so that they
work with ePolicy Orchestrator for configuration of unmanaged systems.
McAfee recommends that you manage all distributed repositories
through ePolicy Orchestrator. This and using global updating, or
scheduled replication tasks frequently, ensures your managed
environment is up-to-date. Use unmanaged distributed repositories only
if your network or organizational policy do not allow managed distributed
repositories.
Repository branches and their purposes
The ePolicy Orchestratorsoftware provides three repository branches, allowing you to maintain three
versions of all packages in your master and distributed repositories.
The repository branches are Current, Previous, and Evaluation. By default, ePolicy Orchestrator uses
only the Current branch. You can specify branches when adding packages to your master repository.
You can also specify branches when running or scheduling update and deployment tasks, to distribute
different versions to different parts of your network.
Update tasks can retrieve updates from any branch of the repository, but you must select a branch
other than the Current branch when checking in packages to the master repository. If a non-Current
branch is not configured, the option to select a branch other than Current does not appear.
To use the Evaluation and Previous branches for packages other than updates, you must configure this
in the Repository Packages server settings. Agent versions 3.6 and earlier can retrieve update
packages only from the Evaluation and Previous branches.
8 Setting up repositories
Repository types and what they do
80 McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide