The configuration required for enabling F-Secure clients to use the beta update channel depends on the F-Secure clients installed in the environment. With F-Secure products supporting central management using Policy Manager Server and Console like F-Secure Client Security and F-Secure Server Security, you can install a dedicated Policy Manager Server and the installation is then configured to download beta updates using the instructions provided below.
As Gateway end-protection clients like Internet Gatekeeper for Linux or F-Secure Anti-Virus Linux Gateway do not support centrally managed installations, these clients require separate steps which are described below.
Hosts in the update should not be business critical, but they should be in active use.
A typical environment for testing the updates is as follows:
The systems can be installed in parallel to production, as a clone of production or specifically configured for daily use by a specific group of more technically experienced users or your internal IT department.
Setting up the environment requires manual reconfiguration of the F-Secure Policy Manager Server or the client. Instructions can be found below.
The systems in beta should not exhibit abnormal or unexpected behavior compared to production systems. Similar system health checks should be available as in the normal production environments.
A typical environment for testing the updates is as follows:
Should you witness an increased number of crashes, false detections, reduced performance or other unexpected anomalies, please report them to F-Secure along with your feedback. Always remember to include F-Secure Support Tool (FSDIAG) report from the affected computer.
Instructions for creating an FSDIAG are available:
All feedback should be sent by email to. Your feedback is highly appreciated as it helps us to improve our products and releases prior to production release.
These are step-by-step instructions on how to configure F-Secure Policy Manager to download updates from beta update server. You need administrator rights on the server to perform this.
The last step in configuring the environment is to ensure that the hosts under the F-Secure Policy Manager will not fetch updates directly from F-Secure. To accomplish this, you need to change the current policy.
After doing this, your F-Secure Policy Manager will start downloading the beta updates.
As these products only support standalone installation, one solution is to configure the hosts to download F-Secure beta updates directly from the F-Secure Beta Update channel server. Use the instructions below to apply this particular change.