McAfee EPOCDE-AA-BA - ePolicy Orchestrator - PC, Product Manual

Page: 206 / 328

• Click
Menu
|
Reporting
|
Queries
, select
VSE: DAT Deployment
in the Queries list, then click
Actions | Run
.
See the VirusScan Enterprise documentation for more information on
this query.
Evaluating new DATs and engines before distribution
Use this task to test update packages using the Evaluation branch. You might want to test DAT and
engine files on a few systems before deploying them to your entire organization.
The ePolicy Orchestrator software provides three repository branches for this purpose.
For option definitions, click
?
in the interface.
Task
1
Create a scheduled Repository Pull task that copies update packages in the Evaluation branch of
your master repository. Schedule it to run after McAfee releases updated DAT files.
For additional information, see Deploying update packages with pull and replication tasks.
2
Create or select a group in the System Tree to serve as an evaluation group, and create a McAfee
Agent policy for the systems to use only the Evaluation branch (in the
Repository Branch Update Selection
section of the
Updates
tab).
The policies take affect the next time the agent calls in to the server. The next time the agent
updates, it retrieves them from the Evaluation branch. For additional information, see Configuring
the Deployment task for groups of managed systems.
3
Create a scheduled Update client task for the evaluation systems that updates DAT and engine files
from the Evaluation branch of your repository. Schedule it to run one or two hours after your
Repository Pull task is scheduled to begin.
The evaluation update task created at the evaluation group level causes it to run only for that
group. For additional information, see Updating managed systems regularly with a scheduled
update task.
4
Monitor the systems in your evaluation group until satisfied.
5
Move the packages from the Evaluation branch to the Current branch of your master repository.
Click
Menu
|
Software
|
Master Repository
to open the Master Repository page.
Adding them to the Current branch makes them available to your production environment. The
next time any Update client tasks run that retrieves packages from the Current branch, the new
DAT and engine files are distributed to systems that use the task. For additional information, see
Checking in packages manually.
16 Using tasks to manage products and systems
Evaluating new DATs and engines before distribution
206 McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide