Technical Tip: How to automate the reconnection of endpoints to the EMS (Endpoint Management Server) after a snapshot recovery

[Nishtha_Baria]

Description	This article provides guidance on automating the process of reconnecting endpoints to the EMS (Endpoint Management Server) following a snapshot recovery, covering both MacOS and Windows OS environments.
Scope	FortiClient EMS.
Solution	Automating the reconnection of endpoints to the EMS server after a snapshot recovery can help streamline the process and ensure that all devices are properly synchronized. Whether the choice to leverage EMS capabilities, PowerShell scripting for Windows OS, or Bash scripting for MacOS, it is essential to monitor the progress and verify that the endpoints have successfully reconnected to the EMS server. Always consider the security and compliance implications of any automation process and test the procedures in a controlled environment before implementing them in a production setting. Solution 1: Utilizing EMS Capabilities. Check EMS Server Configuration:  Ensure that the EMS server is properly configured to accept incoming connections and that any firewall rules or network policies are updated to allow the endpoints to reconnect. Check Endpoint Policies: Review the policies configured within the EMS server to confirm that they are correctly assigned to the affected endpoints. Initiate EMS Synchronization: Within the EMS server interface, trigger a synchronization process to force the endpoints to check-in. This process may vary depending on the EMS server software, so consult the EMS documentation for specific instructions. Solution 2: Using Scripting for Endpoints. For Windows OS: Create a PowerShell Script: On a Windows OS machine, create a PowerShell script that uses the EMS agent's command-line utility (if available) to initiate a connection back to the EMS server. Refer to the below document for commands in Windows: FortiESNAC CLI commands Deploy the Script: Deploy the PowerShell script to the affected Windows endpoints using a centralized management tool like Group Policy or a remote management solution. Execute the Script: Schedule the script to run at regular intervals (e.g., every hour) on the affected endpoints. For MacOS Endpoints: Create a Bash Script: On a MacOS machine, create a Bash script that uses a custom script or tool to initiate a connection back to the EMS server. For Mac, use the same process 'epctrl' as in Linux, the only difference is a path, epctrl on Mac is located in /Library/Application Support/Fortinet/FortiClient/bin/: https://docs.fortinet.com/document/forticlient/7.2.1/administration-guide/41299/forticlient-linux-cl... Deploy the Script: Deploy the Bash script to the affected MacOS endpoints using a centralized management tool, or utilize a tool like SSH for remote execution. Execute the Script:  Schedule the script to run at regular intervals on the affected MacOS endpoints.