-
Host unable to connect to WithSecure Policy Manager Server after upgrading or installing WithSecure Client Security
Read more
Issue:
After upgrading or installing WithSecure Client Security/Server Security 16, you encounter issues with communication. Symptoms include:
- the host is unable to connect to WithSecure Policy Manager Server
- the host is not visible on the "Import host" list in WithSecure Policy Manager Console.
However, the hosts might be able to download updates.
Resolution:
Note: Make sure that the WithSecure Policy Manager Server address is correct and that the host communication ports (default: TCP 80 and 443) are listening.
Test the connectivity between the clients and Policy Manager:
- Try to connect to the WithSecure Policy Manager Server's address via a web browser from one of the hosts (http://pms-server.local:80 and https://pm-server.local:443). If the connection is set up correctly, you will receive a web page from the WithSecure Policy Manager Server indicating so. If there is no page loaded, check that the host communication ports to the Policy Manager Server are allowed in your firewall.
- Make sure that you have configured the WithSecure Policy Manager Server IP address and/or hostname correctly and that the ports configured for host modules are correct.
On the host running WithSecure Client Security/Server Security, the following log contains details on the connection status with the WithSecure Policy Manager Server. You can use it to troubleshoot connection issues:
C:\ProgramData\F-Secure\Log\BusinessSuite\PmpSelectorPlugin.log
Below is an example of a failed connection:
I: Connecting to wait.pmp-selector.local I: Update check failed, error=210 (unable to resolve host) I: Connection failed W: ServerFinder::Ping: Ping to {host: 10.10.10.10, http: 82, https: 443} aborted. There are no valid certificates I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from 10.10.10.10 E: UpdatablePmCertVerifier::RenewCertificates: Failed to download certificate bodies. AsyncSendRequest failed: 12002 W: CosmosUpdater::Run: No servers responded. Policy Manager unavailable.Error 12002 means ERROR_WINHTTP_TIMEOUT > Client Security/Server Security cannot connect to Policy Manager to fetch this list.
A complete list of Microsoft Windows HTTP Services errors is available here.Below is an example of a working connection:
I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from 10.11.10.10 I: UpdatablePmCertVerifier::RenewCertificates: 2 certificate(s) renewed successfully; expire in 86170 seconds
If you have confirmed the communication to work between the client computer and the Policy Manager Server, and you have made sure that the Policy Manager address and ports are configured correctly, make sure that the date and time are configured correctly on the client device.
If the date and time are incorrectly set, the certificate download from the Policy Manager Server will fail. The date and time can be easily incorrectly set in an offline environment, since the Network Time Protocol (NTP) can't be used to set the date and time.
Check the PmpSelectorPlugin.log again for the following:
W: ServerFinder::Ping: Ping aborted: there are no valid certificates I: UpdatablePmCertVerifier::RenewCertificates: Renewing certificates from 192.168.1.100:443 with HTTP proxy '' W: UpdatablePmCertVerifier::StoreCertificates: Certificates renewal yielded no fresh certificates
In the above example the client tries to download the certificate from the Policy Manager Server, but since the client's date and time are in the future compared to the Policy Manager Server, the client thinks no fresh certificate is available.
-
How can I configure or change the intermediate server failover time of a Client Security client?
Read more
Issue:
How to configure or change the default server failover time for clients to fetch the updates from the WithSecure Update Server when they are unable to reach the Policy Manager Server?
Resolution:
Changing the failover time requires the use of "advanced mode" in the Policy Manager Console:
- Open the Policy Manager Console
- Click on Tools > Preferences
- In the Appearance tab, enable Make advanced mode available for Settings and Status pages
- Click OK
Follow these steps to change the server failover time:
- Highlight a host or policy domain from the Domain Tree
- Go to the Settings tab and select 13.x and older hosts
- Navigate to F-Secure Automatic Update Agent > Settings > Communications > Intermediate Server failover time
- Change the time accordingly (default is 1 hour)
Note: Minimum is 1 hour, Maximum is 256 days.
-
Files detected as "Password Protected" when scanning them on Linux Security
Read more
Issue:
When I run the command fsav [path/file] the command returns "ERROR: Password protected file"
Resolution:
"Treat password-protected files as safe" setting on WEBUI has been disabled. This means that a message of "Password protected file" will be output every time such files are being scanned.
By default, the setting is enabled which means that any password protected files are considered to be safe and the scan result will always show as "clean". To revert;
- Login to WEBUI
- Click on "Advanced mode"
- Go to "Virus Protection" > "Real-time Scanning"
- Enable the "Treat password protected archives as safe" setting
- Click on the "Save" button at the right bottom of the page.
- For Manual Scans, go to "Virus Protection" > "Manual Scanning"
- Enable the "Treat password protected archives as safe"
- Click on "Save" button
-
Host module error http port 80 when trying to install Policy Manager
Read more
Issue:
Policy Manager and Server Security was installed on server, but had to be uninstalled and reinstalled due to power cut.
Reinstallation of Policy Manager failed due to host module error on http port 80
Resolution:
Check if port 80 is used by service by launching a web browser locally on the server. Open the following page:
- http://localhost
This will show the homepage of application currently running and hosted on port 80. This application is currently the reason for blocking the Policy Manager Server (re)installation.
To resolve the issue and to reinstall Policy Manager, several options are available and listed below in the order of preference.
1. Stop the service currently running on port 80. Consult the product documentation to understand how to do this. E.g. Microsoft webserver (IIS) using port 80 can be temporarily stopped b typing NET STOP HTTP in a command prompt.
2. Change the default port for the application running on port 80.Consult the product documentation to understand how to do this.
3. Reinstall Policy Manage server and during installation, select a different http port (e.g. 81). However, keep in mind that if you have existing end-points currently running for instance WithSecure Client Security or Server Security, they will no longer be able to contact the Policy Manager Server to download updates, until you distribute a policy with the correct http port (see screenshot). -
f-secure-baseguard services gone for Linux Security 64 and Atlant after FSBG 1.0.907 update
Read more
Issue:
F-Secure Baseguard services f-secure-baseguard-orspgw and f-secure-baseguard-update services are gone for Linux Security 64 and Atlant after FSBG 1.0.907 update.
Resolution:
This is an intended change for Linux Security 64 and Atlant from FSBG version 1.0.907 onwards. These services were removed since they are no longer required.
Details of these changes can be checked from change logs listed below:
New Linux Security 64 update has been released (2024-09-02)
https://community.withsecure.com/discussion/117646/linux-agent-ls64-changelog-elements-business-suite-standalone/p3
※LNX-299: Removed obsolete BaseGuard update service.New Atlant update has been released (2024-09-02)
https://community.withsecure.com/discussion/120778/atlant-changelog/p3
※LNX-299: Removed obsolete BaseGuard update service. -
Error: "The keycode that you entered is not valid" when trying to export an installation package for Client Security or Server Security
Read more
Issue:
When trying to create or export an installation package for Client Security or Server Security from the Policy Manager Console, the user receives the following error message when entering the license key: "The keycode that you entered is not valid"
Resolution:
As with earlier major versions of Client Security and Server Security, each major version of the installer uses a new license key. So for example, version 16 has a different license key compared to version 15, but version 16.00 and 16.01 use the same license key. Start by making sure that the license keys you are using do not belong to version an older version of the product. This can easily be verified by checking your license certificate.
If your license certificate lacks the keys for the latest versions of Client Security and Server Security, you can request an updated license certificate from your WithSecure reseller partner or WithSecure sales contact.
-
Error 2755 upon Windows Business Suite product installation
Read more
Issue:
We are getting error "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755." during the Business Suite Client Security or Server Security installation.
For example:
Resolution:
The error 2755 means that Windows cannot open the files or lacks the proper permissions. Most likely it could be related to privileges on the system. Verify the user installation permission in Group Policy for the system.
This is an expected error when the WithSecure .msi installer is executed with User Account Control (UAC) enabled.
With the UAC enabled by default, even the administrator user is restricted until you click the elevation prompt during installation, but using an MSI installer does not have the possibility to elevation prompt. You are required to run the MSI installation with a built-in administrator rights account or with UAC disabled.
If you come across this error using a domain administrator account, proceed to install using your local administrator account instead.
Sometimes, you may right-click on the installer and select "Run as administrator". This would also help to workaround the issue. Alternatively, you can start the command line window in elevated mode, and run the MSI installer from there.
We also recommend ensuring the system has all Windows updates in place before installing our product.
-
Error: "The Host Module HTTPS port number specified is already in use." when installing WithSecure Policy Manager Server
Read more
Issue:
When installing WithSecure Policy Manager Server or Policy Manager Proxy the user receives the following error after clicking Next on the Configure ports page:
Error: "The Host Module HTTPS port number specified is already in use."
Resolution:
If the port you have chosen for WithSecure Policy Manager Server or Policy Manager Proxy communication is in use by other services (e.g Microsoft webserver), thus causing a conflict, you can solve the issue by changing the port Policy Manager Server will use or by deactivating the service causing the conflict or changing the port that service is using.
Policy Manager Proxy Upgrade
The error could be caused if clients are currently accessing the Policy Manager Proxy. If you are performing an upgrade of Policy Manager Proxy, you can stop all Policy Manager Proxy services and try the upgrade again, then it should work and the upgrade will be completed. -
Emails to external recipients sent from software not encrypted by MSG
Read more
Issue:
A software in our environment sends out regular emails to internal and external recipients. A tag is added to the subject line to have these messages encrypted by MSG.
Only the messages intended for internal recipients are being encrypted, all messages from the software to external recipients arrive unencrypted.Resolution:
Start by verifying that these messages are being routed through the MSG-appliance. It is possible that the software has different routing rules based on domains and that the external traffic isn't routed to the MSG-appliance at all.
In MSG, you can check the details of a message using Smart Search:
- Log in to the MSG Web UI
- Make sure the System-tab is selected at the top
- On the left-hand menu, navigate down to Smart Search-> Search
- Use the sender and/or recipient information to search for the message. Do note that the Time-field usually is set to Last 24 Hours, which might be too restrictive, so expanding it to for example Last 7 Days is recommended.
- If you find messages, you can verify their encryption status by checking the envelope symbol at the left of the message row. If it has a small lock on it, the message is encrypted.
- Expand the message info by clicking the small + next to the envelope symbol to see more details. Here the Encryption-field should also be set to Proofpoint Encryption/Secure Reader Encrypted if the message is encrypted.
If you find messages that should be encrypted but aren't, open a support ticket so that it can be investigated. Provide the appliance-ID and information about the messages so that we can identify them (sender/recipient info, time when it was sent, subject field text). A sample message saved as .eml or .msg is also useful.
To ensure that we can help you efficiently, please make sure that the following IP-addresses can access the MSG-appliance on ports 22 and 10000:
203.112.232.170 F-Secure Support / Kuala Lumpur
193.110.108.33 F-Secure Support / HTC Helsinki
208.86.202.10 Proofpoint
208.84.66.21 Proofpoint
208.84.67.21 Proofpoint -
Does Policy Manager support Windows Management Instrumentation (WMI) Integration?
Read more
Issue:
Windows Management Instrumentation (WMI) Integration with Policy Manager for Windows
Resolution:
Policy Manager supports Windows Management Instrumentation (WMI) Integration. See this user guide for more information: https://www.withsecure.com/userguides/product.html#business/policy-manager/16.00/en/concept_E55FFF0187A54B79B30637C7983BDCC8-16.00-en