--- title: "On-premises Endpoint server" slug: "on-premises-endpoint-server" tags: ["Integration", "Helix", "Sec Ops and Analytics"] updated: 2026-09-15T14:11:17Z published: 2026-09-15T14:11:17Z canonical: "docs.trellix.com/on-premises-endpoint-server" --- > ## 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. # On-premises Endpoint server > [!WARNING] > Important > > There are two versions of IAM. If the URL you use to access the IAM UI ends with `fireeye.com`, this document pertains to you. If the URL you use to access the IAM UI ends with `trellix.com`, see the [Trellix IAM Guide](/network-and-platform/docs/trellix-iam-guide) for information regarding IAM. | Task | Information | Done | | --- | --- | --- | | Verify that the customer ID on the Endpoint Security (HX) appliance matches the ID in the IAM Web UI. | 1. Run the `show version` command in the Endpoint Security (HX) CLI and locate the `Customer ID` field. 2. Log into your Trellix Cloud Account and click **My Settings** > **My Organization**. Locate the **Oracle Customer ID** field on the Organization Settings page. | | | *Standalone servers*: Prevent the Endpoint Security (HX) server from automatically discovering and connecting to a Trellix Helix-enabled cloud Central Management System appliance (if any). | Run the `no cmc client enable` command in the Endpoint Security (HX) CLI. See [Preventing connections to a cloud Central Management appliance](/network-and-platform/docs/preventing-connections-to-a-cloud-central-management-system-appliance). | | | Enable Trellix Helix mode on the Endpoint Security (HX) server. | Run the `helix mode on-premises` command to enable Trellix Helix and allow Single Sign-On (SSO). Run the `helix mode on-premises with-sso` command to enable Trellix Helix and enforce SSO. See [Enabling Helix mode](/network-and-platform/docs/enabling-trellix-helix-mode). | | | *Central Management System**-connected servers*: Ensure that alerts and health statistics are sent directly to Trellix Helix and not through the Trellix Helix-enabled Central Management System appliance. | Run the `show datastreaming helix` command on each connected server and verify that the `Helix data-streaming enabled` field is `yes`. Run the `show helix health-stats status` command on each connected server and verify that the `Enabled` field is `yes`. Run the `no fenet dti helix service override` command on each connected server. See [Sending alerts and health stats directly from appliances](/network-and-platform/docs/sending-alerts-and-health-stats-directly-from-appliances-1). | | | Configure the HelixConnect Client on each server. | The HelixConnect Client is enabled automatically when Trellix Helix mode is enabled, but additional steps may be required. See [Establishing HelixConnect connectivity](/network-and-platform/docs/establishing-helixconnect-connectivity-1). | | | *If your servers use an HTTP proxy for outbound communication*: Enable the servers to communicate with Trellix Helix through the proxy. | Run the `helix proxy preference fenet-proxy` command on the servers. See [Enabling HTTP proxy communication](/network-and-platform/docs/enabling-http-proxy-communication-1). | | | Verify that the Endpoint Security (HX) controller can reach Trellix Helix. | Enable access to `<customer Helix ID>.receiver.apps.fireeye.com` over port TCP 443. | |