Issue:

How to change the time limit for Client Security and Server Security how quickly they consider the malware definition and engine updates (databases) to be old or very old? 

For example, if we have Client Security or Server Security installed in an isolated or offline environment, we do not want to have the user interface warning of old or very old databases as quickly. 

Resolution:

The time limit in days for how quickly a Client Security or Server Security client considers update databases to be old can be changed from the Policy Manager policy settings:

1. Log in to the Policy Manager Console
2. Select a host or policy domain from the domain tree
3. Open the Settings tab
4. Navigate to Windows > Centralized management 
5. In the Automatic updates section, modify the days value for:
   1. Time limit for considering update databases old (in days)
   2. Time limit for considering update databases very old (in days)
6. Distribute the policy (Ctrl + D)

The default value for old is 7 days, while the default value for very old is 30 days. 

Issue:

How to change the customer number (ID) of a Policy Manager Server? We want to change the customer number which we entered during the first time login to the Policy Manager Console to an another customer number. 

Resolution:

The customer number that a Policy Manager Server uses can be changed from Policy Manager Console:

1. Log in to the Policy Manager Console
2. Navigate to Help > Registration from the menu at the top of the window
3. Enter the new customer number in the "Your customer number" field
4. Click OK

Issue:

If by any reason a scheduled scan is missed by Business Suite Client Security or Server Security, for example if computer has been shut down or in sleep mode, will the scan be ran / launched after the computer has been turned on again?  

Resolution:

If by any reason a Scheduled scan by Client Security or Server Security is missed, then it will only run the scheduled scan the next time when its configured to run and not when the computer or server is turned on. 

For example, if scheduled scan is configured to run daily at 08:00, it will only run it at 8:00 and not any other time. 

Issue:

How to configure Linux Security 64 firewall?

Resolution:

Linux Security 64 doesn't have any firewall features, so the firewall would have to be configured using some other application.

Issue:

After deploying Atlant on a Linux host we are unable to activate / validate the subscription key. We get the following errors: 

/var/log/messages-20220116:Jan 13 01:00:31 normand doormand: Request received to set default registration to non-existing registration.
/var/log/messages-20220116:Jan 13 01:00:31 normand doormand: Registration attempt failed: Subscription key was not found from Fate url https://provisioning.ew1.entitlements.fsapi.com/cpa/v1/registration: Type: NotFound, Description: Subscription was not found (140401)

Resolution:

There are two different license keycodes for Atlant. One license keycode is to export the installation package on the Policy Manager Console and the other is to enable the Offload scanning services of Atlant for the clients. 

In order to export the installation package successfully, you need to use the "Policy Manager managed installation" Atlant installer keycode which is indicated in the license certificate. After exporting the installer from the Policy Manager Console you can run the installer on a Linux server. No additional activation is required. 

As for the Atlant Premium keycode, to set up Atlant for use as a replacement for Scanning and Reputation Server, you need to configure it in Policy Manager Console to handle the offloaded requests from virtual desktops and servers.

1. Log in to the Policy Manager Console
2. Select the root
3. Open the Settings tab
4. Navigate to Virtual security > Offload Scanning Agent
5. Enable Offload file scanning and enter the address for your Atlant host
6. Navigate to Virtual security > Atlant scanning service 
7. In the Atlant subscription section, enter the Atlant for Offload Scanning (premium) subscription key in the Subscription key field to enable the premium services of Atlant.
8. Configure the General settings and time out values as needed
9. Under Endpoints: 
   • Click Add if you want add more ICAP service endpoints.
   • Select any of the entries and click Edit if you need to change the address or port for the endpoint.
   • Note: By default, Policy Manager creates a single ICAP scanning endpoint that uses the address 0.0.0.0 and port 1344.
10. Distribute the policy (Ctrl + D)

Configuring Atlant for virtual environments | Atlant | Latest | WithSecure User Guides  

Issue:

I am getting an invalid keycode error when using a license keycode of Atlant Premium to export the installation package on Policy Manager Console

Resolution:

There are two different license keycodes needed for Atlant installation on a Linux server in the Policy Manager managed mode. One license keycode is to export the installation package on Policy Manager Console and the other is to enable the premium services of Atlant.

In order to export the installation package successfully, you need to use the Policy Manager Atlant installer activation keycode which is indicated in the license certificate.

As for the Atlant Premium keycode, you can enter it for the devices by following these steps:

1. Log in to the Policy Manager Console
2. Select a host or policy domain from the domain tree
3. Open the Settings tab
4. Navigate to Virtual security > Atlant scanning service 
5. In the Atlant subscription section, enter the Atlant premium in the Subscription key  field to enable the premium services of Atlant.

Issue:

Is it possible to install Business Suite Client Security on a Windows laptop or tablet where the processor (CPU) is ARM based? 

Resolution:

Client Security does not support installation on Windows computers with ARM processors: System requirements | Client Security for Windows | 16.00 | WithSecure User Guides

ARM based Windows are supported by Elements Endpoint Protection Agent, so you can migrate from Business Suite subscription to a Elements Endpoint Protection for Computers subscription if you need to have protection for your ARM based Windows devices. 

Issue:

How to locally turn off or disable firewall temporarily for a Client Security Windows host computer? 

Resolution:

First make sure the firewall setting is not locked 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. Go to the Firewall settings page
5. Disable the lock for the setting called Enable Windows firewall
6. Distribute the policy (Ctrl + D)

Now the user will be able to disable the firewall temporarily from theClient Security settings if they have administrator rights:

1. Open the Client Security user interface on the device
2. Click on the cogwheel icon to go to Settings
3. Go to the Firewall settings page
4. Click on the Turn off firewall temporarily button
5. Select the amount of time the firewall should be turned off and click Turn off

This will turn of the Windows Firewall and not just the WithSecure firewall profile. If you would only want to disable the WithSecure firewall rules, you can either assign a policy which does not have the Enable firewall configuration through Policy Manager setting in use, or you can turn off all security features. Turning off all security features also removes the WithSecure firewall profile temporarily.  

Issue:

How to lock / force Client Security or Server Security firewall profile so that a local user cannot change it from the local user interface even if the user has administrator privileges? 

Resolution:

You can force a user to use a specific firewall profile by following these steps:

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 Firewall settings page
5. In the General section, click on the Lock on the right side of Workstation host profile or Server host profile
6. Distribute the policy (Ctrl + D)

Once the policy has been taken into use, the firewall profile selection drop-down menu will be grayed out and a local user cannot change the profile from the one pre-selected by the admin. 

If you only want to hide specific firewall profiles from the local user interface, you can add them to the Hidden firewall profiles 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 Firewall settings page
5. Scroll down to the Changing profiles section and click the Hide profiles from users link
6. Click Add
7. Select the profile you want to hide and click OK 
8. Click Close
9. Distribute the policy (Ctrl + D)

Now the hidden firewall profile isn't visible or shown to the local user. 

Issue:

Can Software Updater update software on isolated Client Security and Server Security hosts?

Resolution:

By default Software Updater on Client Security and Server Security host devices tries to download the Software Updater patches from the Policy Manager Server, so if the devices are isolated, they will still be able to download and install Software Updater updates. Policy Manager itself will download the Software Updater patches from the vendor's sites and then distribute the patches to the clients. 

To make sure that Client Security and Server Security will download the updates from the Policy Manager Server, follow these steps:

1. Log in to the Policy Manager Console 
2. Select a host or policy domain from the domain tree
3. Open the Settings tab
4. Navigate to the Windows > Software updater settings page
5. Make sure the form the Download software updates from Policy Manager drop-down menu you have If possible selected
6. Distribute the policy (Ctrl + D)