I wish to complain.
When a Windows workstation's existing F-Secure Client Security protection is upgraded to a newer version via the policy-based method, the last step of the preparation wizard makes it possible to define an end-user warning message and a delay of several minutes for the reboot event which concludes the upgrade. It is also possible to set a "forced reboot" flag to restart even with open programs and documents.
Yet, all these settings are a mere Potemkin village, because F-Secure logic decides internally if a reboot is really needed on the endpoint! (The setup wizard window says "...if a reboot is not needed the user will not receive any notification")
How dare F-Secure software igrore the system administrator's personal command and decide that it is NOT necessary to reboot at the end of the version upgrade process? This is completely unacceptable for any self-conscious company, who take pride (and material responsibility) in properly auditing their IT security processes! The mere chance of protection software ending up in the hung state for hours or days makes it impossible to audit continued antivirus coverage beyond reasonable doubt! Positive proof positively requires reboot.
Why does the policy-based F-Secure Client Security version upgrade wizard fail to include an "Absolutely restart after installation" checkbox?
Thanks for your attention, Yours Sincerely: Tamas Feher, Hungary.
I agree, we do not have the "absolutely restart after installation" option available, but can you elaborate as to what the use case is here related to the security audit. I mean, if there is use case for having such feature, we surely should put in the product backlogs.
And apologies for not answering the query earlier.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link: