FortiClient EMS integrated with FortiGate
The diagram below shows the topology when using FortiClient EMS integrated with FortiGate.
In this scenario, FortiClient EMS provides FortiClient endpoint provisioning, while the FortiGate provides compliance rules to the endpoint. FortiClient endpoints connect FortiClient Telemetry to FortiClient EMS to receive configuration information from FortiClient EMS and receive compliance rules from the FortiGate. Profiles can also be imported from the FortiGate to FortiClient EMS, then pushed to the endpoints. Also see Using EMS integrated with FortiGate.
When viewing the endpoint in the FortiClient EMS GUI, the endpoint's connection is shown as FortiTelemetry to FGT<number> and Managed by EMS.
The below shows an example of the FortiClient Console when the endpoint is not compliant with FortiGate compliance rules and may be blocked from accessing the network.
You have some time to fix the non-compliant issues before FortiGate blocks network access. When an endpoint has a non-compliant (blocked) status, you can identify which compliance rules are causing the non-compliant status under Compliance Policy as seen above.
You can fix non-compliant settings by clicking Fix Non-compliant Settings. For details, see the FortiClient Administration Guide.
The image below shows the FortiOS GUI. In this situation, frank-PC and LHWin7A represent two endpoints connected to the FortiGate. frank-PC is also managed by FortiClient EMS. There is no flag to identify between the scenarios.