Deploy FortiClient using EMS

Deploy FortiClient using EMS

You can use FortiClient EMS to deploy FortiClient (Windows) in managed mode to devices in your network that are running a supported Windows operating system. For installation information, see the FortiClient

Upgrade FortiClient

EMS Administration Guide.

An upgrade schedule dialog box is displayed in advance when deploying FortiClient from EMS to endpoints running Windows operating system. If no FortiClient is installed on the endpoint, no reboot is required for the installation, and no upgrade schedule dialog box is displayed. The user can postpone the reboot for a maximum of 24 hours. Before the mandatory reboot occurs, a FortiClient dialog box is displayed with a 15 minute warning.

Upgrade FortiClient

For information about supported upgrade paths for FortiClient, see the FortiClient Release Notes.

 

This entry was posted in FortiClient and tagged , , on by .

About Mike

Michael Pruett, CISSP has a wide range of cyber-security and network engineering expertise. The plethora of vendors that resell hardware but have zero engineering knowledge resulting in the wrong hardware or configuration being deployed is a major pet peeve of Michael's. This site was started in an effort to spread information while providing the option of quality consulting services at a much lower price than Fortinet Professional Services. Owns PacketLlama.Com (Fortinet Hardware Sales) and Office Of The CISO, LLC (Cybersecurity consulting firm).

3 thoughts on “Deploy FortiClient using EMS

  1. kk27653

    Hi,
    Using EMS 1.0.3.0107 and FortiClient 5.4.2.0860 and configured Excluded Folders like this: T:\
    This is shared network drive and I see that it’s being scanned by random clients.
    Can root folder be excluded like this or I have to specify each folder under T:\

    Reply
  2. kk27653

    Yes. I have just found under Advanced setting of profile setting “Scan network files” which I toggled to Off setting.
    It seems that excluded folder setting is being used only for local drives and does not apply to network mapped drives. Normally there is no explanation of this behavour anywhere so this is my conclusion.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.