McAfee EPOLICY ORCHESTRATOR 4.0.2 Product Manual page 132

Deploying Software and Updates
Deployment packages for products and updates
Each McAfee product that ePolicy Orchestrator can deploy provides a product deployment
package ZIP file. ePolicy Orchestrator can deploy these packages to any of your managed
systems, once they are checked in to the master repository. The ZIP file contains the product
installation files, which are compressed in a secure format.
ZIP files are used for both detection definition (DAT) and engine update packages.
You can configure product policy settings before or after deployment. McAfee recommends
configuring policy settings before deploying the product to network systems. This saves time
and ensures that your systems are protected as soon as possible.
These package types can be checked in to the master repository with pull tasks, or manually.
Supported package types
Package type
Detection definition (DAT) files
File type: ZIP
Scanning engine
File type: ZIP
SuperDAT (SDAT.EXE) files
File type: SDAT.EXE
Supplemental detection
definition (EXTRA.DAT) files
File type: EXTRA.DAT
Product deployment packages
File type: ZIP
Agent installation package
File type: ZIP
Agent language packages
File type: ZIP
132 McAfee ePolicy Orchestrator 4.0.2 Product Guide
Description
The regular, daily DAT files released by
McAfee.
The updated scanning engine for
McAfee anti-virus products, such as
VirusScan Enterprise. Engines are
usually updated once or twice a year.
The SuperDAT files contain both DAT
and engine files in one update package.
If bandwidth is a concern, McAfee
recommends updating DAT and engine
files separately.
The EXTRA.DAT files address one or a
few specific threats that have appeared
since the last DAT file was posted. If
the threat has a high severity, distribute
the EXTRA.DAT immediately, rather
than wait until that signature is added
to the next DAT file. EXTRA.DAT files
are from the McAfee website. You can
distribute them through ePolicy
Orchestrator. Pull tasks do not retrieve
EXTRA.DAT files.
A product deployment package contains
the installation software of a McAfee
product.
An agent installation package contains
the installation software for the agent.
An agent language package contains
files necessary to display agent
information in a local language.
Origination
McAfeeFtp and McAfeeHttp update sites,
and the McAfee website. Use a pull task
to download DAT files directly into the
master repository, or download and check
them into the master repository manually.
McAfeeFtp and McAfeeHttp update sites,
and the McAfee website. Use a pull task
to download engine files directly into the
master repository, or download and check
them into the master repository manually.
McAfee website. Download and check
SuperDAT files into the master repository
manually.
McAfee website. Download and check
supplemental virus definition files in to the
master repository manually.
Product CD or downloaded product ZIP
file. Check product deployment packages
in to the master repository manually. For
specific locations, see the documentation
for that product. Only the agent and
System Compliance Profiler deployment
packages are checked in to the master
repository as part of the ePO server
installation.
Master repository — checked in at
installation. For future versions of the
agent, you must check agent installation
packages in to the master repository
manually.
Master repository — checked in at
installation. For future versions of the
agent, you must check agent language