Creating a deployment configuration
|
EMS may not deploy certain FortiClient versions to the selected endpoints. EMS can download a signature, the EMS/FCT upgrade & compatibility matrix signature, from FortiGuard. This signature provides operating system support information for FortiClient versions. EMS uses this information and only pushes deployment to endpoints with an OS that supports the FortiClient version deployed. For example, consider that you have an endpoint running Windows 7, which FortiClient 7.4.4 does not support. If your EMS has the EMS/FCT upgrade & compatibility matrix and you create a deployment configuration to deploy FortiClient 7.4.4 to the endpoint, EMS does not deploy FortiClient 7.4.4 to that endpoint. |
To create a deployment configuration:
- Go to Deployment & Installers > Manage Deployment.
- Click Add.
- Configure the fields as desired:
Field
Description
Name Required. Enter the desired name. Endpoint Groups Optional. Select the desired endpoint group. The list includes device groups for all imported domains and workgroups.
If you are selecting a security group from a Microsoft Entra ID server, it must include a device object. If you are selecting a security group from an Active Directory server, it must include a computer object. If you select a security group that only has user objects as members, EMS does not assign the installer to the users.
Action Select Install or Uninstall.
When EMS pushes an uninstall to FortiClient (macOS), the uninstall does not remove FortiClient system extensions from the device. A user can run the uninstaller manually to remove system extensions as part of the uninstall.
Deployment Package Select the desired deployment package from the dropdown list. Start at a Scheduled Time If this feature is enabled, FortiClient displays a notification to users that there is a newer FortiClient version that they are expected to upgrade to. The time that you specify in this field displays to users as the default scheduled time for the installation to take place. The notification also allows users to configure a custom install time or to install the update immediately. If this feature is disabled, the FortiClient installation starts immediately without user interaction. Unattended Installation
When enabled, the end user cannot modify the installation schedule. If needed, the device reboots without warning logged-in users.
Reboot When Needed Reboot the endpoint to install FortiClient when needed.
This option is supported on FortiClient Windows 7.2.0-7.2.5 and 7.4.0 only.
Reboot When No Users Are Logged In Allow the endpoint to reboot without prompt if no endpoint user is logged into FortiClient. Notify Users and Let Them Decide When To Reboot When Users Are Logged In Notify the end user if a reboot of the endpoint is needed and allow the user to decide what time to reboot the endpoint. Disable to reboot the endpoint without notifying the user.
This option is supported on FortiClient Windows 7.2.0-7.2.5 and 7.4.0 only.
Priority The default priority for a new deployment configuration is the lowest priority. You cannot edit the priority while creating the deployment configuration. You can edit change the priority level after creating the deployment configuration. See Managing deployment configuration priority levels. Enable the Deployment Enable or disable. - Click Save.