Based on the CLI output from FortiGate:

The configuration shows the use of "type fortiems," indicating that FortiGate is set up to interact with FortiClient EMS.

The "server" field points to an IP address (10.0.1.200), which is typically the address of the FortiClient EMS server.

The configuration includes an SSL-enabled connection, which is a common setup for secure communication between FortiGate and FortiClient EMS.

Thus, the configuration indicates that FortiGate is set up to pull user groups from FortiClient EMS.

References

FortiGate Security 7.2 Study Guide, FSSO Configuration Section

Fortinet Documentation on FortiGate and FortiClient EMS Integration

When FortiClient is installed on a Windows Server, the default behavior for real-time protection control is:

Real-time protection is disabled:By default, FortiClient does not enable real-time protection on server installations to avoid potential performance impacts and because servers typically have different security requirements compared to client endpoints.

Thus, real-time protection is disabled by default on Windows Server installations.

References

FortiClient EMS 7.2 Study Guide, Real-time Protection Section

Fortinet Documentation on FortiClient Default Settings for Server Installations

FortiClient communicates directly with FortiClient EMS to continuously share device status information through ZTNA telemetry.