Skip to main content
RiverChen
Staff
Staff
January 23, 2026

Technical Tip: FortiEndpoint collector remains in Default Collector Group due to EMS system profile setting

  • January 23, 2026
  • 0 replies
  • 541 views
Description This article describes an easily overlooked configuration that can cause FortiEDR collectors to remain in the Default Collector Group.
Scope FortiEndpoint.
Solution

In FortiEndpoint environments, the FortiEDR collector is deployed and managed through FortiClient EMS. The FortiClient EMS deployments should sync with FortiEDR collector groups.
The collector group synchronization relies on communication between FortiClient and FortiEDR installed on the device. If the endpoint profile assigned to a device has 'Endpoint Detection & Response' disabled, FortiClient and FortiEDR cannot communicate with each other. As a result, the Collector group is not updated, and the endpoint remains in the Default Collector Group in the FortiEDR console, even though the device may appear correctly in FortiClient EMS.

 

This setting can be found under:
Endpoint Profiles -> System Settings ->  Assigned Profile -> Enable Endpoint Detection & Response.

 

Step 1: Verify the profile assigned to the device.
From the EMS Endpoints tab, identify which system profile is assigned to the affected device (highlighted with a red box in the screenshot below).


article1.png

 

Step 2: Verify the system profile setting.
Navigate to Endpoint Profiles -> System Settings, and check whether Enable Endpoint Detection & Response is enabled for the assigned profile (highlighted with a red box in the screenshot below).
If the setting is disabled, enable it and allow time for the Collector to resynchronize and update its group assignment.

image (1).png

 

Further troubleshooting:
If the setting is already enabled and the Collector still does not move out of the Default Collector Group, further troubleshooting is required. In some cases, toggling EMS deployments (enable/disable) or creating a new deployment can help. If the issue persists, review FortiEDR logs and collect EMS diagnostic logs for further analysis. 

 

* EMS logs: set the EMS-Server log level to debug (System Settings -> Log) and run the EMS diagnostic tool.

 

EMS kb.png

 

EMS kb 02.png

 

  • FortiClient Logs (set the client log level to debug in EMS-Server profile, reproduce the issue and provide Diagnostic Tool output .cab file).

 

FCT kb 02.png

 

FCT kb.png

 

  • FortiEDR logs: 

 

Win:"C:\Program Files\Fortinet\FortiEDR\FortiEDRCollectorService.exe" --support

MacOs:sudo /Applications/FortiEDR.app/Contents/MacOS/FortiEDRCollector.app/Contents/MacOS/FortiEDRCollector --support

Linux:sudo /opt/FortiEDRCollector/bin/FortiEDRCollector --support

 

Related Article: 

What to provide when opening a FortiEndpoint ticket with TAC 

    Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
    Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.