Technical Tip: Steps to consider on initial deployment FortiEndpoint

Description

This article describes what to consider in the Initial Deployment of FortiEndpoint.

Scope

FortiEndpoint.

Solution

It is possible to use the BPS license for help with orientation and configuration on the Initial Deployment of FortiEndpoint.

Initiate a BPS Onboarding Request

Introduction BPS

Important Notes: If coming from an old deployment of FortiClient EMS or FortiClient.

1. Migrate from the old FortiClient deployment to FortiEndpoint.

• Configure on EMS/FortiEndpoint all policies, security groups, tags/'FGT-Fabric' connector, rules, and AD to match the configuration of the old server.

• When EMS/FortiEndpoint is ready with all required configurations. Use the switch option to send users to the new EMS/Fortiendpoint Server. 

• Validate all services are working as expected.

• Prepare the Packet installation with the FCT version and EDR version (FortiEndpoint packet).

• Activate the deployment packet.
  
  

2. Migrate from the old FortiEDR deployment to FortiEndpoint.

• Uninstall the old EDR solution.

• Install the new Fortiendpoint packet with FortiClient/EDR features.
  
  

3. Any other security tool installed? If yes, it will require parallel exceptions between security tools. 

Important Note: No proper exclusions may cause: BSOD, Memory crashes, Performance Issues, or Driver conflicts. To validate all processes that require exclusion, EDR can use Task Manager or CMD.

Open CMD as admin:

tasklist /v | findstr /i kaspersky
tasklist /v | findstr /i defender
tasklist /v | findstr /i crowdstrike
tasklist /v | findstr /i csfalcon
tasklist /v | findstr /i sentinel
tasklist /v | findstr /i sophos