I updated our FortiClient EMS from 7.07 to 7.2 yesterday. I then began to deploy the 7.2 client to a subset of our devices to test the upgraded client before rolling it out to everyone. We are new to EMS and FortiClient so this was our first go around with updating existing clients.
The test clients all upgraded successfully, however, the client machines all rebooted without ANY warning or indication that an upgrade or installation was taking place, even if there was a user logged in. I do not want to roll it out this way as employees may be in the middle of working on a document or attending a meeting when their machine randomly reboots.
Here are my deployment settings in EMS, what am I doing wrong?
Ideally, if they are logged in, I would like the client to be notified that an upgrade is available and to let them install/reboot it when they are ready. If they are not logged in, then go ahead and install/reboot automatically.
Thanks.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Same old story, FortiClient is THE worst software to upgrade..
Did this ever get resolved?
Created on 03-06-2024 11:46 AM Edited on 03-06-2024 11:46 AM
Yes. It upgraded properly in 7.2.3 on Windows 11 for me when I last tested it. The upgrade process is much better than it used to be in earlier versions. I'm going to be testing 7.2.4 which just came out.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1733 | |
1106 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.