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

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

For information about what client tasks are available, and for details about their functionality, see the
product documentation for your managed products.
How the Client Task Catalog works
The Client Task Catalog allows you to create client task objects you can use to help manage systems
in your network.
Client Tasks Catalog applies the concept of logical objects to ePolicy Orchestrator client tasks. You can
create client task objects for a variety of purposes without the need to assign them immediately. As a
result, you can treat these objects as reusable components when assigning and scheduling client tasks.
Client tasks can be assigned at any level in the System Tree, and are inherited by groups and systems
lower in the tree. As with Policies and policy assignments, you can break the inheritance for an
assigned client task.
Client task objects can be shared across multiple registered ePolicy Orchestrator servers in your
environment. When client task objects are set to be shared, each registered server receives a copy
after your
Share Client Task
server task runs. Any changes made to the task are updated each time it
runs. When a client task object is shared, only the owner of the object can modify its settings.
Global Administrators on the target server that receives a shared task is
not an owner for that shared task. None of the users on the target
server is owner for any shared task objects the target receives.
Deployment tasks
Once you have checked in the product deployment package, use the Product Deployment client task to
install the product on managed systems. The task installs any product that is deployable through the
ePolicy Orchestrator software and has been checked in to the master repository.
Best practices
You can run the Product Deployment task for any group or individual system. When deciding how to
stage your product deployment, McAfee recommends considering the size of the package and the
available bandwidth between the master or distributed repositories and the managed systems. In
addition to potentially overwhelming the McAfee ePO server or your network, deploying products to
many systems can make troubleshooting problems more complicated.
Consider a phased rollout to install products to groups of systems at a time. If your network links are
fast, try deploying to several hundred clients at a time. If you have slower or less reliable network
connections, try smaller groups. As you deploy to each group, monitor the deployment, run reports to
confirm successful installations, and troubleshoot any problems with individual systems.
If you are deploying McAfee products or components that are installed on a subset of your managed
systems:
1 Use a tag to identify these systems.
2 Move the tagged systems to a group.
3 Configure a Product Deployment client task for the group.
Using the Product Deployment task to deploy products to managed systems
Use these tasks to deploy products to managed systems with the Product Deployment client task.
ePolicy Orchestrator allows you to create this task for a single system, or for groups of the System Tree.
16 Using tasks to manage products and systems
Client tasks and what they do
200 McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide