---
title: "Deploying Trellix Agent from ePO server"
slug: "deploying-trellix-agent-from-epo-server-1"
updated: 2026-10-26T07:33:44Z
published: 2026-10-26T07:33:44Z
canonical: "docs.trellix.com/deploying-trellix-agent-from-epo-server-1"
---

> ## 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.

# Deploying Trellix Agent from ePO server

Deploying from ePO - On-prem allows you to install Trellix Agent on multiple client systems at the same time.

- Systems must already be added to the **System Tree**.

### Tip

If you have not yet created the **System Tree** groups, you can deploy the Trellix Agent installation package to systems when you add groups and systems to the **System Tree**. But, if you are importing large domains or Active Directory containers, don't use this method. It generates significant network traffic.
- The user must have local administrator rights on all target systems. Domain administrator rights are required on a system to access the default `Admin$` shared folder. ePO - On-prem service requires access to this shared folder to install Trellix Agent.
- ePO - On-prem must be able to communicate with the target systems.

Before beginning a large Trellix Agent deployment, make sure that the client systems are reachable from ePO - On-prem. To test the connectivity between ePO - On-prem and Trellix Agent, ping the client systems with IP address or host name depending on how the client systems are identified in ePO - On-prem.

### Tip

The ability to successfully use ping commands from ePO - On-prem to managed systems is not required for Trellix Agent to communicate with the server. But it is a useful test to determine if you can deploy Trellix Agent to those client systems from ePO - On-prem.
- The `Admin$` share folder on Windows target systems must be accessible from ePO - On-prem. Verify that this is true on a sample of target systems. This test also validates your administrator credentials, because you cannot access remote `Admin$` shares without administrator rights.

From ePO - On-prem, click Windows Start → Run, then type the path to the target system's `Admin$` share, specifying system name or IP address. For example, type **`\\<System Name>\Admin$`**.

If the systems are properly connected over the network, and your credentials have sufficient rights, and the `Admin$` share folder is present, a Windows Explorer dialog box appears.
- Enable SSH on the Linux and Macintosh client systems before installing Trellix Agent from ePO - On-prem.

Comment out the following line in the `/etc/sudoers` file on a Red Hat operating system.

```
Default requiretty
```

Remove the comment from the following line `/etc/ssh/sshd_config file`

```
PermitRootLogin Yes
```

### Note

You must have root permissions to install Trellix Agent on non-Windows systems.
- Enable the network access on Windows 7 Home client systems.
- Enable the file and print sharing.
- Enable the server services.
- Enable the remote registry services.
- Temporarily disable the user account control on client systems to push Trellix Agent from ePO - On-prem.

The push deployment feature can install Trellix Agent on many systems at the same time. You can only install a single version of Trellix Agent on a client system.

: