Product guide

Recommended ASCINetwork Size
150 minutesWireless LAN
NOTE: For complete information on balancing bandwidth, server hardware, and ASCI
determination, see the ePolicy Orchestrator 4.0 Hardware Sizing and Bandwidth Usage Guide .
Agent-initiated after agent startup
After the installation, and after the agent service is stopped and restarted, the agent calls into
the server at a randomized interval within ten minutes. Subsequent communications occur 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 with the /P command-line option.
Wake-up calls
Wake-up calls prompt the agents to call in to the server. Wake-up calls can be sent manually
or scheduled as a client task. These are useful when you have made policy changes or checked
in updates that you want to apply to the managed systems sooner than the next ASCI.
Wake-up calls can also configured on query results which are scheduled in the Server Task
Builder wizard.
SuperAgents and broadcast wake-up calls
If you plan to use agent wake-up calls to initiate agent-server communication, consider converting
an agent on each network broadcast segment into a SuperAgent. SuperAgents distribute the
bandwidth impact of the agent wake-up call, minimizing network traffic.
Instead of sending agent wake-up calls from the server to every agent, the server sends the
SuperAgent wake-up call to SuperAgents in the selected System Tree segment. When
SuperAgents receive this wake-up call they send broadcast wake-up calls to all the agents in
their network broadcast segments. This reduces network traffic. This is beneficial in large
Distributing Agents to Manage Systems
Agent-server communication
McAfee ePolicy Orchestrator 4.0 Product Guide66