FCP_FCT_AD-7-2 practice question 6 of 15

An administrator deploys a FortiClient installation through the Microsoft AD group policy After installation is complete all the custom configuration is missing. What could have caused this problem?

Full set: 55 questions
Answer options
A: The FortiClient exe file is included in the distribution package
B: The FortiClient MST file is missing from the distribution package
C: FortiClient does not have permission to access the distribution package.
D: The FortiClient package is not assigned to the group Correct answer
Correct Answer:
D. The FortiClient package is not assigned to the group
Explanation

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

Scroll to Top