Superagents And Broadcast Wakeup Calls - McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual

®
ePolicy Orchestrator 3.6 Walkthrough Guide

SuperAgents and broadcast wakeup calls

For complete information on balancing bandwidth, server hardware, and ASCI, see
the ePolicy Orchestrator 3.6 Hardware Sizing and Bandwidth Usage white paper.
Note
Agent-server communication after agent startup
After the installation, or if the agent service is stopped and restarted, the agent calls
into the server at a randomized interval within ten minutes. The second and
subsequent ASCI after startup occurs with the ASCI set in the agent policy (60 minutes
by default).
You can force the agent to communicate to the server immediately after the installation
by running the .
CMDAGENT EXE
Wakeup calls
When you send a wakeup call from the server to agents in your environment, the
agents are prompted to call into the server. Wakeup calls can be sent manually or
scheduled as a task and are useful when you have made policy changes or checked in
updates to the master repository that you want to be applied to the managed systems
sooner than when the ASCI may occur.
If you plan to use agent wakeup calls in your network to initiate agent-server
communication, consider converting an agent on each network broadcast segment into
a SuperAgent. SuperAgents distribute the agent wakeup call's bandwidth impact,
minimizing network traffic. Depending on your network environment, you may find
SuperAgent wakeup calls to be a more resource-efficient method of prompting agents
to call in, than relying on the server to send wakeup calls to all agents.
with the command-line option.
/P
32
Deploying the Agent and Products
ePolicy Orchestrator agent
4