Technical Tip: Process behind the update notifications pushed by the FortiSASE cloud towards the FortiClient

[srajapratap]

Description	This article explains how FortiSASE pushes upgrade notifications to the FortiClients in various scenarios.
Scope	FortiSASE, FortiClient.
Solution	FortiSASE Cloud has its own set of 'FortiClient' software as compared to what is present on the Fortinet Support site. This differentiation is not based on the capabilities of the software but on the criteria of what set of features are activated on the FortiClient and most importantly, the installer ID. When the FortiSASE cloud pushes the firmware update notification, i.e., 7.0.10, to the FortiClient, it will compare the installer ID of the FortiClient 7.0.10, it possesses, and the installer ID of the FortiClient already installed on the endpoint device. After the verification, if the installer ID found is different than the one it possesses, then it will trigger a pop-up on the client that an upgrade needs to be done, as shown below. This is possible in the below cases: Scheduled maintenance upgrade initiated by the FortiSASE cloud. Network Admin installed the same FortiClient, 7.0.10, from the Fortinet Support portal, which has a different installer ID, as compared to the installer ID of FortiClient on the FortiSASE cloud. Despite being on the same FortiClient version, the verification process on the FortiSASE cloud will know that the upgrade popup should be triggered on the endpoints If the installer ID is the same after comparison, then the popup will not be triggered. Below is the documentation mentioning the installer IDs on the FortiClient: Deploying different installer IDs to endpoints using the same deployment package