Support articles

Business Suite

  • Devices are getting blocked. How can I grant access to specific devices on Policy Manager?

    Read more
    Issue:

    My devices are getting blocked. How can I grant access to specific devices on Policy Manager?

    Resolution:

    You can set rules to allow a specific device while all other devices under the same class are blocked.

    You need to know the hardware ID of the device that you want to allow before you can create a rule that grants full access to the device.

    To add an exception to a rule, follow these instructions.

    1. Get the hardware ID for the device that you want to allow. The hardware ID has to be more specific than the ID which is used to block the device.
    2. Go to the Settings tab and select Windows > Device control.
    3. On the Device access rules table, click Add.
    4. Enter the hardware ID for the device as the Hardware ID in the new rule.
    5. Set Access Level to Full access to allow the use of the device.
    6. Set Active to Yes for the new rule.
    7. Distribute Policy
  • Do DeepGuard exclusions accept Windows environment variables or wildcards when the exclusion is created through WithSecure Policy Manager?

    Read more
    Issue:

    Do DeepGuard exclusions accept Windows environment variables or wildcards when the exclusion is created through WithSecure Policy Manager?

    Resolution:

    DeepGuard exclusions for WithSecure Client Security, Server Security and Email and Server Security products support wildcards for DeepGuard exclusions. Follow these steps to create an exclusion using a wildcard:

    1. Log into Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Go to the Settings tab and select Standard view
    4. Go to Real-time scanning 
    5. Scroll down and enable Do not scan the following files and applications 
    6. Click Add and select Folder path
    7. Enter the folder path, for example: *\examplefolder\subfolder\* and click OK
    8. Distribute the policy (Ctrl + D)

    More examples can be found in the following F-Secure Community article: https://community.f-secure.com/business-suite-en/kb/articles/5665-using-wildcards-in-exclusions-in-real-time-scanning

  • DNS queries are blocked by the Botnet Blocker in Client Security/Server Security.

    Read more
    Issue:

    DNS resolution for certain sites are blocked with the product installed. How to avoid this from happening?

    Resolution:

    Most likely the DNS resolution is blocked by the Botnet Blocker feature. The site is rated as unsafe and hence blocked by the feature.

    You need to do the following:

    1. Share the URL with the Labs team, for further investigation. The Labs team will whitelist the URL if the site is not malicious: https://www.withsecure.com/en/support/contact-support/submit-a-sample

    2. Whitelist the blocked site or the IP address of the blocked site via the Advanced View in the PM Console at:

    1. Log in to Policy Manager Console
    2. Highlight a host or policy domain from the Domain Tree
    3. Go to the Settings tab
    4. Go to Web content control settings
    5. Click Add from the right side of the Trusted sites list
    6. Add the site or domain URL in the address field
    7. Distribute the policy (Ctrl + D)
  • Client Security and Server Security cannot connect to Policy Manager via reverse proxy

    Read more
    Issue:

    Client Security and Server Security are not connecting to Policy Manager via reverse proxy or proxy.

    Resolution:

    Please use Policy Manager Proxy. Policy Manger is not internet application, but internal network application.  Client Security and Server Security cannot connect to Policy Manager via reverse proxy or proxy. CS/SS need to connect to Policy Manager directly or via Policy Manager Proxy. Some techniques, like Proxy/NAPT, may be working, however F-Secure won't assure those environment. 

  • Client Security or Server Security unable to connect to the Policy Manager Server after installing Server Security on the same server

    Read more
    Issue:

    The symptoms include

    • Clients are unable to download updates from the Policy Manager Server
    • Clients are unable to upload status information to the Policy Manager Server and will eventually show up in Policy Manager Console as disconnected hosts

    However, clients might still be able to download updates because in the default configuration, fallback to WithSecure update servers is allowed.

    A couple of logfiles on the endpoint help to establish, if the client is having a connection problem due to the firewall blocking access on the server.
    Examples are for Client Security 14 but also apply for Server Security 14 and later. Policy Manager Server here is pms.acme.com listening on default ports 80 and 443.

    C:\ProgramData\F-Secure\Log\AUA\Aua.log

    2019-10-02 12:07:25.311 [15d4.1d50]  I: Connecting to pms.acme.com:80/guts22019-10-02 12:07:46.349 [15d4.1d50]  I: Update check failed, error=110 (connection timed out)

    Same is also visible in this log file:

    2019-10-02 12:17:37.502 [15d4.1d68]  I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from pms.acme.com:443 with HTTP proxy ''2019-10-02 12:17:58.535 [15d4.1d68] *E: UpdatablePmCertVerifier::RenewCertificates: Failed to download certificate bodies (FsHttpRequest::Error_Timeout, AsyncSendRequest failed: 12002)2019-10-02 12:18:07.536 [15d4.1d68]  I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from pms.acme.com:443 with HTTP proxy ''

    Error 12002 translates to 

    12002 ERROR_INTERNET_TIMEOUT The request has timed out.

    Resolution:

    WithSecure Server Security uses the Windows Firewall. It is likely that the ports that the HTTP and HTTPS services are using are blocked in the firewall on the server where Policy Manager Server is installed in. This would cause the clients to be unable to be in contact with the Policy Manager Server.  

    To resolve the issue, create a firewall rule allowing inbound HTTP and HTTPS traffic to the server where Policy Manager Server is installed. 

    You can find instructions how to create firewall rules in Policy Manager 14 in this guide.

    Things to consider:

    1. Make sure, the firewall rule is enabled. This is the first checkbox in the Firewall rules table
    2. Make sure, the Server profile containing the rule is assigned as the "Server host profile". In the example below, the profile is called Server (cloned)
    3. The other rules in the profiles in this screenshot are also activated but this is is not needed to meet client Policy Manager Server communication requirements
    4. As this particular rule is only required for the server host running Policy Manager Server, we have selected the server before making the change (the server called here DC1-PETERF)

     

  • Correct way to import certificates into MSG

    Read more
    Issue:

    What is the correct way to combine certificate(s) and key into one file that can be imported into MSG?

    Resolution:

    The files provided by the Certificate Authority needs to be assembled in the following order: Appliance certificate, any intermediate certificate(s), Private key.
    The data can be bundled together in your text editor of choice, and then saved as a .pem-file to be imported into the MSG appliance.
    The end result might look something like this:

    ----BEGIN CERTIFICATE-----

    -----END CERTIFICATE-----
    ----BEGIN CERTIFICATE-----

    -----END CERTIFICATE-----
    ----BEGIN PRIVATE KEY-----

    -----END PRIVATE KEY-----

  • Client Security or Server Security installation failed because Universal CRT is not installed.

    Read more
    Issue:
    • Universal CRT is not installed therefore Client Security or Server Security installation fails.
    • In Policy Manger Console, push installations result in the status error message: "Installation failed. MSI error code is 1603".
    • The following error can be seen in Windows Application Event Logs: "Product: F-Secure Client Security [Premium] 14.XX/F-Secure Server Security [Premium] 14.XX -- Universal CRT is not installed".
    Resolution:

    The latest version of Client Security and Server Security require Windows Universal C Runtime to be installed on the system. Download and install Windows Universal C Runtime from the link here before installing Client Security or Server Security.

    Here is also an alternate link from where to download Windows Universal C Runtime. Use this link, if a server operating system is used.
     

  • Client Security or Server Security Firewall rules made with Policy Manager do not work or appear in the Windows firewall

    Read more
    Issue:
    • Firewall rules made with Policy Manager are not operational on Client Security or Server Security clients.
    • Firewall rules pushed from Policy Manager to Client Security or Server Security clients do not appear / are not visible in the Windows firewall.
    Resolution:

    Check that you have edited the same firewall profile that is in use on the client. This can be done by following these steps:

    1. Open Policy Manager Console
    2. Select the host or domain from the Domain tree
    3. Go to the Settings tab
    4. Go to the Firewall page
    5. Check that Host profile and Profile being edited match

    If they match, the reason why the rule is not applied on the client is because it is an invalid rule. Invalid rules do not appear in the Windows Firewall. If the rule has many IP addresses in it, make sure that you have used a comma ( , ) in between each IP range as a value separator. Using a space or semicolon ( ; ) in between the IP ranges will invalidate the rule and it will not be visible in the Windows Firewall. 

  • Client Security or Server Security DataGuard feature blocks applications running from the Windows Users \ AppData folder

    Read more
    Issue:

    WithSecure Client Security or Server Security DataGuard blocks applications such as Firefox, OneDrive etc. that are installed to and running from the Users \ AppData folder on a Windows computer.

    Resolution:

    If the setting Discover trusted applications automatically is enabled, only applications that are installed under the 'default trusted locations' or utilizing 'default trusted processes' will be allowed to make changes to DataGuard Monitored folders automatically. The default trusted locations and processes are predefined as follows;
     

    C:\PROGRAM FILES (X86)\
    C:\PROGRAM FILES\
    C:\WINDOWS\EXPLORER.EXE
    C:\WINDOWS\FILEMANAGER\PHOTOSAPP.EXE
    C:\WINDOWS\NOTEPAD.EXE
    C:\WINDOWS\SPLWOW64.EXE
    C:\WINDOWS\SYSTEM32\MSPAINT.EXE
    C:\WINDOWS\SYSTEM32\MSTSC.EXE
    C:\WINDOWS\SYSTEM32\NOTEPAD.EXE
    C:\WINDOWS\SYSTEM32\PICKERHOST.EXE
    C:\WINDOWS\SYSTEM32\RUNTIMEBROKER.EXE
    C:\WINDOWS\SYSTEM32\SEARCHPROTOCOLHOST.EXE
    C:\WINDOWS\SYSTEM32\SIHOST.EXE
    C:\WINDOWS\SYSTEM32\SNIPPINGTOOL.EXE
    C:\WINDOWS\SYSTEM32\SPOOLSV.EXE
    C:\WINDOWS\SYSTEM32\WFS.EXE
    C:\WINDOWS\SYSTEM32\WRITE.EXE
    C:\WINDOWS\SYSWOW64\EXPLORER.EXE
    C:\WINDOWS\SYSWOW64\MSPAINT.EXE
    C:\WINDOWS\SYSWOW64\MSTSC.EXE
    C:\WINDOWS\SYSWOW64\NOTEPAD.EXE
    C:\WINDOWS\SYSWOW64\PICKERHOST.EXE
    C:\WINDOWS\SYSWOW64\SEARCHPROTOCOLHOST.EXE
    C:\WINDOWS\SYSWOW64\WRITE.EXE
    C:\WINDOWS\WRITE.EXE

    Since the AppData folder is not on the list, applications installed to the AppData folder will be blocked by DataGuard.

    Resolution is to either:

    1. Uninstall the application from the AppData folder and to reinstall it to a trusted location such as C:\Program Files or C:\Program Files (x86) 
    2. Add the application to the DataGuard Trusted applications list 

    How to add the application to the DataGuard Trusted applications list:

    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. Go to the DataGuard settings page
    5. Scroll down to the Trusted applications table and click Add
    6. Write the full application path to the Applications field
    7. Distribute the policy (Ctrl + D)

    Note: You can use system environment variables when you want to create an exclusion for many users. The supported environment variables are: %USERPROFILE%, %HOMEDRIVE%, %HOMEPATH%, %APPDATA%, %ProgramFIles%, %ProgramFiles(x86)% %ProgramData%, %windir%, %SystemRoot%, %SystemDrive%

  • Client Security or Server Security is not able to connect to Policy Manager Server

    Read more
    Issue:

    Client Security or Server Security is not able to connect to Policy Manager Server. 

    Consequently, the client is unable to auto register itself to the Policy Manager Server and cannot download policies or upload status-information.

    Resolution:

    To troubleshoot similar connectivity issues, open the following file on the computer:

    • C:\ProgramData\F-Secure\Log\BusinessSuite\pmpselectorplugin.log

    Below is an example when communication with the PMS is working (PMS hostname is acme.com):

    2019-03-08 09:08:34.991 [0e70.118c]  I: ***  LOGGING STARTED  *** (UTC+2:00, session: 0x0)
    2019-03-08 09:08:35.283 [0e70.118c]  I: PmpSelectorPlugin::PluginMain: Starting: '100\PmpSelectorPlugin'
    2019-03-08 09:08:35.284 [0e70.118c]  I: ServerFinder::ServerFinder: Last known good server is {host: acme.com, http: 80, https: 443}
    2019-03-08 09:08:35.284 [0e70.118c]  I: `anonymous-namespace'::LoadPmsAddress: Forced PMS address loaded from cosmos: {host: acme.com, http: 80, https: 443}
    2019-03-08 09:08:35.746 [0e70.118c]  I: ServerFinder::Find: Ping to {host: acme.com, http: 80, https: 443} failed
    2019-03-08 09:08:42.801 [0e70.118c]  I: ServerFinder::Find: Ping to {host: acme.com, http: 80, https: 443} failed
    2019-03-08 09:08:48.895 [0e70.118c]  I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from acme.com
    2019-03-08 09:08:49.436 [0e70.118c]  I: UpdatablePmCertVerifier::RenewCertificates: Certificates renewed successfully. Count: 2
    2019-03-08 09:08:49.436 [0e70.118c]  I: CosmosUpdater::UpdateCosmos: Updating cosmos with PMS {host: acme.com, http: 80, https: 443}

    Below is an example where communication is failing (PMS hostname acme2.com):

    2019-03-01 12:32:56.185 [2b20.1a40]  I: ***  LOGGING STARTED  *** (UTC+5:30, session: 0x0)
    2019-03-01 12:32:56.612 [2b20.1a40]  I: PmpSelectorPlugin::PluginMain: Starting: '100\PmpSelectorPlugin'
    2019-03-01 12:32:56.614 [2b20.1a40]  I: ServerFinder::ServerFinder: Last known good server is {host: acme2.com, http: 80, https: 443}
    2019-03-01 12:32:56.644 [2b20.1a40]  I: `anonymous-namespace'::LoadPmsAddress: PMS address loaded from cosmos: {host: acme2.com, http: 80, https: 443}
    2019-03-01 12:32:56.653 [2b20.1a40] .W: ServerFinder::Ping: Ping to {host: acme2.com, http: 80, https: 443} aborted. There are no valid certificates
    2019-03-01 12:32:56.653 [2b20.1a40]  I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from acme2.com
    2019-03-01 12:32:59.070 [2b20.1a40] *E: UpdatablePmCertVerifier::RenewCertificates: Failed to download certificate bodies. AsyncSendRequest failed: 12007

    From the failed connection, the failure to connect is error 12007. Checking the Microsoft error-page:
     

    • https://docs.microsoft.com/en-us/windows/desktop/winhttp/error-messages

    Error 12007 translates to:

    ERROR_WINHTTP_NAME_NOT_RESOLVED
    12007
    The server name cannot be resolved.

    Additionally, you may run the Connectivity Tool to verify the current connectivity status to the Policy Manager Server. You can find this tool in the product settings window under Support > Tools, then click the Run connectivity tool button.