Created on 08-30-2023 08:31 PM Edited on 08-31-2023 07:09 AM By Stephen_G
Description | This article describes how to connect a FortiClient endpoint to EMS without user interaction, and how to change the EMS Server if necessary. |
Scope | Windows FortiClient 7.0+, 7.2+. |
Solution |
Sometimes, it is necessary to automatically connect FortiClient endpoints to EMS or migrate endpoints that are already connected to an EMS server to another one. The fastest way to execute this procedure is to create a script to automatically run at the endpoints. The process is simple, just create a script and then, it is possible to use Windows GPO to execute on all the endpoints in the domain. In this article, two script samples will be studied:
Script for registering FortiClient Telemetry to an EMS Server.
cd \
Example:
The FortiClient telemetry is disconnected from EMS:
Script to migrate a FortiClient registered to an EMS Server to another EMS Server.
At this stage, a script will be used to migrate a FortiClient connected to an EMS Server to another EMS Server. This is very useful when a new server needs to be recreated from scratch.
cd \
In this example, FortiClient telemetry currently registered to 10.6.2.6 will be migrated to 10.6.2.3:
The FortiClient telemetry is currently connected to 10.6.2.6:
This script can be used with Windows GPO. This way it is possible to automatically connect or migrate FortiClient endpoints with EMS with less effort and without user interaction.
Note: Nothing happens when the script asking the FortiClient to connect to an EMS Server is used if the FortiClient is already connected.
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.