Business Suite

Sort by:
Issue: I am trying to activate Client Security 14.xx with the License key we used for 13.xx but it is not recognized. Resolution: Please check that you are using a valid license key. License keys differ between versions. Contact your reseller to obtain your updated license keys and certificates Article no: 000012137
View full article
Issue: The F-Secure Client Security products started sending security alerts to F-Secure Policy Manager for every single blocked URL. This started when F-Secure Online Safety 2019-09-02_02 update was released. The security alerts have following details: Unknown alert: online_safety.page.block. Resolution: The fix was released in the F-Secure Online Safety 2019-09-10_01 update package. The update is installed automatically and does not require user or administrator actions.   Article no: 000015569
View full article
Issue: After installing F-Secure Linux Security 64 the following error messages related to the missing dependencies is returned. Do you accept this license agreement? The license agreement text is available at /opt/f-secure/linuxsecurity/doc/LICENSE /var/opt/f-secure/linuxsecurity/download/linuxsecurity-1200-linux-x86_64/1562587205/content/setup: package 'fuse-libs.x86_64' is not installed 2019-07-19 13:11:56 src/fsbootstrap.c:417[7] executing '/var/opt/f-secure/linuxsecurity/download/linuxsecurity-1200-linux-x86_64/1562587205/content/setup' failed, result 256 2019-07-19 13:11:56 src/fsbootstrap.c:209[7] install failed Failed to activate the product! Resolution: You need to install the necessary dependencies. Uninstall the current F-Secure Linux Security 64 rpm -e f-secure-linuxsecurity Install the missing dependencies (example fuse-libs and libcurl) yum install -y  fuse-libs libcurl  Re-install F-Secure Linux Security 64 by using the following commands. bash f-secure-linuxsecurity/f-secure-linuxsecurity-installer 2>&1 | tee ls64_install_2.log Article no: 000014074
View full article
Issue: Launching Policy Console Manager (PMC) using the below command does nothing: sg fspmc -c /opt/f-secure/fspmc/fspmc The Console does not launch and no error message was displayed.   Resolution: To be able to launch Policy Manager Console (PMC), the account used in Linux needs to be listed in the local Linux group fspmc, created by the PMC installation. Instructions on how to add account/user to the fspmc user group can be found in the link below:  https://help.f-secure.com/product.html#business/policy-manager/14.20/en/task_71F3EEBC7E55465DA945969196067962-14.20-en   Article no: 000016402
View full article
Issue: How to backup and restore Policy Manager Server database ? Resolution: Read the following instructions completely before you start working on the server. If you want to keep the DNS name, just move h2db to the new host, stop the old host and start the new one. If you change the DNS name of the server, you must follow the instructions below. Create a backup of the Policy Manager Server: 1. Stop the Policy Manager Server service. 2. Back up the directory <F-Secure Installation Folder> \ Management Server 5 \ data \ h2db>.  Note: Please copy the DB on some different location as the one PM is installed. 3. Restart the Policy Manager Server service. Now perform the installation on the new server. The current installation file can be found here Note: To avoid the communication issues, use exactly the same ports by the installation like for the old F-Secure  Policy Manager Server . To restore secured Policy Manager data: 1. Stop the Policy Manager Server service. 2. Copy the backup to the <F-Secure Installation Folder> \ Management Server 5 \ data \ h2db> directory to the correct location. 3. Restart the Policy Manager Server service.   After the installation is complete, the new F-Secure Policy Manager Server has the complete domain structure, including the settings. After logging into the old server using the Policy Manager Console, enter the address of the new Policy Manager Server <F-Secure Management Agent / Data Communication / Protocols / HTTP / Management Server Address>   and distribute the policies for all your policy domain. Note that the policy setting needs to be locked down to ensure that it's not getting overwritten by locally defined settings. Now all clients will connect the new server. Once all clients are connected without errors with the new Policy Manager Server, you can turn off the old one. You may also find additional instructions in our community:   Article no: 000001258
View full article
Issue: How to block specific extensions using “Disallowed Inbound Files“ for incoming, outgoing and Internal with F-Secure Email and server security. I want to block only these extensions " *.doc *.docx *.docm *.xlx *.xlsx *.xlsm" for Internal email only, but not Outgoing or Incoming   Resolution: Each mail route has its own settings. You need to individually define which match list to use. You can use Policy Manager Console to make these changes, if you are managing your F-Secure Email and Server Security via Policy Manager, or use the Web Console to login to your Email and Server Security locally. As you can see here, I am using a different Match list for each of my mail route, where I have defined the file types I want to block. On Actions, I have however selected "only drop the attachment", not the whole message. Now, I have activated each list for my Email traffic scanning accordingly, and each of them has their own list that contains the Extensions I want to be blocked from attachments.   Note: I did not use the default "Disallowed Files" from Lists and templates as I wanted to have my own customized lists. If you are using the default list on each email route, it means that the same rules will apply for all.   Article no: 000016592
View full article
Issue: F-Secure Linux Security 64: launching a manual scan as a non-root user fails with the following error: /opt/f-secure/linuxsecurity/bin/fsanalyze: line 56: /etc/opt/f-secure/fsbg/mgmt/lock: permission denied   Resolution: Running fsanalyze with a non-root user is currently not supported. We are working on providing this functionality, which will become available in a future release. Current estimate for releasing this feature is 31.10.2019 As a workaround, do the following: Run a manual scan on the system using fsanalyze with a root account, or Configure a scheduled scan via Policy Manager Console You can also use Linux Security 11.10, which has support for manual scanning using fsav (5) even for non-root users. Linux Security 11.10 is still supported until 31.12.2020. Article no: 000015618
View full article