ePolicy Orchestrator software is designed to be extremely flexible. It can be set up in many different ways, to meet your unique needs.

The software follows the classic client-server model, in which a client system (system) calls into your server for instructions. To facilitate this call to the server, a McAfee Agent is deployed to each system in your network. Once an agent is deployed to a system, the system can be MANAGED by your McAfee ePO server. Secure communication between the server and managed system is the bond that connects all the components of your ePolicy Orchestrator software. The figure below shows an example of how your McAfee ePO server and components inter-relate in your secure network environment. 

1 Your McAfee ePO server connects to the McAfee update server to pull down the latest SECURITY content.

2 The ePolicy Orchestrator database stores all the data about the managed systems on your network,including:

• System properties
• Policy information
• Directory structure
• All other relevant data the server needs to KEEP your systems up-to-date.

3 McAfee Agents are deployed to your systems to facilitate:

• Policy enforcement
• Product deployments and updates
• Reporting on your managed systems

4 .Agent-server secure communication (ASSC) occurs at regular intervals between your systems and server. If remote Agent Handlers are installed in your network, agents communicate with the server through their assigned Agent Handlers.

5 .Users LOG onto the ePolicy Orchestrator console to perform security management tasks, such as running queries to report on security status or working with your managed software security policies.

6 .The McAfee update server hosts the latest security content, so your ePolicy Orchestrator can pull the content at scheduled intervals.

7 .Distributed repositories placed throughout your network host your security content locally, so agents can receive updates more quickly.

8.Remote Agent Handlers help to scale your network to HANDLE more agents with a single McAfee ePO server.

9 .Automatic Response notifications are sent to security administrators to notify them that an event has occurred.

ePolicy Orchestrator software is designed to be extremely flexible. It can be set up in many different ways, to meet your unique needs.

The software follows the classic client-server model, in which a client system (system) calls into your server for instructions. To facilitate this call to the server, a McAfee Agent is deployed to each system in your network. Once an agent is deployed to a system, the system can be managed by your McAfee ePO server. Secure communication between the server and managed system is the bond that connects all the components of your ePolicy Orchestrator software. The figure below shows an example of how your McAfee ePO server and components inter-relate in your secure network environment. 

1 Your McAfee ePO server connects to the McAfee update server to pull down the latest security content.

2 The ePolicy Orchestrator database stores all the data about the managed systems on your network,including:

3 McAfee Agents are deployed to your systems to facilitate:

4 .Agent-server secure communication (ASSC) occurs at regular intervals between your systems and server. If remote Agent Handlers are installed in your network, agents communicate with the server through their assigned Agent Handlers.

5 .Users log onto the ePolicy Orchestrator console to perform security management tasks, such as running queries to report on security status or working with your managed software security policies.

6 .The McAfee update server hosts the latest security content, so your ePolicy Orchestrator can pull the content at scheduled intervals.

7 .Distributed repositories placed throughout your network host your security content locally, so agents can receive updates more quickly.

8.Remote Agent Handlers help to scale your network to handle more agents with a single McAfee ePO server.

9 .Automatic Response notifications are sent to security administrators to notify them that an event has occurred.