Fortinet white logo
Fortinet white logo

Release Notes

Configuring FortiClient EMS and FortiClient EMS Cloud on a per-VDOM basis

Configuring FortiClient EMS and FortiClient EMS Cloud on a per-VDOM basis

This information is also available in the FortiProxy 7.6 Administration Guide:

FortiClient EMS and FortiClient EMS Cloud can be added on a per-VDOM basis. Enabling override is necessary to add an EMS server for each VDOM.

config endpoint-control settings
    set override {enable | disable}
end

If override is enabled for a VDOM, the global configuration will not affect the VDOM. Override must be configured for each VDOM that connects to an EMS server.

This feature requires FortiClient EMS 7.2.1 and later.

With this override configuration, the FortiProxy can connect to multiple on-premise FortiClient EMS instances per VDOM. However, with this same configuration, only one FortiClient EMS Cloud instance can be connected per FortiProxy.

Each VDOM supports up to seven EMS servers, plus an additional seven in the global configuration. With override enabled on all ten VDOMs, a 10-VDOM contract would have up to 77 EMS servers. If override is enabled on only one VDOM, a 10-VDOM contract would have up to 14 EMS servers.

This functionality can be applied to MSSP (managed security service provider) configurations, and each VDOM has its own FortiClient EMS card for the EMS server or instance. For example:

  • Separate on-premise FortiClient EMS instances

  • Single FortiClient EMS multi-tenant instance based on FQDN type

  • Separate FortiClient EMS Cloud instances

To configure a FortiClient EMS server per VDOM in the GUI:
  1. Enable override in the FortiProxy CLI on the required VDOMs:

    config endpoint-control settings
        set override enable
    end
  2. Navigate to the desired VDOM, then go to Security Fabric > Fabric Connectors and double-click the FortiClient EMS card.

  3. Configure the EMS server settings as needed (see Configuring FortiClient EMS in the FortiProxy Administration Guide for detailed steps).

To configure a FortiClient EMS server per VDOM in the CLI:
  1. Enable override on the required VDOMs:

    config endpoint-control settings
        set override enable
    end
  2. Configure the EMS server on the desired VDOM:

    (root) config endpoint-control fctems-override
        edit 1
            set status enable
            set name "emstest24"
            set server "10.120.1.24"
            set serial-number "FCTEMS**********"
            set tenant-id "00000000000000000000000000000000"
            set capabilities fabric-auth silent-approval websocket websocket-malware push-ca-certs common-tags-api tenant-id client-avatars single-vdom-connector
    	 set verifying-ca "Fortinet_CA_Backup"
        next
    end

Configuring FortiClient EMS and FortiClient EMS Cloud on a per-VDOM basis

Configuring FortiClient EMS and FortiClient EMS Cloud on a per-VDOM basis

This information is also available in the FortiProxy 7.6 Administration Guide:

FortiClient EMS and FortiClient EMS Cloud can be added on a per-VDOM basis. Enabling override is necessary to add an EMS server for each VDOM.

config endpoint-control settings
    set override {enable | disable}
end

If override is enabled for a VDOM, the global configuration will not affect the VDOM. Override must be configured for each VDOM that connects to an EMS server.

This feature requires FortiClient EMS 7.2.1 and later.

With this override configuration, the FortiProxy can connect to multiple on-premise FortiClient EMS instances per VDOM. However, with this same configuration, only one FortiClient EMS Cloud instance can be connected per FortiProxy.

Each VDOM supports up to seven EMS servers, plus an additional seven in the global configuration. With override enabled on all ten VDOMs, a 10-VDOM contract would have up to 77 EMS servers. If override is enabled on only one VDOM, a 10-VDOM contract would have up to 14 EMS servers.

This functionality can be applied to MSSP (managed security service provider) configurations, and each VDOM has its own FortiClient EMS card for the EMS server or instance. For example:

  • Separate on-premise FortiClient EMS instances

  • Single FortiClient EMS multi-tenant instance based on FQDN type

  • Separate FortiClient EMS Cloud instances

To configure a FortiClient EMS server per VDOM in the GUI:
  1. Enable override in the FortiProxy CLI on the required VDOMs:

    config endpoint-control settings
        set override enable
    end
  2. Navigate to the desired VDOM, then go to Security Fabric > Fabric Connectors and double-click the FortiClient EMS card.

  3. Configure the EMS server settings as needed (see Configuring FortiClient EMS in the FortiProxy Administration Guide for detailed steps).

To configure a FortiClient EMS server per VDOM in the CLI:
  1. Enable override on the required VDOMs:

    config endpoint-control settings
        set override enable
    end
  2. Configure the EMS server on the desired VDOM:

    (root) config endpoint-control fctems-override
        edit 1
            set status enable
            set name "emstest24"
            set server "10.120.1.24"
            set serial-number "FCTEMS**********"
            set tenant-id "00000000000000000000000000000000"
            set capabilities fabric-auth silent-approval websocket websocket-malware push-ca-certs common-tags-api tenant-id client-avatars single-vdom-connector
    	 set verifying-ca "Fortinet_CA_Backup"
        next
    end