McAfee ePolicy Orchestrator, Руководство пользователя

Страница: 45 / 126

42
ePolicy Orchestrator
®
3.6 Walkthrough Guide Deploying the Agent and Products
About deploying and updating products
4
Using digital signatures guarantees that packages originated from McAfee or were
checked in by you, and that they have not been tampered with or corrupted. The agent
only trusts package catalog files signed by ePolicy Orchestrator or McAfee. This
protects your network from receiving packages from unsigned or untrusted sources.
Legacy product support
Older products use a flat directory structure in conjunction with the AutoUpdate and
AutoUpgrade client tasks to install product updates. New products that take advantage
of AutoUpdate 7.0 use a hierarchal directory structure and the update task to install
product updates.
If the update location you specify in the AutoUpdate or AutoUpgrade task settings is a
distributed repository managed by ePolicy Orchestrator, you must enable legacy
product support when you check the corresponding package into the master repository.
Doing so copies the packages into both directory structures, enabling you to support
legacy products.
Package ordering and dependencies
If one product update is dependent on another, you must check their packages into the
master repository in the required order. For example, if Patch 2 requires Patch 1, you
must check in Patch 1 before Patch 2. Packages cannot be reordered once they are
checked in. You must remove them and check them back in, in the proper order. If you
check in a package that supersedes an existing package, the existing package is
removed automatically.
About deploying and updating products
The ePolicy Orchestrator repository infrastructure allows you to deploy products and
update packages to your managed systems from a central location. Although the same
repositories are used, there are differences.
Product deployment and updating process
The high-level process for distributing DAT and engine update packages follows:
1 Check the update package into the master repository with a pull task or manually.
Table 4-4 Comparison of product deployment and update packages
Product deployment packages Update packages
Must be manually checked into the master
repository. DAT and engine update packages can be
copied from the source repository
automatically with a pull task.
Most other update packages must be
checked into the master repository manually.
Can be replicated to the distributed
repositories and installed on managed
systems with global updating. Can be replicated to the distributed
repositories and installed on managed
systems
automatically with global updating.
If not implementing global updating for
product deployment, a
deployment task must
be configured and scheduled for managed
systems to retrieve the package.
If not implementing global updating for
product updating, an
Update task must be
configured and scheduled for managed
systems to retrieve the package.