You can use a Telemetry server list to specify what IP addresses or FQDNs and ports endpoints can use to connect FortiClient Telemetry to FortiClient EMS, or EMS and FortiOS. You can create one or more Telemetry server lists and configure them as part of endpoint policies to assign them to domains or workgroups.
If FortiClient is installed using a deployment package configured with an EMS IP address or FortiClient Cloud invitation code, FortiClient automatically connects to that EMS or FortiClient Cloud after installation. If this is not the case, FortiClient uses the assigned Telemetry server list to try and connect FortiClient Telemetry to EMS or EMS and FortiOS.
Even if the endpoint is already connected to an EMS or an EMS and FortiOS, you can still assign a Telemetry server list to endpoints as part of an endpoint policy. You can also update existing Telemetry server lists as required. EMS pushes the updates to endpoints with the next Telemetry communication.
FortiClient 6.4.0 and later versions cannot directly connect Telemetry to FortiOS. FortiClient 6.4.0 only connects Telemetry to EMS, which then sends FortiClient data to FortiOS. Only endpoints with FortiClient versions older than 6.4.0 installed can connect Telemetry directly to FortiOS.