Product Troubleshooting WithSecure Business Suite

Warning message of "This installer version is going to be obsoleted at the end of year 2024" during the installation of Linux Security 64
Updating malware definitions on an isolated client using fsaua-update_32.exe fails with message ERROR:Update archive file is broken
Updating malware definitions on an isolated client using fsaua-update_32.exe fails with message ERROR:Update archive file is broken
Where can I find the key code for the latest version of my Business Suite software?
Error: "The keycode that you entered is not valid" when trying to export an installation package for Client Security or Server Security
"capricorn-linux64" channel are added in product's database after Linux Security 64 update version 12.0.482 and Atlant update version 1.0.319
How to schedule Business Suite Software Updater to install updates automatically to Client Security and Server Security devices?
f-secure-baseguard services gone for Linux Security 64 and Atlant after FSBG 1.0.907 update
How to hide the real-time scanning exclusions or other exclusions from users in the local Client Security or Server Security user interface?
WithSecure Client Security or Server Security Web content control is not blocking categories that are set as "Disallowed"

How to disable client fallback to the WithSecure update server from the Policy Manager?

Issue:

We are in an isolated intranet environment and our clients/servers are not connected to internet. We are facing an issue that in times Client Security and Server Security clients change the update server details from default Policy Manager server URL to guts2.sp.f-secure.com. As the clients are not connected to internet, the updates check fails.

Resolution:

To disable fallback to the WithSecure update server, follow these steps to disallow the hosts from falling back to the WithSecure update server if Policy Manager is inaccessible:

Log in to the Policy Manager Console
Select a host or a policy domain from the domain tree
Go to the Settings tab
Go to the Windows > Centralized Management settings page
Scroll down to the Automatic updates section and disable Allow falling back to WithSecure update server if Policy Manager Proxies are inaccessible
Distribute the policy (Ctrl + D)

Article no: 000027684