EMS only
The FortiClient and EMS versions do not affect the on-net, off-net, or online status. On-net/off-net status are affected by the DHCP onnet/offnet and On-Net Subnets settings in EMS. See the FortiClient EMS Administration Guide for details on these settings.
The following table shows how various configurations determine the endpoint status when FortiClient Telemetry is connected to EMS:
|
EMS DHCP on-net / off-net setting |
On-net subnet |
Option 224 serial number |
Endpoint status |
|---|---|---|---|
|
Off |
No |
N/A |
On-net |
|
On |
No |
Option not configured |
Off-net |
|
On |
No |
Option configured |
On-net |
|
Off or on |
Yes and match |
Configured or not |
On-net |
|
Off or on |
Yes and do not match |
Configured or not |
Off-net |
\
The following examples show how endpoint status is determined when FortiClient is connected to EMS only:
- The endpoint has an offline and off-net status when the endpoint cannot connect FortiClient Telemetry to EMS and is outside one of the on-net networks.
- The endpoint has an offline on-net status when the endpoint cannot connect FortiClient Telemetry to EMS but is inside one of the on-net networks.
|
On-net subnets have higher priority over other settings. In addition, EMS does not compare the Option 224 serial number. As long as the endpoint has the serial number, EMS assumes the endpoint is behind a FortiGate and is on-net. |