Description | This article describes how to successfully Install and deploy applications using SCCM when FortiEDR is enabled. |
Scope | Applies to both On prem and cloud FortiEDR environments. |
Solution |
FortiEDR version 5.2 and above uses some extra monitoring. As per the Microsoft documentation we need to define Security exclusions for Configuration Manager:
SCCM doesn't check MD5s right after files are copied for deployment and therefore FortiEDR blocks the installation.
Follow the steps below to configure required exclusions:
*\Windows\CCMCache\* *\Windows\Logs\* *\Windows\CCM\*.sdf *\Windows\CCM\SystemTemp\* *\Windows\CCMSetup\* *\Windows\Setup\Scripts\* *\Windows\CCM\ScriptStore\* *\Windows\CCM\ServiceData\* *\Program Files\Microsoft Policy Platform\authorityDb\ *.sdf *\Windows\SMSTSPostUpgrade\* *\Windows\CCM\CcmExec.exe *\_smstasksequence\packages\*
If there are still any problems encountered, open a new technical support ticket for further assistance: Support Fortinet. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.