Special considerations for migrating high-load servers

On high-load servers, it is important to monitor performance and avoid faults. After migration to Kaspersky Endpoint Security for Windows, we recommend temporarily disabling application components that use substantial server resources relative to other components. After you make sure that the server is performing as normal, you can turn the application components back on.

We recommend migrating high-load servers as follows:

  1. Create a Kaspersky Endpoint Security policy with default settings.

    Default settings are considered optimal. This settings are recommended by Kaspersky experts. Default settings provide recommended protection level and optimal resource use.

  2. In policy settings, turn off the following components: Network Threat Protection, Behavior Detection, Exploit Prevention, Remediation Engine, Application Control.

    If your organization has the Kaspersky Managed Detection and Response (MDR) solution deployed, upload the BLOB configuration file to the Kaspersky Endpoint Security policy.

  3. Remove Kaspersky Security for Windows Server from the server.
  4. Install Kaspersky Endpoint Security for Windows with the default set of components.

    If your organization has Detection and Response solutions deployed, select the relevant components in the properties of the installation package.

    If your organization has the Kaspersky Anti Targeted Attack Platform (KATA EDR) solution deployed, select the Integration with Kaspersky Anti Targeted Attack Platform component in installation package properties. To support KATA EDR, the server must have the Kaspersky Endpoint Agent application installed.

  5. Check the settings of the application:
    • The application is activated with the KSWS license key.
    • The new policy is applied. Previously selected components are disabled.
  6. Make sure the server is working. Make sure that Kaspersky Endpoint Security for Windows is not using more than 1% of the server's resources.
  7. If necessary, create scan exclusions, add trusted applications, create a list of trusted web addresses.
  8. Turn on Behavior Detection, Exploit Prevention, Remediation Engine components. Make sure that Kaspersky Endpoint Security for Windows is not using more than 1% of the server's resources.
  9. Turn on the Network Threat Protection component. Make sure that Kaspersky Endpoint Security for Windows is not using more than 2% of the server's resources.
  10. Turn on the Application Control component in rule testing mode.
  11. Make sure Application Control is working. If necessary, add new Application Control rules and turn off rule testing mode after confirming that Application Control is working.

After migrating from KSWS to KES, make sure that the application is operating correctly. Check the status of the server in the console (should be OK). Make sure no errors are reported for the application, also check the time of the last connection to the Administration Server, the time of the last database update and the server protection status.

Page top