Support articles

Business Suite

  • 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. 

     
     

  • Does Business Suite Client Security for Mac use same license keycode as the Client Security Windows version?

    Read more
    Issue:

    Does Business Suite Client Security for Mac use same subscription key or license keycode as the Client Security Windows version?

    Resolution:

    No, Client Security for Mac client does not use the same license keycode as the Windows version of Client Security. It has its own license keycode which you should be able to see in the license certificate. 

    If the Client Security for Mac license keycode is not listed in the license certificate, please contact your WithSecure partner and they will be able to provide an updated license certificate. 

  • Where can I find the new license keycodes for the latest Business Suite Client Security and Server Security versions?

    Read more
    Issue:

    Where can I find the license key codes for the latest version of my Business Suite software?

    • Client Security for Windows or Mac
    • Server Security 
    • Email and Server Security 
    • Linux Security 64
    Resolution:

    The latest Business Suite (Client Security, Server Security and Linux Security 64) license keycodes are listed in the license certificate. You can be in contact with your WithSecure reseller partner if you need to acquire a new license certificate which includes all the new license keycodes for the latest versions.

    A WithSecure partner with access to Partner Portal can find the license certificates from the Partner Portal:

    1. Log in to the Partner Portal https://partnerportal.withsecure.com
    2. Navigate to Sales > Accounts (This will take you to the list of your customers)
    3. Search for the relevant customer using the search field at the top right (if necessary)
    4. Click on the customer name to open the details view.
    5. Navigate to the "Deal Ordering & Subscriptions" tab
    6. Scroll down to the "Assets" section
    7. Click on the "Get Certificates" button
    8. Select the desired language and download the document
  • How to check if Policy Manager Server is using the offline registration.json token file?

    Read more
    Issue:

    How to check if Policy Manager Server is using the offline registration.json token file?

    Resolution:

    When the offline registration of Policy Manager has been performed successfully using the registration.json file, there is no notification mentioning about the license expiring when logging in to the Policy Manager Console. Or if the license was already expired, the Policy Manager Console simply lets you log in successfully.

    If you would like to confirm that the offline registration is working fine, Policy Manager registration related logs can be found in "fspms-registration.log" file.

    In case of Policy Manager for Linux: 
    /var/opt/f-secure/fspms/logs/fspms-registration.log

    In case of Policy Manager for Windows: 
    C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\log\fspms-registration.log

    When offline token is applied, the following logs will be output in "fspms-registration.log", which means the token has been applied and it is using offline registration. 

    [fspms-registration.log]
    11.03.2022 14:42:59,012 INFO [c.f.f.r.RegistrationLoaderImpl] - Registration token for customer number 1-XXXXX has been successfully loaded.
    11.03.2022 14:42:59,012 INFO [c.f.f.r.RegistrationLoaderImpl] - Registration token file has been deleted
    ...
    11.03.2022 11:26:45,412 INFO [c.f.f.r.RegistrationUpdater] - Refreshing registration...
    11.03.2022 11:26:47,084 INFO [c.f.f.r.RegistrationRestTemplate] - Connected to registration server successfully (direct connection)
  • What is the official way to silently remove or uninstall Client Security or Server Security from Windows computers?

    Read more
    Issue:

    What is the official way to silently remove or uninstall Client Security or Server Security from Windows computers?

    Resolution:

    Business Suite (Client Security and Server Security) has a remote uninstallation operation feature, which can be used to uninstall the product remotely from Windows hosts. Mac or Linux hosts require manual local uninstallation using an uninstallation tool. 

    1. Log in to the Policy Manager Console
    2. Go to the Installation tab
    3. Select a host or policy domain from the domain tree
    4. Click on the uninstall button from the "Installed products summary" table
    5. Distribute the policy (CTRL + D)

    Once the host receives the operation, the Client Security or Server Security client will be silently uninstalled from the host.

    Note: For the uninstall button to appear on the "installed products summary" table, you will need to have the .jar file of that particular Client Security or Server Security version imported in the Policy Manager Server's installation packages.

     

    If for some reason the clients are not connected to a Policy Manager Server and therefore you cannot uninstall Client Security or Server Security remotely from the Policy Manager Console with an operation, the workaround would be to use the WithSecure Uninstallation Tool for Windows. The WithSecure Uninstallation Tool can be run from the command line with an additional parameter to remove the system protection unattended (silently):

    1. Download the WithSecure Uninstallation Tool from the Support Tools page: Support tools - WithSecure™ 
    2. Open a Windows Command Prompt with administrator privileges
    3. Navigate to the location where you saved the WithSecure Uninstallation Tool
    4. Run the following command:
      1. WsUninstallationTool.exe --silent

    This will remove all WithSecure products from the computer silently.

  • How to check the current version number of Linux Security 64

    Read more
    Issue:

    I have installed Linux Security 64, how to check the current version number of the product?

    Resolution:

    You can check the version of each component that has been installed for Linux Security 64 by running the following command in the Terminal: cat /etc/opt/f-secure/*/release-info.ini'

    Example: 
     

    # cat /etc/opt/f-secure/*/release-info.ini
    [release]
    fscomp_name=fsbg-channel
    fscomp_version=1.0.938
    
    [release]
    fscomp_name=fsbg-channel
    fscomp_version=1.0.938
    [release]
    fscomp_name=linuxsecurity2-channel
    fscomp_version=12.0.146

     

  • Client Security or Server Security update download and installation fails with error: "115 (operation in progress)"

    Read more
    Issue:

    Client Security or Server Security malware definition database and engine update download and installation fails with error: "115 (operation in progress)" shown in the Automatic Update Agent (AUA.log) when clicking View log file from the local client's Updates settings page. 

    Resolution:

    If you are 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. Run the FSAUA-Reset.exe tool and restart the problematic client. 

    If you have several Client Security or Server Security hosts showing this error, you can try to manually reset the GUTS2 update folder on the Policy Manager Server:

    Here are the steps how to manually reset 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

     

  • How to install Policy Manager Server to communicate via HTTP proxy?

    Read more
    Issue:

    How to install WithSecure Policy Manager Server to communicate via HTTP proxy?

     

    Resolution:

    If the Policy Manager or Policy Manager Proxy host does not have a direct internet connection, specify the HTTP proxy configuration as 'PROXY_SERVER' MSI argument for example by running an MSI file from the command line and passing the arguments to it:

    msiexec /i policy-manager.msi PROXY_SERVER=http://proxy.example.com:8080

    Use percent encoding for any reserved URI characters in the user name or password. For example, if the password is ab%cd, you need to enter it as follows:
    http://user:ab%25cd@proxy.example.com:8080

    You can find all the supported MSI parameters in the user guide: Supported MSI parameters | Policy Manager | 16.10 | WithSecure User Guides 

    fspms.proxy.config is not created by default with Policy Manager Server to C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\

    You can use proxy_server parameter during installation to specify the proxy address, and then the fspms.proxy.config file will be created in that location.