How to install an WithSecure Client Security or Server Security as stand-alone, so that it downloads the updates directly from the WithSecure Update Server, without trying to download them from the WithSecure Policy Manager Server?
During the MSI installer exporting process, you can choose the initial policy, which will be the policy included in the installer. After installation, the client will start to use the settings from that policy immediately. Since the WithSecure Client Security or Server Security will be installed as stand-alone, the MSI installer must be given an initial policy that allows the client to fallback to the WithSecure Update Server if the WithSecurePolicy Manager Server is unreachable.
You can create a new policy domain in the domain tree for the policy which you will then include as the initial policy in the installer:
- Right-click an existing policy domain in the domain tree
- Click New policy domain
- Enter the domain a name
- Select the newly created policy domain from the domain tree
- Go to the Settings tab
- Go to the Centralized Management settings page
- Scroll down to the Automatic updates section and enable Allow falling back to WithSecure update server if Policy Manager Proxies are inaccessible
- Distribute the policy (Ctrl + D)
After exporting the MSI installer, run it on a host. The Client Security or Server Security installation will still try to first download the updates from the WithSecure Policy Manager Server, but after failing to download the updates for a few hours, the client will fallback to using the WithSecure Update Server to download the malware definition updates.
If the host client is in an isolated environment with no access to the WithSecure Update Server, you can find the instructions how to update malware definitions on isolated Client Security and Server Security hosts here: https://www.withsecure.com/userguides/product.html#business/policy-manager/16.00/en/concept_8AE300FF20744C2882DFBB00D3E6E426-16.00-en
Article no: 000019091