McAfee EPOLICY ORCHESTRATOR 4.5 Product Manual page 48

Configuring ePolicy Orchestrator
Security keys and how they work
Task
For option definitions, click ? in the interface.
1 Click Menu | Configuration | Server Settings, select Security Keys from the Setting
Categories list, then click Edit. The Edit Security Keys page appears.
2 Next to the Agent-server secure communication keys list, click New Key. In the
dialog box, type the name of the security key.
3 If you want existing agents to use the new key, select the key in the list, then click Make
Master.
Agents 3.6 and later begin using the new key at the first agent-server communication after
their next update task is complete. For earlier versions of the agent, you must run a client
product update task to push down the new key, using the agent updater 3.5.5 that is in
the master repository.
CAUTION:
performed only when you have specific reason to do so. McAfee recommends performing
this procedure in phases so you can more closely monitor progress.
4 After all agents have stopped using the old key, delete it.
In the list of keys, the number of agents currently using that key is displayed to the right
of every key.
5 Back up all keys.
Designating an ASSC key pair as the master
Use this task to change which key pair, listed in the Agent-server secure communication
keys list, is specified as the master. Do this after importing or generating a new key pair.
Task
For option definitions, click ? in the interface.
1 Click Menu | Configuration | Server Settings, select Security Keys from the Setting
Categories list, then click Edit. The Edit Security Keys page appears.
2 From the Agent-server secure communication keys list, select a key , then click Make
Master.
3 Create an update task for the agents to run immediately, so that agents update after the
next agent-server communication.
NOTE: Ensure that the agent key updater package is checked in to the master repository
and has been replicated to all distributed repositories that are managed by ePolicy
Orchestrator. Agents begin using the new key pair after the next update task for the agent
is complete. At any time, you can see which agents are using any of the agent-server
secure communication key pairs in the list.
4 Back up all keys.
Using the same ASSC key pair for all servers and agents
Follow this process to ensure that all ePO servers and agents use the same agent-server secure
communication (ASSC) key pair.
48 McAfee ePolicy Orchestrator 4.5 Product Guide
In large installations, generating and using new master key pairs should be