Technical Tip: How to collect FortiClient EMS on-premise logs by Diagnostic tool

[JHelio]

Description	This article describes how to collect FortiClient EMS on-premise logs by Diagnostic tool and which considerations need to be taken.
Scope	FortiClient EMS.
Solution	It is recommended to have debug enabled by the GUI console at Log Setting before any log recording and analysis: Access the Windows server directory where the FortiClient EMS is installed and locate the DiagnosticTool.exe. The tool is located by default at: C:\Program Files(x86)\Fortinet\FortiClientEMS\EMSDiagnosticTool.exe. It is recommended to execute with administrator rights. The diagnostic tool will gather information on EMS logs and Windows server information and events. It needs to be patient due to such a task can take several minutes, depending on server capabilities and the quantity of information that need to be gathered.  After the competition, a compressed file named 'forticlientems_7.X.X.XXXX_diagnostic_XXX.zip' is created once it is executed. If the Windows folder with the EMS log file is not open automatically, the output file is located at: C:\Users\Administrator\AppData\Local\Temp. Such files can be used to check logs and further troubleshoot at FortiClient EMS on-premise side. FortiClient EMS v7.4. In the latest FortiClient EMS v7.4, EMS services are now running on Linux. To collect Diagnostic Tool via CLI (for example, if Diagnostic Tool via GUI is not working,) below command can be used: /opt/forticlientems/bin/diagnostic_tool -o <file_name> A .zip file will be generated with the name defined in <file_name>, for example: This .zip file will be saved in the root/directory: Gathering the correct information and following the appropriate procedure helps to do better troubleshooting.