Beta programs for business users

Beta Update Channel Instructions

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 described also below.

How to configure F-Secure Policy Manager to download updates from beta update server

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.

Windows:

1. Start Windows Regedit (regedit.exe)
2. Open this path: HKEY_LOCAL_MACHINE\Software\Data Fellows\F-Secure\FSAUA
3. Right-click and select "New" -> "String Value" to add a new string value with the beta update server address:
   Name = RootServer
   Type = REG_SZ
   Data = http://fsbwserver-beta.f-secure.com
4. After doing this, you need to restart F-Secure Automatic Update Agent service (Start / Administrative Tools / Services).

Linux:

1. Open the file /etc/opt/f-secure/fsaua/fsaua_config using a text editor
2. Locate the "Update servers" section
3. Under the "TEMPLATE_UPDATE_SERVERS" section, find the following line:
   
   #update_servers=http://fsbwserver.f-secure.com
    
4. Change the above line to this (Remove the hash "#" sign from the start and add "-beta" to the server address):
   
   update_servers=http://fsbwserver-beta.f-secure.com
   
   
5. After doing this, you need to restart F-Secure Automatic Update Agent daemon by running /etc/init.d/fsaua restart.

Both Windows and Linux:

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.

1. Open F-Secure Policy Manager Console.
2. Select "Advanced Mode" from the View menu.
3. Open F-Secure Automatic Update Agent/Settings/Communications.
4. Select "Allow fetching updates from F-Secure update server" and change that to "No".
5. Distribute policies.

After doing this, your F-Secure Policy Manager will start downloading the beta updates.

How to configure F-Secure Internet Gatekeeper and F-Secure Anti-Virus Linux Gateway to download updates from the F-Secure Beta update server

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. 

Internet Gatekeeper for Linux:

1. Open the file /opt/f-secure/fsigk/conf/dbupdate.conf with a text editor
2. Locate the following line
   
   UPDATEURL=
   
   Change the line to this:
   
   UPDATEURL=http://fsbwserver-beta.f-secure.com
    
3. Save the file
4. Restart the F-Secure Automatic Update Agent daemon by typing this to the command prompt:
   
   cd /opt/f-secure/fsigk ; ./rc.fsigk_fsaua restart

 F-Secure Anti-Virus Linux Gateway:

1. Open the file /opt/f-secure/fsigk/conf/dbupdate.conf with a text editor
2. Locate the following line
   
   UPDATEURL=
   
   Change the line to this:
   
   UPDATEURL=http://fsbwserver-beta.f-secure.com
   
    
3. Save the file
4. Restart the F-Secure Automatic Update Agent daemon by typing this to the command prompt:
   
   cd /home/virusgw ; ./rc.virusgw_fsaua restart