FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
This article describes that in some cases, EMS can unable to deploy or upgrade FortiClient on the endpoints and EMS can generate Deployment Error 150 for those endpoints.
This error is a generic error and usually happens when the connection between EMS and the problematic endpoint cannot be established properly.
Scope
Fortinet EMS Server. Important: Note that EMS 7.2.X versions are not supporting the initial deployment and only support the upgrade process.
Solution
This can be caused by several things which I will be stating below. If deployment error 150 are received on the EMS server for the endpoints, it would be useful to check the below :
EMS and the problematic endpoint can solve each other FQDN.
EMS and the problematic endpoint can ping each other with FQDN.
Task Scheduler and Remote Registry are running on the problematic endpoint and their StartUp type is Automatic.
Windows Firewall is turned off on the problematic endpoint.
There is no third-party security product has been installed on the problematic endpoint (A third-party security product can conflict with the processes of FortiClient).
There is no third-party security product has been installed on the EMS Server (A third-party security product can conflict with the processes of the EMS Server).
Check the TCP 135, 445, and 10443 ports between EMS Server and the problematic endpoint.
