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?

Question

Options

• AThe FortiClient exe file is included in the distribution package
• BThe FortiClient MST file is missing from the distribution package
• CFortiClient does not have permission to access the distribution package.
• DThe FortiClient package is not assigned to the group

• A
  3% (1)
• B
  9% (3)
• C
  12% (4)
• D
  76% (25)

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.

No community discussion yet for this question.