An administrator deploys a FortiClient installation through the Microsoft AD group policy After installation is complete all the custom configuration…

When deploying FortiClient via Microsoft AD Group Policy, it is essential to ensure that the

deployment package is correctly assigned to the target group. The absence of custom configuration

after installation can be due to several reasons, but the most likely cause is:

Deployment Package Assignment: The FortiClient package must be assigned to the appropriate group

in Group Policy Management. If this step is missed, the installation may proceed, but the custom

configurations will not be applied.

Thus, the administrator must ensure that the FortiClient package is correctly assigned to the group to

include all custom configurations.

Reference

FortiClient EMS 7.2 Study Guide, Deployment and Installation Section

Fortinet Documentation on FortiClient Deployment using Microsoft AD Group Policy