
• Bandwidth
• Which machines have the latest content for protection
• The quality of your compliance reports
If a deployment task is being deployed to multiple point-products for the first time, you want to
gradually roll out the products to some targeted test machines. The schedule you configure depends
on the bandwidth available in your environment. For example, if you are upgrading from VirusScan
Enterprise 8.7 to 8.8, you can look at the VirusScan Enterprise 8.8 package that you checked into the
ePolicy Orchestrator repository and see it is 36 MB. That means each machine you target for
deployment is pulling 36 MB from its nearest repository. If your McAfee ePO server is managing 5,000
nodes and you only have one repository, those 5,000 nodes are pulling a total of 180 GB of data from
that one repository when the deployment task is executed. To keep that repository from being
overwhelmed, you must randomize your deployment.
Many customers forget to enable randomization on their tasks and choose a specific time for their task
to run such as noon on a daily basis. If you haven't configured randomization and you deploy a
product or signature update at noon on a daily basis, this generates a significant spike in traffic to
your repositories at that exact time. This could impact network performance.
Randomization is critical to any client task that uses bandwidth. Always calculate how much bandwidth
the deployment needs by taking the size of the deployment package, multiplied by the number of
nodes targeted, divided by the number of repositories used. For example, VirusScan 8.8, which is 36
MB, deployed to 1,000 nodes, pulled across 3 repositories, equals 36 GB of data. That 36 GB of data is
being pulled across three repositories which equals 12 GB per repository.
36 MB (VSE) * 1,000 (nodes) = 36 GB (total) / 3 (repositories) = 12 GB per repository
Using Client and Server tasks in your managed environment
Client tasks
8
McAfee
®
ePolicy Orchestrator
®
Best Practices Guide for use with ePolicy Orchestrator versions 4.5.0 and 4.0.0
61
Comentarios a estos manuales