Skip to main content
droehrig
New Member
Jul 22, 2019 12:28 PM UTC
Question

Forticlient EMS Endpoint Notified

After an auto deployment I have many endpoints that only say under Installer- Endpoint Notified but they never updated to the latest version. How do I fix this? It happens every time there is an update to the Forticlient and we do an auto deployment of the update. 

 

Thanks,

Donna

    6 replies

    Mario_M
    Visitor III
    Sep 13, 2022 7:26 AM UTC

    Hi Donna,

     

    any news about this topic?

     

    TIA
    Mario

    Translate
    IT_Satcom
    Visitor III
    Feb 24, 2023 9:14 AM UTC

    Would like to hear about as well, the same problem here.

    Translate
    hirozawa
    New Member
    Nov 11, 2024 11:57 AM UTC

    ※I am using translation software, so the sentences may be difficult to understand.

     

    The cause of the problem may be an invalid certificate.

    I changed "Invalid Certificate Action" to "Allow" in "System Setting Profile" of "Endpoint Profile". Then, when I configured the "Deployment" again, a notification was displayed to the user.

    Translate
    mgoswami
    Staff
    Staff
    Nov 28, 2024 9:17 AM UTC

    Hello,

     

    What network ports are allowed between endpoints and EMS ? Please check the Firewall and ensure that following ports are open "TCP 135, 445, and 10443 ports between EMS Server".

     

    Regards,

    Manosh

    Translate
    hirozawa
    New Member
    Jul 3, 2025 12:54 PM UTC

    I didn't know how this feature actually worked.
    Here are the results of my investigation:

     

    1. EMS notifies FortiClient of the "System Settings >> EMS Settings >> EMS Settings" field, specifically the "FortiClient Download URL."
    2. FortiClient accesses the notified URL to download the package.
    3. The client installs the downloaded package.


    I mistakenly thought the package was downloaded through telemetry (port 8013)!
    The reality is that the download URL (port 10443) is notified, and the package is retrieved from there.

    Even if a user doesn't utilize the download URL,
    users who use the "Manage Deployment" feature should ensure that TCP/10443 is accessible for communication!

     

    Furthermore, if the download URL displays a certificate warning,
    it is recommended to set the "Invalid Certificate Action" to "Allow" in the system profile.

    Translate
    New Member
    Oct 1, 2026 5:43 AM UTC

    If endpoints remain stuck at “Endpoint Notified,” first verify that the affected clients can communicate with FortiClient EMS and that the required EMS/FortiGuard connectivity is not being blocked. Check the deployment logs on a few affected endpoints for installer, permission, or connectivity errors. It can also help to restart the FortiClient service and trigger a fresh deployment or policy synchronization from EMS. If the issue consistently occurs after every upgrade, review the auto-deployment package and version compatibility, then test the app update on a small endpoint group before deploying it broadly.

    Translate
    Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024