Technical Tip: How to collect FortiClient EMS on-premise logs by diagnostic tool
| 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 |
The tool is located by default at:
It is recommended to execute with administrator rights.
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 the on-premise side. 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), the following 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:
Note, starting with FortiClient EMS v7.4.1, a dedicated CLI utility called emscli has been introduced. This CLI utility streamlines and simplifies the diagnostic collection process (including collecting EMS diagnostics and backup via CLI and transferring them to a remote server, all in one command line).
Refer to the following article for more information and use cases of emscli: Technical Tip: How to use emscli CLI tool to manage FortiClient EMS v7.4.1+ from Linux shell.
In addition, since FortiClient EMS now supports VM appliance deployments, where emscli is a default shell, a set of commands for non-VM and VM deployments slightly differ. Refer to the official emscli references for both deployment types below:
Gathering the correct information and following the appropriate procedure helps with better troubleshooting. |






