--- title: "Best practice: Agent Handlers eliminate multiple ePO - On-prem servers" slug: "best-practice-agent-handlers-eliminate-multiple-epo-on-prem-servers" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:26Z published: 2026-09-07T17:46:26Z canonical: "docs.trellix.com/best-practice-agent-handlers-eliminate-multiple-epo-on-prem-servers" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Best practice: Agent Handlers eliminate multiple ePO - On-prem servers Use **Agent Handlers** in different geographic regions instead of multiple ePO - On-prem servers. > [!NOTE] > Note > > Multiple ePO - On-prem servers cause management, database duplication, and maintenance problems. Use **Agent Handlers** to: - Expand the existing ePO - On-prem infrastructure to handle more agents, more products, or a higher load due to more frequent agent-server communication. - Ensure that agents continue to connect and receive policy, task, and product updates even if the ePO - On-prem server is unavailable. - Expand ePO - On-prem management into disconnected network segments with high-bandwidth links to the ePO - On-prem database. Usually, it is more efficient and less expensive to add an **Agent Handler** rather than a ePO - On-prem server. > [!NOTE] > Note > > Use a separate ePO - On-prem server for *separate* IT infrastructures, *separate* administrative groups, or *test* environments.