Support articles

Business Suite

  • Should I disable or uninstall Windows Defender on Windows Server 2016/2019/2022 after installing Server Security or Email and Server Security or Elements Endpoint Protection for Servers?

    Read more
    Issue:

    I've installed  Server Security or Email and Server Security or Elements Endpoint Protection on a Windows Server 2016/2019/2022 server, but Windows Defender real-time protection is still on. Should I deactivate it when I'm using the WithSecure product?

    Resolution:

    Yes, Windows Defender should be deactivated when using Email and Server Security or Elements Endpoint Protection. Multiple Anti-Virus products running at the same time may cause conflicts.

    On Windows Server 2016/2019/2022, Windows Defender will not enter passive or disabled mode automatically if you install a third-party antivirus.
    If you're using a non-Microsoft antivirus product as your primary antivirus solution on Windows Server, you must set Microsoft Defender Antivirus to passive mode or disabled mode manually. Please find more details here. Microsoft Defender Antivirus on Windows Server

    Microsoft's general recommendation is to uninstall the Defender on the server installations.

    Passive mode is something controlled by Windows, so it could be changed by Windows and we don't control it.

    After installing a third-party antivirus you should uninstall Windows Defender AV on Windows Server 2016 to prevent problems caused by having multiple antivirus products installed on a machine.

    If you are using Windows Server, version 1803 and Windows 2019, you can enable passive mode by setting this registry key:

    Path: HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection
    Name: ForceDefenderPassiveMode
    Value: 1

    In case of uninstalling Windows Defender, you can use this Powershell command:

    Uninstall-WindowsFeature -Name Windows-Defender

    It will require a restart and after that, Windows Security will not be visible with Antivirus at all but WithSecure still functions.

    MsMpEng.exe will also not be running anymore
     

  • Security Cloud Client is not connected on Server Security / Client Security

    Read more
    Issue:

    Security Cloud Client is not connected on Server Security / Client Security

    Resolution:

    You need to ensure that the affected F-Secure host is allowed to connect to the URL:

    • * https://a.karma.sc2.fsapi.com
    • * https://api.doorman.fsapi.com

    You can try to open https://a.karma.sc2.fsapi.com/healthcheck and https://api.doorman.fsapi.com/doorman/v1/healthcheck in web browser on the host. If the connectivity works you shall see "OK" message in return.

    Also, do take note that the URLs are subject to change in the near future. We recommend allowing the connectivity to *f-secure and *.fsapi.com. To validate the connectivity to WithSecure backend, you can run the Connectivity Tool (wsconnectionchecker.exe) from C:\Program Files (x86)\F-Secure\<Client Security or Server Security>\ui on the device, using all accounts including LOCAL SYSTEM and Network Service account.

    If this host requires a connection via HTTP proxy to access this URL, you have to configure these settings via the WithSecure Policy Manager Console:

    1. Log on to your Policy Manager Console.
    2. Select the Policy domain 
  • Push installation of Client Security from Policy Manager fails with error code 53

    Read more
    Issue:

    I am trying to push a Client Security installation from the Policy Manager, but the installation fails with error code 53.

    Resolution:

    Error code 53 means that the network path was not found:
    ERROR_BAD_NETPATH
    53 (0x35)
    The network path was not found.

    System Error Codes (Windows)

    Make sure, that:

    1. The installation account have enough rights (has to be local or domain administrator).

    2. Enable the Remote registry service on the clients (To enable remote registry service go to Control Panel -> Administrative Tools -> Services -> Remote registry).

    3. Admin$ shares is enable on the client as well as the PMS, please try to access the admin$ share drive on the client from PMS and vice versa to confirm on this.

    4. Windows Firewall is disable in the service on both clients and PMS, to avoid blocking the network traffic from getting through.

    5. Both Policy manager and workstation are in the same network.

    6. Certain Inbound traffic need to be allowed for the workstation such as RPC(TCP 135 Port), NetBios (137-139) and SMB (TCP 445 port) on your firewall (if there's any)

    7. On the client, go to Control Panel->Administrative tools->Local security policy->Local policies-> Security Options - Network Access: sharing and security model for local accounts, check that setting. Make sure is Classic - local users authenticate as themselves" 

    8. Otherwise you can create an .msi package and run the installation locally on the client, you can find more information about that here:

    Push Installations

  • Policy Manager Console does not appear when running the "sg fspmc -c /opt/f-secure/fspmc/fspmc" command

    Read more
    Issue:

    Customer run the normal command of
     

    sg fspmc -c /opt/f-secure/fspmc/fspmc

    to login to Policy Manager Console but it does not apper and there is no output being shown on Terminal.

    Resolution:

    Graphical User Interface (GUI) enabled environment is needed in order to use F-Secure Policy Manager for Linux.
    Hence, you need to enable the GUI and run the command to login to the F-Secure Policy Manager Console.

  • Policy-based upgrades and installations are failing with error status "download interrupted"

    Read more
    Issue:

    We are using the policy-based installation option to upgrade our clients, from which we receive status "Failed: download interrupted" 

    Resolution:

    By default WithSecure Policy Manager Server can handle a maximum of 50 simultaneous package download requests. If the network cannot handle the bandwidth required for 50 simultaneous downloads, the policy-based installation or upgrade operation might fail. This error can also be the result of, if you have a sub-network with low bandwidth, which tries to fetch packages for several minutes.

    For a network with low bandwidth, that can not handle such a high network load, we recommend to use the  Policy Manager Proxy as an option.
    Policy Manager Proxy offers a solution to bandwidth problems in distributed installations of Client Security and Server Security by significantly reducing load on the networks. More about this topic can be found in the Help Guide. The Policy Manager Proxy can be downloaded from the WithSecure page: WithSecure™ Download Center | WithSecure™

    Another solution, which can decrease the network load, is to use the additional_java_args setting: -DmaxSynchronousPackageRetrievalRequests=25

    This settings changes the maximum number of simultaneously handled package download requests for policy-based installations. 

    You can apply this change on your WithSecure Policy Manager Server by following these steps:

    1. Open the Command Prompt as an administrator and use the following command to stop the Policy Manager Server service:
      • Policy Manager 15: net stop fsms
      • Policy Manager 16: net stop wspms
    2. Open regedit and navigate to:
      • Policy Manager 15: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Data Fellows\F-Secure\Management Server 5
      • Policy Manager 16: HKEY_LOCAL_MACHINE\SOFTWARE\WithSecure\Policy Manager\Policy Manager Server
    3. Select additional_java_args and double-click it
    4. Enter the following string to Value Data: -DmaxSynchronousPackageRetrievalRequests=25
    5. Use Command prompt to restart the Policy Manager Server service:
      • Policy Manager 15: net start fsms
      • Policy Manager 16: net start wspms

    Note: If there is no existing additional_java_args registry entry, you can create one. Set the type as REG_SZ.

     

  • Policy Manager Console 15.30 could not launch on a computer with NonVisual Desktop Access (NVDA) screen reader installed

    Read more
    Issue:

    NonVisual Desktop Access (NVDA) user is unable to start / run Policy Manager Console after upgrading to or installing version 15.30 

    Resolution:

    We have tested and found that Policy Manager Console 15.30 JRE is some how missing some accessibility support.

    While the R&D team is working on getting this fixed on the upcoming build, please follow the instruction below for a temporary workaround.

    1. Install Policy Manager Console 15.21
    2. Copy the jre folder in C:\Program FIles (x86)\F-Secure\Administrator\ to some temporary place like desktop.
    3. Install Policy Manager Console 15.30
    4. Rename the existing jre folder in C:\Program Files (x86)\F-Secure\Administrator\ to jre-orig
    5. Copy the jre folder that was taken from the Policy Manager Console 15.21 installation earlier and paste it in to C:\Program Files (x86)\F-Secure\Administrator\

    You should be able to launch Policy Manager Console 15.30 after this.

    If issue persists, the reason is in another Java installed at the target host enabling assistive technologies for all JVMs. As Policy Manager versions starting from 15.30 are using the Java runtime image with all unused modules removed (to lower the attack surface for vulnerabilities like log4j), this technology can not be loaded to the Policy Manager Console.

    As a workaround (instead of replacing the JRE runtime) you can disable this technology for the current user:

    1. Open C:\Users\<username>\.accessibility.properties as a text file (i.e. using Notepad)
    2. Comment following lines in the config by adding hashmark (#) in front of them:
      • assistive_technologies=com.sun.java.accessibility.AccessBridge screen_magnifier_present=true
  • Policy Manager OpenJDK platform process is consuming high memory usage in the server

    Read more
    Issue:

    Why is the OpenJDK Platform process from WithSecure consuming 90% (or high usage) of memory, causing the server to be slow?

    Resolution:

    The WithSecure Policy Manager uses the OpenJDK platform to run.

    In Windows, you can check if the process belongs to the Policy Manager by checking the path of the executable (Right-click process > Open file location). The Policy Manager OpenJDK process is executed from the Policy Manager installation directory, <installation folder\F-Secure\Management Server 5\jre\bin.

    If the issue occurs right after upgrading your Policy Manager to the latest version, or after migration of the H2DB database, the root cause can be related to the high number of alerts in your current H2DB database. You can make use of the WithSecure Policy Manager Database Maintenance tool to drop these alerts from your database as per guide (see: https://www.withsecure.com/userguides/product.html#business/policy-manager/16.00/en/task_E02887FA732B4D9686C82ADE63844464-16.00-en)

    If this does not help, try using the recovery tool.

    For Windows: https://community.withsecure.com/en/kb/articles/5639-using-the-policy-manager-for-windows-database-recovery-tool-version-10-00-and-later
    For Linux: https://community.withsecure.com/en/kb/articles/5621-using-the-policy-manager-for-linux-database-recovery-tool-version-10-00-and-later

     

  • New Linux Security(2024-03-18) offline database update fails

    Read more
    Issue:

    New Linux Security(2024-03-18)  fails offline database update

    Resolution:

    New Linux Security(2024-03-18)  update includes changes which will affect the procedure to install future malware definition or product updates from ZIP archives.  Please continue reading if you are currently making use of ZIP archives to install updates using the offline-update program.

     After updating your product installation to the new version, follow these steps to prepare update ZIP archives in the future:

    1. Log on to the endpoint on which you intend to install updates from a ZIP archive.
    2. Run the command
      /opt/f-secure/fsbg/bin/withsecure-migrator status
    3. Check the last line of output from the above command.
    4. If the system reports that the command does not exist, or the command reports “not-performed” or “not-ready”, you can prepare a new f-secure-updates.zip archive for updates by using any version of fspm-definitions-update-tool and channels.json files you might already have available, and install the updates as before from the f-secure-updates.zip file using the offline-update program. Before starting to prepare another ZIP archive later, however, return to step 1 of these instructions.
    5. If the command at step 2 reports "migrated", the procedure for installing the updates changes as follows:
      1. First, please verify that you are using a recent enough version of fspm-definitions-update-tool for creating update archives.
        • If you are using fspm-definitions-update-tool from a Policy Manager Server 16 installation, you are already at a new enough version.
        • If you are not using Policy Manager 16, or are unsure about the version of fspm-definitions-update-tool, download the latest version of fspm-definitions-update-tool from the product download page, and extract the files to a directory.
          Support - Linux Security
      2. Second, download the latest version of the channels.json file to use to configure fspm-definitions-update-tool:
        https://download.f-secure.com/corpro/ls64/current/channels.json
        As before, replace the channels.json file under fspm-definitions-update-tool's conf/ subdirectory with the downloaded file, remove the data/ directory if it exists.
      3. Run the fspm-definitions-update-tool program.  fspm-definitions-update-tool will create a fresh data/ subdirectory with two ZIP archives: f-secure-updates.zip and withsecure-updates.zip.  You must now use the withsecure-updates.zip file to install updates on the endpoint using the offline-update program.
        (The f-secure-updates.zip file should no longer be used for installing updates on that endpoint.  When run, fspm-definitions-update-tool will however continue to create this file to support packaging updates for endpoints which still need this file.)
      4. After installing the product updates for the first time from the withsecure-updates.zip file on an endpoint, it won't be necessary to verify the status of the installation again on that endpoint (step 2); all later product updates can be installed using the withsecure-updates.zip file.

    If you still experience update error, please refer this knowledge as well.
    https://community.withsecure.com/en/kb/articles/31302-the-latest-linux-security-64-update-fails-to-install

  • Policy Manager warns that the latest virus definition update is several days old

    Read more
    Issue:

    WithSecure Policy Manager is warning on the Server events for the last 24H event list that the latest virus definition update is several days old. 

    Resolution:

    If the WithSecure Policy Manager Server is showing this event on the dashboard:

    • Make sure that you have upgraded both the Policy Manager and the clients to a supported version. You need to have at least version 16 of both Policy Manager and the clients, since old versions will not be able to connect to the WithSecure Update servers.
    • Verify that the server is able to connect to the WithSecure Update servers. You can download and run the WithSecure Connectivity Tool to make sure the client and servers can connect to all required addresses: https://download.withsecure.com/connectivitytool/ConnectionChecker.exe
    • Verify that the server has more than 2GB of free disk space and that there are no low disk space alerts shown on the server events list. If the server has less than 2GB, the Policy Manager Server will automatically stop downloading new virus definition updates
    • Verify there is no conflicting third party software (antivirus) blocking WithSecure's updates.
  • PDF report sent from scheduled reporting in Policy Manager 15.x is empty

    Read more
    Issue:

    I receive the PDF report sent from scheduled reporting in Policy Manager 15.x.

    However, when I attempt to open the PDF report attached in the mail, the PDF report is empty and does not show any information.

    Resolution:

    To workaround the issue, we recommend importing the Policy Manager CA to the trusted root:

    1. Run the following command to export Policy Manager CA certificate:
      • "c:\Program Files (x86)\F-Secure\Management Server 5\jre\bin\keytool.exe" -keystore "c:\Program Files (x86)\F-Secure\Management Server 5\data\fspms-ca.jks" -alias fspm-ca -exportcert -file fspms-ca.cer -rfc -protected
    2. Run certlm.msc to bring up the Windows certificate store.
    3. Import fspms-ca.cer (that you exported in step 1) to the Trusted Root Certification Authorities -> Certificates
    4. Reboot the Policy Manager Server, to take the updated root CA in use for all services