Support articles

Business Suite

  • Business Suite Client Security or Server Security WithSecure Plugin Hosting Service is causing high CPU usage

    Read more
    Issue:

    I am noticing high CPU usage by WithSecure Plugin Hosting Service in Windows host installed with Business Suite Client Security or Server Security, why is this happening? It is slowing down the performance of the device. 

    Resolution:

    When WithSecure plugin hosting service is using high amounts of CPU performance and disk resources, it is an indication that: 

    • A scheduled or manual scan is currently running and it is scanning the files
    • Real-time scanning scanning files that are accessed by the system 

    If you want to confirm if a scheduled or manual scan is running, you can check from the Task Manager's Details tab if the fsscan.exe process is running. If it is, then a scheduled or manual scan is currently running and that is causing high CPU and RAM usage, especially if you have scanning of compressed files (archives) enabled in the host's policy settings.

    To change the scheduled and manual scanning settings for Client Security or Server Security:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Manual scanning settings page.

    Here you can find separate sections for scheduled scanning and manual scanning settings. To decrease the CPU usage during scans, you can:

    • Disable Scan inside compressed files
    • Enable Run scanning as low priority
    • Enable Scan only known file types 

    To stop or cancel a scheduled scan, you can follow these steps:

    1. Open the WithSecure client's user interface
    2. Click on the three dots and select Recent events 
    3. Click on the Cancel button on the right side of the ongoing scheduled scanning event
      • Note: the Allow users to skip scheduled scans setting must be enabled for a local user to be able to stop a scheduled scan

    If the issue is not caused by a manual or scheduled scan, it could be that real-time scanning is scanning some files for a very long time or very frequently. If you collect a wsdiag diagnostic file from the device, you can check the fa.log (frequently accessed) log file from the path wsdiag.zip\f-secure\logs\system\FSAV\. 

    Here is an explanation of the columns in the fa.log:

    • First column: 1 means scan was longer than usual. 2 means file was scanned frequently
    • Second column: how many milliseconds the last scan took and if file has been scanned frequently, How many milliseconds in total has been spent scanning the file
    • Third column: How many times the file has been scanned 
    • Fourth column: Date and time of last scan
    • Seventh column: path to the file

    You can use the information in the fa.log to create real-time scanning exclusions in the device settings. 

    High CPU usage can also happen if Security Cloud is either disabled or it doesn't have proper network connectivity. To check the network connectivity, run the WithSecure Connectivity Tool from the product's installation folder: 

    • Client Security: C:\Program Files (x86)\F-Secure\Client Security\ui\fsconnectionchecker.exe
    • Server Security: C:\Program Files (x86)\F-Secure\Server Security\ui\fsconnectionchecker.exe

    If Security Cloud is disabled, you can enable it from the policy settings:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain in the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Real-time scanning settings page 
    5. Enable Use Security Cloud
    6. Distribute the policy (Ctrl + D)

    If the high CPU usage appears on a Terminal Server:

    If fshoster32.exe causes high CPU usage on a Terminal server, we propose to disable the local user interface for Server Security:

    1. Log in to the Policy Manager Console
    2.  Select a host or policy domain in the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Centralized management settings page
    5. Scroll down to the Local user interface section
    6. Disable Show local user interface 
    7. Click Save profile

     

  • What is the expected behavior for Business Suite endpoint products after the license has expired?

    Read more
    Issue:

    What is the expected behavior for Business Suite endpoint products after the license has expired? 

    Resolution:

    Business Suite Policy Manager: 

    • Admin still have a grace period of 7 days to access Policy Manager Console and apply configuration changes. 

    Client Security and Server Security endpoint clients: 

    • Endpoints will keep receiving updates for the grace period and will stop receiving it after that.
    • Endpoint's security features will stop working right after the license expires, hence system will be unprotected. 

    Before the subscription expires, we recommend to allow local uninstallation in the policy settings, so that the Client Security or Server Security clients can be uninstalled even after the subscription has expired. 

  • How to collect installation trace logs for WithSecure Linux Protection and Linux Security 64

    Read more
    Issue:
    Sometimes WithSecure Linux Protection or Linux Security 64 installation and/or activation fails and additional trace logging is required to determine the root cause. This document describes how to generate the trace logs while uninstalling and reinstalling the product on the affected system.
     
    Resolution:

    To generate the logfiles, use these instructions. Perform them as root or while using sudo

     
    Remove Linux Protection completely 
     
    • RHEL-based distributions: rpm -e linuxsecurity-installer
    • Debian-based distributions: dpkg -r linuxsecurity-installer
    • rm -rf /opt/f-secure
    • rm -rf /etc/opt/f-secure
    • rm -rf /var/opt/f-secure
    If the device is still visible in the Elements Security Center portal, remove the device from the portal as well.
     
    Reinstall Linux Protection

    • RHEL-based distributions: rpm -Uvh linuxsecurity-installer.rpm 
    • Debian-based distributions: dpkg -i linuxsecurity-installer.deb 
    Enable setup tracing

    export FSECURE_TRACE_SETUP=.

     

    Activate Linux Protection while capturing the trace output:
    /opt/f-secure/linuxsecurity/bin/activate --psb --subscription-key <insert-your-key> id> 2>&1 | tee -a setup_trace.log

    When the issue reproduces, share the following information via the support ticket.

    1. The file setup_trace.log created above
    2. Freshly created fsdiag file created by running /opt/f-secure/linuxsecurity/bin/fsdiag․sh
    3. output from the terminal used to reinstall the product (copy/paste this into a file or the email) showing the failed installation including errors.
  • Client Security or Server Security fails do download update from Policy Manager, AUA.log shows "try later" error

    Read more
    Issue:

    Client Security or Server Security are unable to download malware definition database and engine updates from the Policy Manager Server or Proxy due to the update check ending with "try later" result:

    I: Connecting to <Policy Manager Server or Policy Manager Proxy Server address>/guts2
    I: Update check completed with 'try later' result

    Resolution:

    This could happen in case the Policy Manager Server/Policy Manager Proxy Server is attempting to download the updates (but unable to reach the web update server), and respond with "try later".

    You need to ensure that the Policy Manager Server/Policy Manager Proxy Server is able to reach the web update server. Do allow the connectivity to *.withsecure.com and *.fsapi.com in the Policy Manager Server's HTTP proxy or firewall.

    We recommend to run the WithSecure Connection Checker tool to make sure your servers and hosts are allowed to connect to all the necessary addresses: https://download.withsecure.com/connectivitytool/ConnectionChecker.exe

    If you Policy Manager Server requires HTTP proxy to reach the WithSecure GUTS2 update server, you need to define the proxy server address in the fspms.proxy.config file. 

    Windows: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\ fspms.proxy.config

    Linux: /var/opt/f-secure/fspms/data/fspms.proxy.config

    If issue remain, try to manually delete old updates from the Policy Manager Server's GUTS2 updates folder: 

    Here are the steps how to manually reset on a Windows Server the Policy Manager Server's updates GUTS2 folder:

    1. Stop the Policy Manager Server service by using Command Prompt
      1. net stop wspms
    2. Delete the contents of the following folder: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\guts2\updates
    3. Start the Policy Manager Server service: 
      1. net start wspms

    On Linux Servers, delete contents of  /var/opt/f-secure/fspms/data/ and restart the server.

    If you are still experiencing update download or installation issues on your Client Security or Server Security clients, you can run the FSAUA-Reset.exe tool on the clients: Support tools - WithSecure™ 

    It resets the WithSecure Automatic Update Agent (AUA) agent on the clients and forces them to re-download the updates. 

  • The Policy Manager "Denied website blocked" alert doesn't include the website URL address

    Read more
    Issue:

    There are "Denied website blocked" alerts in the Policy Manager Console's Alerts tab that don't include the website URL address. Why are the website URL addresses not shown in the alerts sent from the Client Security and Server Security devices?

    Resolution:

    The website URL address will not be shown by default if the address has been added by the administrator to the Web Content Control > Disallowed sites list.  

    • Settings >Windows > Web Content Control > Disallowed sites

    This is due to user privacy reasons.

    If you want to include the URL addresses in alerts that are not about harmful or malicious websites being blocked, you can enable the Include the blocked URLs in all alerts setting. This setting will change the behavior so that the URLs addresses are included when:

    • Website URL address has been added to the Disallowed sites list by the administrator
    • When Connection Control blocks a website during an active banking session
    • When a website belonging to a disallowed Web Content Control category is blocked

    Steps to enable the Include the blocked URLs in all alerts setting:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Go to the Settings tab
    4. Navigate to the Windows > Browsing Protection settings page
    5. In the General section, enable the Include the blocked URLs in all alerts setting
    6. Distribute the policy (Ctrl + D)
  • Getting 'License already expired' error when installing Linux Security 64

    Read more
    Issue:

    We are getting the "license already expired" error message during the Linux Security 64 installation on a client machine. 

    Resolution:

    If your Business Suite license is valid and you are able to log in to the Policy Manager Console, but you still get the "License already expired" error when installing Linux Security 64 on a Linux device, then the most likely reason is that you are using an old installation package for Linux Security 64.

    We recommend you to:

    1. Remove the previously imported Linux Security 64 .jar installation package from the Policy Manager Console
    2. Download the latest Linux Security 64 .Jar installation package from our downloads page and import it to the Policy Manager Console: Linux Security - WithSecure™ 
    3. Export a new installer and run in on the Linux device

    Note: Before running the installer, make sure that there are no files left of the previous failed installation: Uninstalling the product | Linux Security 64 | Latest | WithSecure User Guides 

    If you are installing Linux Security 64 as a stand-alone installation in an isolated or offline environment without Policy Manager managed mode, there is also a need to use a new content package (withsecure-updates.zip) to update the definitions: Creating the content package for isolated environments | Linux Security 64 | Latest | WithSecure User Guides 

  • How to enable mailbox scanning feature for Client Security?

    Read more
    Issue:

    How to enable mailbox scanning feature for Client Security? We want to have Client Security to scan the local mailbox file for malicious attachments. 

    Resolution:

    You can enable scanning of mailbox files and archives for Client Security devices by following these steps:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Go to the Settings tab
    4. Navigate to the Windows > Manual scanning settings page
    5. Enable Scan inside mailbox files (pst, ost,...)
    6. Distribute the policy (Ctrl + D)

    When "Scan inside mailbox files" is enabled for Client Security, a manual scan will scan the mailbox archive and report if any infections are found. 

    Note: Infected files within mailboxes will not be automatically deleted or quarantined. You need to take manual action on the infected file.

  • Client Security goes into "Network isolation" state by itself

    Read more
    Issue:

    One or more Client Security hosts have gone into a "Network isolation" state and are unable to connect to the internet. What can cause Client Security to automatically isolate device from the network?

    Resolution:

    If Client Security devices have been automatically isolated from the network by Client Security, It is likely that the network quarantine feature has been enabled in the policy settings for the device. The network quarantine setting can automatically Client Security devices from the network due to outdated virus definition on the managed hosts or if real-time scanning has been disabled on the host. 

    To check the network isolation settings in the policy:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Go to the Settings tab
    4. Navigate to the Windows > Firewall settings page
    5. Scroll down to the Network quarantine section
    6. Check if the network quarantine feature is enabled

    If network quarantine is enabled, the Virus definition age to activate network quarantine value determines how old the definitions can be before the Client Security host is automatically isolated from the network.

    The network quarantine section also includes the setting for "Activate network quarantine on host if real-time scanning is disabled". 

    You can release a host from network isolation by following these steps:

    NOTE: The operation cannot be performed on domain level or when multiple hosts are selected

     

    1. Log in to Policy Manager console
    2. Select the host under Domain tree
    3. Click on the Operations tab at the top menu
    4. Under Network isolation, click the 'Release' option
  • Why is the quarantine action not available for Linux Security 64?

    Read more
    Issue:

    In the Policy Manager Console's Linux > Real-time scanning settings in the Actions for real-time scanning, the Action for malware drop-down menu does not include a "quarantine" action. Why is the quarantine action not available for Linux Security 64?

    Resolution:

    The Action for Malware: Quarantine option is only available in Windows clients and Servers.

    In Linux Security available actions in real-time scanning are rename, remove (delete) or do nothing when a file is detected as malicious: Using real-time scanning with Policy Manager | Linux Security 64 | Latest | WithSecure User Guides 
     

  • Which license keycode should be used for WithSecure Client Security for Mac?

    Read more
    Issue:

    Which license keycode should be used for WithSecure Business Suite - Client Security for Mac?

    Resolution:

    Business Suite Client Security for Mac has its own license keycode and it does not use the same license keycode as the Client Security for Windows version. Check your latest license certificate if you can find the Client Security for Mac license keycode in it. If your latest license certificate does not include a license keycode for Client Security for Mac, you can contact your WithSecure reseller partner and they can provide you the latest license certificate.