Specifications
6
McAfee update server — Hosts the latest security content so your ePolicy Orchestrator can pull
the content at scheduled intervals.
7
Distributed repositories — Installed throughout your network to host your security content
locally, so agents can receive updates more quickly
8
Remote Agent Handlers — Helps to scale your network to handle more agents with a single
ePolicy Orchestrator server
9
Ticketing system — Connects to your ePolicy Orchestrator server to help manage your issues and
tickets
10
Automatic responses — Provides notifications sent to security administrators when an event occurs
Hardware configuration
The physical hardware configuration you use for the McAfee ePO server and SQL Server is determined
primarily by the number of nodes, or node count, these servers manage.
Previous versions of McAfee ePolicy Orchestrator could easily manage up to 200,000 nodes using one
ePolicy Orchestrator server with a separate SQL Server. But the latest versions of McAfee ePolicy
Orchestrator have many more features and are much more robust changing the number of nodes it
can manage efficiently. Now McAfee ePolicy Orchestrator can manage up to 50,000 nodes with basic
server hardware and reasonable planning. Once you pass 50,000 nodes it becomes much more
important how you configure your McAfee ePO server hardware for the best possible performance.
Initially your managed node count determines your ePolicy Orchestrator server platform and the
recommended hardware specifications. The node count helps you answer these questions:
• Can I install the McAfee ePO server and SQL Server on the same physical hardware?
• Can I use a virtual machine for McAfee ePolicy Orchestrator or the SQL Servers?
• Can McAfee ePolicy Orchestrator use an existing SQL Server running other databases for McAfee
ePolicy Orchestrator?
• How do I partition my hard disk drives for the McAfee ePO server and SQL Server?
Configuration of McAfee ePO server and SQL Server on the
same physical server
You must determine the number of nodes you want the McAfee ePO server and SQL Server to manage
before you know if both servers can be installed on the same physical server.
Environments up to 5,000 or 10,000 nodes can have the McAfee ePO server and SQL Server installed
on one physical server to save hardware, IT, and energy costs. This works if you:
• Optimize your storage using multiple dedicated drives (see Hard disk configuration) for each
application as your node count increases
• Manage only the basic McAfee products, such as VirusScan Enterprise and Host Intrusion Prevention
If in the future if you plan to manage more McAfee products and to add
many more nodes, split the one server into two physical servers, one
dedicated to the McAfee ePO server and the other for the SQL Server.
ePolicy Orchestrator product architecture
Hardware configuration
2
McAfee
®
ePolicy Orchestrator
®
4.0 and 4.5 Best Practices Guide
13