Kaspersky Security Center 13.1
[Topic 180963]

Scenario: Regular updating Kaspersky databases and applications

This section provides a scenario for regular updating of Kaspersky databases, software modules, and applications. After you complete the Configuring network protection scenario, you must maintain the reliability of the protection system to make sure that the Administration Servers and managed devices are kept protected against various threats, including viruses, network attacks, and phishing attacks.

Network protection is kept up-to-date by regular updates of the following:

  • Kaspersky databases and software modules
  • Installed Kaspersky applications, including Kaspersky Security Center components and security applications

When you complete this scenario, you can be sure of the following:

  • Your network is protected by the most recent Kaspersky software, including Kaspersky Security Center components and security applications.
  • The anti-virus databases and other Kaspersky databases critical for the network safety are always up-to-date.

Prerequisites

The managed devices must have a connection to the Administration Server. If they do not have a connection, consider updating Kaspersky databases, software modules, and applications manually or directly from the Kaspersky update servers.

Administration Server must have a connection to the internet.

Before you start, make sure that you have done the following:

  1. Deployed the Kaspersky security applications to the managed devices according to the scenario of deploying Kaspersky applications through Kaspersky Security Center 13.1 Web Console.
  2. Created and configured all required policies, policy profiles, and tasks according to the scenario of configuring network protection.
  3. Assigned an appropriate amount of distribution points in accordance with the number of managed devices and the network topology.

Updating Kaspersky databases and applications proceeds in stages:

  1. Choosing an update scheme

    There are several schemes that you can use to install updates to Kaspersky Security Center components and security applications. Choose the scheme or several schemes that meet the requirements of your network best.

  2. Creating the task for downloading updates to the repository of the Administration Server

    This task is created automatically by Kaspersky Security Center Quick Start Wizard. If you did not run the Wizard, create the task now.

    This task is required to download updates from Kaspersky update servers to the repository of the Administration Server, as well as to update Kaspersky databases and software modules for Kaspersky Security Center. After the updates are downloaded, they can be propagated to the managed devices.

    If your network has assigned distribution points, the updates are automatically downloaded from the Administration Server repository to the repositories of the distribution points. In this case the managed devices included in the scope of a distribution point download the updates from the repository of the distribution point instead of the Administration Server repository.

    How-to instructions:

    or

  3. Creating the task for downloading updates to the repositories of distribution points (optional)

    By default, the updates are downloaded to the distribution points from the Administration server. You can configure Kaspersky Security Center to download the updates to the distribution points directly from Kaspersky update servers. Download to the repositories of distribution points is preferable if the traffic between the Administration Server and the distribution points is more expensive than the traffic between the distribution points and Kaspersky update servers, or if your Administration Server does not have internet access.

    When your network has assigned distribution points and the Download updates to the repositories of distribution points task is created, the distribution points download updates from Kaspersky update servers, and not from the Administration Server repository.

    How-to instructions:

    or

  4. Configuring distribution points

    When your network has assigned distribution points, make sure that the Deploy updates option is enabled in the properties of all required distribution points. When this option is disabled for a distribution point, the devices included in the scope of the distribution point download updates from the repository of the Administration Server.

    If you want the managed devices to receive updates only from the distribution points, enable the Distribute files through distribution points only option in the Network Agent policy.

  5. Optimizing the update process by using the offline model of update download or diff files (optional)

    You can optimize the update process by using the offline model of update download (enabled by default) or by using diff files. For each network segment, you have to choose which of these two features to enable, because they cannot work simultaneously.

    When the offline model of update download is enabled, Network Agent downloads the required updates to the managed device once the updates are downloaded to the Administration Server repository, before the security application requests the updates. This enhances the reliability of the update process. To use this feature, enable the Download updates and anti-virus databases from the Administration Server in advance option in the Network Agent policy.

    If you do not use the offline model of update download, you can optimize traffic between the Administration Server and the managed devices by using diff files. When this feature is enabled, the Administration Server or a distribution point downloads diff files instead of entire files of Kaspersky databases or software modules. A diff file describes the differences between two versions of a file of a database or software module. Therefore, a diff file occupies less space than an entire file. This results in decrease in the traffic between the Administration Server or distribution points and the managed devices. To use this feature, enable the Download diff files option in the properties of the Download updates to the Administration Server repository task and/or the Download updates to the repositories of distribution points task.

    How-to instructions:

    or

  6. Verifying downloaded updates (optional)

    Before installing the downloaded updates, you can verify the updates through the Update verification task. This task sequentially runs the device update tasks and virus scan tasks configured through settings for the specified collection of test devices. Upon obtaining the task results, the Administration Server starts or blocks the update propagation to the remaining devices.

    The Update verification task can be performed as part of the Download updates to the repository of the Administration Server task. In the properties of the Download updates to the repository of the Administration Server task, enable the Verify updates before distributing option in the Administration Console or the Run update verification option in Kaspersky Security Center 13.1 Web Console.

    How-to instructions:

    or

  7. Approving and declining software updates

    By default, the downloaded software updates have the Undefined status. You can change the status to Approved or Declined. The approved updates are always installed. If an update requires reviewing and accepting the terms of the End User License Agreement, then you first need to accept the terms. After that the update can be propagated to the managed devices. The undefined updates can only be installed on Network Agent and other Kaspersky Security Center components in accordance with the Network Agent policy settings. The updates for which you set Declined status will not be installed on devices. If a declined update for a security application was previously installed, Kaspersky Security Center will try to uninstall the update from all devices. Updates for Kaspersky Security Center components cannot be uninstalled.

    How-to instructions:

    or

  8. Configuring automatic installation of updates and patches for Kaspersky Security Center components

    Starting from version 10 Service Pack 2, the downloaded updates and patches for Network Agent and other Kaspersky Security Center components are installed automatically. If you have left the Automatically install applicable updates and patches for components that have the Undefined status option enabled in the Network Agent properties, then all updates will be installed automatically after they are downloaded to the repository (or several repositories). If this option is disabled, Kaspersky patches that have been downloaded and tagged with the Undefined status will be installed only after you change their status to Approved.

    For Network Agent versions earlier than 10 Service Pack 2, make sure that the Update Network Agent modules option is enabled in the properties of the Download updates to the repository of the Administration Server task or the Download updates to the repositories of distribution points task.

    How-to instructions:

    or

  9. Installation of updates for the Administration Server

    Software updates for the Administration Server do not depend on the update statuses. They are not installed automatically and must be preliminarily approved by the administrator on the Monitoring tab in the Administration Console (Administration Server <server name>Monitoring) or on the NOTIFICATIONS section in Kaspersky Security Center 13.1 Web Console (MONITORING & REPORTINGNOTIFICATIONS). After that, the administrator must explicitly run installation of the updates.

  10. Configuring automatic installation of updates for the security applications

    Create the Update tasks for the managed applications to provide timely updates to the applications, software modules and Kaspersky databases, including anti-virus databases. To ensure timely updates, we recommend that you select the When new updates are downloaded to the repository option when configuring the task schedule.

    By default, updates for Kaspersky Endpoint Security for Windows and Kaspersky Endpoint Security for Linux are installed only after you change the update status to Approved. You can change the update settings in the Update task.

    If an update requires reviewing and accepting the terms of the End User License Agreement, then you first need to accept the terms. After that the update can be propagated to the managed devices.

    How-to instructions:

    or

Results

Upon completion of the scenario, Kaspersky Security Center is configured to update Kaspersky databases and installed Kaspersky applications after the updates are downloaded to the repository of the Administration Server or to the repositories of distribution points. You can then proceed to monitoring the network status.

See also:

Scenario: Configuring network protection

Page top
[Topic 180689_1]

About updating Kaspersky databases, software modules, and applications

To be sure that the protection of your Administration Servers and managed devices is up-to-date, you must provide timely updates of the following:

  • Kaspersky databases and software modules
  • Installed Kaspersky applications, including Kaspersky Security Center components and security applications

Depending on the configuration of your network, you can use the following schemes of downloading and distributing the required updates to the managed devices:

  • By using a single task: Download updates to the Administration Server repository
  • By using two tasks:
    • The Download updates to the Administration Server repository task
    • The Download updates to the repositories of distribution points task
  • Manually through a local folder, a shared folder, or an FTP server
  • Directly from Kaspersky update servers to Kaspersky Endpoint Security on the managed devices

Using the Download updates to the Administration Server repository task

In this scheme, Kaspersky Security Center downloads updates through the Download updates to the Administration Server repository task. In small networks that contain less than 300 managed devices in a single network segment or less than 10 managed devices in each network segment, the updates are distributed to the managed devices directly from the Administration Server repository (see figure below).

Updating by using the Download updates to the Administration Server repository task without distribution points

By default, the Administration Server communicates with Kaspersky update servers and downloads updates by using the HTTPS protocol. You can configure the Administration Server to use the HTTP protocol instead of HTTPS.

If your network contains more than 300 managed devices in a single network segment or if your network consists of several network segments with more than 9 managed devices in each network segment, we recommend that you use distribution points to propagate the updates to the managed devices (see figure below). Distribution points reduce the load on the Administration Server and optimize traffic between the Administration Server and the managed devices. You can calculate the number and configuration of distribution points required for your network.

In this scheme, the updates are automatically downloaded from the Administration Server repository to the repositories of the distribution points. The managed devices included in the scope of a distribution point download the updates from the repository of the distribution point instead of the Administration Server repository.

Updating by using the Download updates to the Administration Server repository task with distribution points

When the Download updates to the Administration Server repository task is complete, the following updates are downloaded to the Administration Server repository:

  • Kaspersky databases and software modules for Kaspersky Security Center

    These updates are installed automatically.

  • Kaspersky databases and software modules for the security applications on the managed devices

    These updates are installed through the Update task for Kaspersky Endpoint Security for Windows.

  • Updates for the Administration Server

    These updates are not installed automatically. The administrator must explicitly approve and run installation of the updates.

    Local administrator rights are required for installing patches on the Administration Server.

  • Updates for the components of Kaspersky Security Center

    By default, these updates are installed automatically. You can change the settings in the Network Agent policy.

  • Updates for the security applications

    By default, Kaspersky Endpoint Security for Windows installs only those updates that you approve. (You can approve updates via the Administration Console or via Kaspersky Security Center 13.1 Web Console). The updates are installed through the Update task and can be configured in the properties of this task.

The Download updates to the repository of the Administration Server task is not available on virtual Administration Servers. The repository of the virtual Administration Server displays updates downloaded to the primary Administration Server.

You can configure the updates to be verified for operability and errors on a set of test devices. If the verification is successful, the updates are distributed to other managed devices.

Each Kaspersky application requests required updates from Administration Server. Administration Server aggregates these requests and downloads only those updates that are requested by any application. This ensures that the same updates are not downloaded multiple times and that unnecessary updates are not downloaded at all. When running the Download updates to the Administration Server repository task, Administration Server sends the following information to Kaspersky update servers automatically in order to ensure the downloading of relevant versions of Kaspersky databases and software modules:

  • Application ID and version
  • Application installation ID
  • Active key ID
  • Download updates to the repository of the Administration Server task run ID

None of the transmitted information contains personal or other confidential data. AO Kaspersky Lab protects information in accordance with requirements established by law.

Using two tasks: the Download updates to the Administration Server repository task and the Download updates to the repositories of distribution points task

You can download updates to the repositories of distribution points directly from the Kaspersky update servers instead of the Administration Server repository, and then distribute the updates to the managed devices (see figure below). Download to the repositories of distribution points is preferable if the traffic between the Administration Server and the distribution points is more expensive than the traffic between the distribution points and Kaspersky update servers, or if your Administration Server does not have internet access.

Updating by using the Download updates to the Administration Server repository task and the Download updates to the repositories of distribution points task

By default, the Administration Server and distribution points communicate with Kaspersky update servers and download updates by using the HTTPS protocol. You can configure the Administration Server and/or distribution points to use the HTTP protocol instead of HTTPS.

To implement this scheme, create the Download updates to the repositories of distribution points task in addition to the Download updates to the Administration Server repository task. After that the distribution points will download updates from Kaspersky update servers, and not from the Administration Server repository.

Distribution point devices running macOS cannot download updates from Kaspersky update servers.

If one or more devices running macOS are within the scope of the Download updates to the repositories of distribution points task, the task completes with the Failed status, even if it has successfully completed on all Windows devices.

The Download updates to the Administration Server repository task is also required for this scheme, because this task is used to download Kaspersky databases and software modules for Kaspersky Security Center.

Manually through a local folder, a shared folder, or an FTP server

If the client devices do not have a connection to the Administration Server, you can use a local folder or a shared resource as a source for updating Kaspersky databases, software modules, and applications. In this scheme, you need to copy required updates from the Administration Server repository to a removable drive, then copy the updates to the local folder or the shared resource specified as an update source in the settings of Kaspersky Endpoint Security (see figure below).

Updating through a local folder, a shared folder, or an FTP server

For more information about sources of updates in Kaspersky Endpoint Security, see the following Helps:

Directly from Kaspersky update servers to Kaspersky Endpoint Security on the managed devices

On the managed devices, you can configure Kaspersky Endpoint Security to receive updates directly from Kaspersky update servers (see figure below).

Updating security applications directly from Kaspersky update servers

In this scheme, the security application does not use the repositories provided by Kaspersky Security Center. To receive updates directly from Kaspersky update servers, specify Kaspersky update servers as an update source in the interface of the security application. For more information about these settings, see the following Helps:

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 46875_1]

Creating the Download updates to the Administration Server repository task

Expand all | Collapse all

The Download updates to the Administration Server repository task of the Administration Server is created automatically by the Kaspersky Security Center Quick Start Wizard. You can create only one Download updates to the Administration Server repository task. Therefore, you can create a Download updates to the Administration Server repository task only if this task was removed from the Administration Server tasks list.

This task is required to download updates from Kaspersky update servers to the repository of the Administration Server. The list of updates includes:

  • Updates to databases and software modules for Administration Server
  • Updates to databases and software modules for Kaspersky security applications
  • Updates to Kaspersky Security Center components
  • Updates to Kaspersky security applications

After the updates are downloaded, they can be propagated to the managed devices.

Before distributing updates to the managed devices, you can run the Update verification task. This allows you to make sure that Administration Server will install the downloaded updates properly and a security level will not decrease because of the updates. To verify them before distributing, configure the Run update verification option in the Download updates to the Administration Server repository task settings.

To create the Download updates to the Administration Server repository task:

  1. In the main menu, go to DEVICES → TASKS.
  2. Click Add.

    The Add Task Wizard starts. Follow the steps of the Wizard.

  3. For the Kaspersky Security Center application, select the Download updates to the Administration Server repository task type.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. If you want to modify the default task settings, enable the Open task details when creation is complete option on the Finish task creation page. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  6. Click the Create button.

    The task is created and displayed in the list of tasks.

  7. Click the name of the created task to open the task properties window.
  8. In the task properties window, on the Application settings tab, specify the following settings:
    • Sources of updates

      The following resources can be used as a source of updates for the Administration Server:

      • Kaspersky update servers

        HTTP(S) servers at Kaspersky from which Kaspersky applications download database and application module updates. By default, the Administration Server communicates with Kaspersky update servers and downloads updates by using the HTTPS protocol. You can configure the Administration Server to use the HTTP protocol instead of HTTPS.

        Selected by default.

      • Primary Administration Server

        This resource applies to tasks created for a secondary or virtual Administration Server.

      • Local or network folder

        A local or network folder that contains the latest updates. A network folder can be an FTP or HTTP server, or an SMB share. When selecting a local folder, you must specify a folder on the device that has Administration Server installed.

        An FTP or HTTP server or a network folder used by an update source must contain a folders structure (with updates) that matches the structure created when using Kaspersky update servers.

    • Content of updates:
    • Other settings:
      • Force update of secondary Administration Servers

        If this option is enabled, the Administration Server starts the update tasks on the secondary Administration Servers as soon as new updates are downloaded. Otherwise, the update tasks on the secondary Administration Servers start according to their schedules.

        By default, this option is disabled.

      • Copy downloaded updates to additional folders

        After the Administration Server receives updates, it copies them to the specified folders. Use this option if you want to manually manage the distribution of updates on your network.

        For example, you may want to use this option in the following situation: the network of your organization consists of several independent subnets, and devices from each of the subnets do not have access to other subnets. However devices in all of the subnets have access to a common network share. In this case, you set Administration Server in one of the subnets to download updates from Kaspersky update servers, enable this option, and then specify this network share. In downloaded updates to the repository tasks for other Administration Servers, specify the same network share as the update source.

        By default, this option is disabled.

      • Do not force updating of devices and secondary Administration Servers unless copying is complete

        The tasks of downloading updates to client devices and secondary Administration Servers start only after those updates are copied from the main update folder to additional update folders.

        This option must be enabled if client devices and secondary Administration Servers download updates from additional network folders.

        By default, this option is disabled.

      • Update Network Agent modules (for Network Agent versions earlier than 10 Service Pack 2)

        If this option is enabled, updates for software modules of Network Agent are installed automatically after the Administration Server completes the download updates to the repository task. Otherwise, updates received for Network Agent modules can be installed manually.

        This option is only applicable to Network Agent versions earlier than 10 Service Pack 2. Starting from version 10 Service Pack 2, Network Agents are updated automatically.

        By default, this option is enabled.

    • Run update verification:
      • Run update verification

        Administration Server downloads updates from the source, saves them to a temporary repository, and runs the task defined in the Update verification task field. If the task completes successfully, the updates are copied from the temporary repository to a shared folder on the Administration Server and then distributed to all devices for which the Administration Server acts as the source of updates (tasks with the When new updates are downloaded to the repository schedule type are started). The task of downloading updates to the repository is finished only after completion of the Update verification task.

        By default, this option is disabled.

  9. In the task properties window, on the Schedule tab, create a schedule for task start. If necessary, specify the following settings:
    • Scheduled start:

      Select the schedule according to which the task runs, and configure the selected schedule.

      • Manually (selected by default)

        The task does not run automatically. You can only start it manually.

        By default, this option is enabled.

      • Every N minutes

        The task runs regularly, with the specified interval in minutes, starting from the specified time on the day that the task is created.

        By default, the task runs every 30 minutes, starting from the current system time.

      • Every N hours

        The task runs regularly, with the specified interval in hours, starting from the specified date and time.

        By default, the task runs every six hours, starting from the current system date and time.

      • Every N days

        The task runs regularly, with the specified interval in days. Additionally, you can specify a date and time of the first task run. These additional options become available, if they are supported by the application for which you create the task.

        By default, the task runs every day, starting from the current system date and time.

      • Every N weeks

        The task runs regularly, with the specified interval in weeks, on the specified day of week and at the specified time.

        By default, the task runs every Monday at the current system time.

      • Daily (daylight saving time is not supported)

        The task runs regularly, with the specified interval in days. This schedule does not support observance of daylight saving time (DST). It means that when clocks jump one hour forward or backward at the beginning or ending of DST, the actual task start time does not change.

        We do not recommend that you use this schedule. It is needed for backward compatibility of Kaspersky Security Center.

        By default, the task starts every day at the current system time.

      • Weekly

        The task runs every week on the specified day and at the specified time.

      • By days of week

        The task runs regularly, on the specified days of week, at the specified time.

        By default, the task runs every Friday at 6:00:00 PM.

      • Monthly

        The task runs regularly, on the specified day of the month, at the specified time.

        In months that lack the specified day, the task runs on the last day.

        By default, the task runs on the first day of each month, at the current system time.

      • Every month on specified days of selected weeks

        The task runs regularly, on the specified days of each month, at the specified time.

        By default, no days of month are selected; the default start time is 6:00:00 PM.

      • On virus outbreak

        The task runs after a Virus outbreak event occurs. Select application types that will monitor virus outbreaks. The following application types are available:

        • Anti-virus for workstations and file servers
        • Anti-virus for perimeter defense
        • Anti-virus for mail systems

        By default, all application types are selected.

        You may want to run different tasks depending on the anti-virus application type that reports a virus outbreak. In this case, remove the selection of the application types that you do not need.

      • On completing another task

        The current task starts after another task completes. You can select how the previous task must complete (successfully or with error) to trigger the start of the current task. For example, you may want to run the Manage devices task with the Turn on the device option and, after it completes, run the Virus scan task.

    • Run missed tasks

      This option determines the behavior of a task if a client device is not visible on the network when the task is about to start.

      If this option is enabled, the system attempts to start the task the next time the Kaspersky application is run on the client device. If the task schedule is Manually, Once or Immediately, the task is started immediately after the device becomes visible on the network or immediately after the device is included in the task scope.

      If this option is disabled, only scheduled tasks run on client devices; for Manually, Once and Immediately, tasks run only on those client devices that are visible on the network. For example, you may want to disable this option for a resource-consuming task that you want to run only outside of business hours.

      By default, this option is enabled.

    • Use automatically randomized delay for task starts

      If this option is enabled, the task is started on client devices randomly within a specified time interval, that is, distributed task start. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      The distributed start time is calculated automatically when a task is created, depending on the number of client devices to which the task is assigned. Later, the task is always started on the calculated start time. However, when task settings are edited or the task is started manually, the calculated value of the task start time changes.

      If this option is disabled, the task starts on client devices according to the schedule.

    • Use randomized delay for task starts within an interval of (min)

      If this option is enabled, the task is started on client devices randomly within the specified time interval. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      If this option is disabled, the task starts on client devices according to the schedule.

      By default, this option is disabled. The default time interval is one minute.

    • Stop task if it has been running longer than (min)

      After the specified time period expires, the task is stopped automatically, whether it is completed or not.

      Enable this option if you want to interrupt (or stop) tasks that take too long to execute.

      By default, this option is disabled. The default task execution time is 120 minutes.

  10. Click the Save button.

The task is created and configured.

When Administration Server performs the Download updates to the Administration Server repository task, updates to databases and software modules are downloaded from the updates source and stored in the shared folder of Administration Server. If you create this task for an administration group, it will only be applied to Network Agents included in the specified administration group.

Updates are distributed to client devices and secondary Administration Servers from the shared folder of Administration Server.

See also:

Scenario: Regular updating Kaspersky databases and applications

Verifying downloaded updates

Download updates to the Administration Server repository task settings

Page top
[Topic 180697]

Verifying downloaded updates

Expand all | Collapse all

Before installing updates to the managed devices, you can first check the updates for operability and errors through the Update verification task. The Update verification task is performed automatically as part of the Download updates to the Administration Server repository task. The Administration Server downloads updates from the source, saves them in the temporary repository, and runs the Update verification task. If the task completes successfully, the updates are copied from the temporary repository to the Administration Server shared folder. They are distributed to all client devices for which the Administration Server is the source of updates.

If, as a result of the Update verification task, updates located in the temporary repository are incorrect or if the Update verification task completes with an error, such updates are not copied to the shared folder. The Administration Server retains the previous set of updates. Also, the tasks that have the When new updates are downloaded to the repository schedule type are not started then. These operations are performed at the next start of the Download updates to the Administration Server repository task if scanning of the new updates completes successfully.

A set of updates is considered invalid if any of the following conditions is met on at least one test device:

  • An update task error occurred.
  • The real-time protection status of the security application changed after the updates were applied.
  • An infected object was detected during running of the on-demand scan task.
  • A runtime error of a Kaspersky application occurred.

If none of the listed conditions is true for any test device, the set of updates is considered valid, and the Update verification task is considered to have completed successfully.

Before you start to create the Update verification task, perform the prerequisites:

  1. Create an administration group with several test devices. You will need this group to verify the updates.

    We recommend using devices with the most reliable protection and the most popular application configuration across the network. This approach increases the quality and probability of virus detection during scans, and minimizes the risk of false positives. If viruses are detected on test devices, the Update verification task is considered unsuccessful.

  2. Create two tasks for Kaspersky Endpoint Security for Windows: Update and Virus Scan. You will need them to create the Update verification task. This task sequentially runs the Update and Virus Scan tasks on test devices to check that all updates are valid.

    When creating the Update and Virus Scan tasks, specify the administration group with the test devices.

To make Kaspersky Security Center verify downloaded updates before distributing them to client devices:

  1. In the main menu, go to DEVICES → TASKS.
  2. Click the Download updates to the Administration Server repository task.
  3. In the task properties window that opens, in the Application settings tab, click the Configure button next to Run update verification.
  4. In the Update verification window that opens, enable the Run update verification option.
  5. If the Update verification task exists, click the Edit link. In the window that opens, select the Update verification task in the administration group with test devices.
  6. If you did not create the Update verification task earlier, do the following:
    1. Click the New task button.
    2. In the Add Task Wizard that opens, specify the task name if you want to change the preset name.
    3. Select the administration group with test devices, which you created earlier.
    4. First, select the Update task of Kaspersky Endpoint Security for Windows, and then select the Virus Scan task.

      After that, the following options appear. We recommend leaving them enabled:

    5. Specify an account from which the Update verification task will be run. You can use your account and leave the Default account option enabled. Alternatively, you can specify that the task should be run under another account that has the necessary access rights. To do this, select the Specify account option, and then enter the credentials of that account.
  7. Click Save to close the properties window of the Download updates to the Administration Server repository task.

The automatic update verification is enabled. Now, you can run the Download updates to the Administration Server repository task, and it will start from update verification.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 181095]

Creating the task for downloading updates to the repositories of distribution points

Expand all | Collapse all

The Downloading updates to the repositories of distribution points task works only on distribution point devices running Windows. Distribution point devices running Linux or macOS cannot download updates from Kaspersky update servers.If at least one device running Linux or macOS is within the task scope, the task will have the Failed status. Even if the task is completed successfully on all Windows devices, it will return an error on the remaining devices.

You can create the Download updates to the repositories of distribution points task for an administration group. This task will run for distribution points included in the specified administration group.

You can use this task, for example, if traffic between the Administration Server and the distribution point(s) is more expensive than traffic between the distribution point(s) and Kaspersky update servers, or if your Administration Server does not have internet access.

This task is required to download updates from Kaspersky update servers to the repositories of distribution points. The list of updates includes:

  • Updates to databases and software modules for Kaspersky security applications
  • Updates to Kaspersky Security Center components
  • Updates to Kaspersky security applications

After the updates are downloaded, they can be propagated to the managed devices.

To create the Download updates to the repositories of distribution points task, for a selected administration group:

  1. In the main menu, go to DEVICES → TASKS.
  2. Click the Add button.

    The Add Task Wizard starts. Follow the steps of the Wizard.

  3. For the Kaspersky Security Center application, in the Task type field select Download updates to the repositories of distribution points.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. Select an option button to specify the administration group, the device selection, or the devices to which the task applies.
  6. At the Finish task creation step, if you want to modify the default task settings, enable the Open task details when creation is complete option. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  7. Click the Create button.

    The task is created and displayed in the list of tasks.

  8. Click the name of the created task to open the task properties window.
  9. On the Application settings tab of the task properties window, specify the following settings:
    • Sources of updates

      The following resources can be used as a source of updates for the distribution point:

      • Kaspersky update servers.

        HTTP(S) servers at Kaspersky from which Kaspersky applications download database and application module updates.

        This option is selected by default.

      • A local or network folder that contains the latest updates. A network folder can be an FTP or HTTP server, or an SMB share. When selecting a local folder, you must specify a folder on the device that has Administration Server installed.

        An FTP or HTTP server or a network folder used by an update source must contain a folders structure (with updates) that matches the structure created when using Kaspersky update servers.

    • Folder for storing updates

      The path to the specified folder for storing saved updates. You can copy the specified folder path to a clipboard. You cannot change the path to a specified folder for a group task.

    • Update Network Agent modules

      If this option is enabled, updates for software modules of Network Agent are installed automatically after the Administration Server completes the download updates to the repository task. Otherwise, updates received for Network Agent modules can be installed manually.

      This option is only applicable to Network Agent versions earlier than 10 Service Pack 2. Starting from version 10 Service Pack 2, Network Agents are updated automatically.

      By default, this option is enabled.

    • Download diff files

      This option enables the downloading diff files feature.

      By default, this option is disabled.

  10. Create a schedule for task start. If necessary, specify the following settings:
    • Scheduled start

      Select the schedule according to which the task runs, and configure the selected schedule.

      • Manually (selected by default)

        The task does not run automatically. You can only start it manually.

        By default, this option is enabled.

      • Every N minutes

        The task runs regularly, with the specified interval in minutes, starting from the specified time on the day that the task is created.

        By default, the task runs every 30 minutes, starting from the current system time.

      • Every N hours

        The task runs regularly, with the specified interval in hours, starting from the specified date and time.

        By default, the task runs every six hours, starting from the current system date and time.

      • Every N days

        The task runs regularly, with the specified interval in days. Additionally, you can specify a date and time of the first task run. These additional options become available, if they are supported by the application for which you create the task.

        By default, the task runs every day, starting from the current system date and time.

      • Every N weeks

        The task runs regularly, with the specified interval in weeks, on the specified day of week and at the specified time.

        By default, the task runs every Monday at the current system time.

      • Daily (daylight saving time not supported)

        The task runs regularly, with the specified interval in days. This schedule does not support observance of daylight saving time (DST). It means that when clocks jump one hour forward or backward at the beginning or ending of DST, the actual task start time does not change.

        We do not recommend that you use this schedule. It is needed for backward compatibility of Kaspersky Security Center.

        By default, the task starts every day at the current system time.

      • Weekly

        The task runs every week on the specified day and at the specified time.

      • By days of week

        The task runs regularly, on the specified days of week, at the specified time.

        By default, the task runs every Friday at 6:00:00 PM.

      • Monthly

        The task runs regularly, on the specified day of the month, at the specified time.

        In months that lack the specified day, the task runs on the last day.

        By default, the task runs on the first day of each month, at the current system time.

      • Every month on specified days of selected weeks

        The task runs regularly, on the specified days of each month, at the specified time.

        By default, no days of month are selected; the default start time is 6:00:00 PM.

      • On virus outbreak

        The task runs after a Virus outbreak event occurs. Select application types that will monitor virus outbreaks. The following application types are available:

        • Anti-virus for workstations and file servers
        • Anti-virus for perimeter defense
        • Anti-virus for mail systems

        By default, all application types are selected.

        You may want to run different tasks depending on the anti-virus application type that reports a virus outbreak. In this case, remove the selection of the application types that you do not need.

      • On completing another task

        The current task starts after another task completes. You can select how the previous task must complete (successfully or with error) to trigger the start of the current task. For example, you may want to run the Manage devices task with the Turn on the device option and, after it completes, run the Virus scan task.

    • Run missed tasks

      This option determines the behavior of a task if a client device is not visible on the network when the task is about to start.

      If this option is enabled, the system attempts to start the task the next time the Kaspersky application is run on the client device. If the task schedule is Manually, Once or Immediately, the task is started immediately after the device becomes visible on the network or immediately after the device is included in the task scope.

      If this option is disabled, only scheduled tasks run on client devices; for Manually, Once and Immediately, tasks run only on those client devices that are visible on the network. For example, you may want to disable this option for a resource-consuming task that you want to run only outside of business hours.

      By default, this option is enabled.

    • Use automatically randomized delay for task starts

      If this option is enabled, the task is started on client devices randomly within a specified time interval, that is, distributed task start. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      The distributed start time is calculated automatically when a task is created, depending on the number of client devices to which the task is assigned. Later, the task is always started on the calculated start time. However, when task settings are edited or the task is started manually, the calculated value of the task start time changes.

      If this option is disabled, the task starts on client devices according to the schedule.

    • Use randomized delay for task starts within an interval of (min)

      If this option is enabled, the task is started on client devices randomly within the specified time interval. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      If this option is disabled, the task starts on client devices according to the schedule.

      By default, this option is disabled. The default time interval is one minute.

  11. Click the Save button.

The task is created and configured.

In addition to the settings that you specify during task creation, you can change other properties of a created task.

When the Download updates to the repositories of distribution points task is performed, updates for databases and software modules are downloaded from the update source and stored in the shared folder. Downloaded updates will only be used by distribution points that are included in the specified administration group and that have no update download task explicitly set for them.

The previous versions of the application (Kaspersky Security Center 10 Service Pack 2 and earlier) allowed you to create the update download task for distribution points as a local task only. Starting from Kaspersky Security Center 10 Service Pack 3, this restriction has been lifted, which has resulted in decreased traffic rates.

See also:

Download updates to the repositories of distribution points task settings

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 180731]

Enabling and disabling automatic updating and patching for Kaspersky Security Center components

Updates and patches for the Administration Server can be installed only manually, after obtaining explicit approval from the administrator.

Automatic installation of updates and patches for Kaspersky Security Center components is enabled by default during Network Agent installation on the device. You can disable it during Network Agent installation, or disable it later by using a policy.

To disable automatic updating and patching for Kaspersky Security Center components during local installation of Network Agent on a device:

  1. Start local installation of Network Agent on the device.
  2. At the Advanced settings step, clear the Automatically install applicable updates and patches for components that have Undefined status check box.
  3. Follow the instructions of the Wizard.

Network Agent with disabled automatic updating and patching for Kaspersky Security Center components will be installed on the device. You can enable automatic updating and patching later by using a policy.

To disable automatic updating and patching for Kaspersky Security Center components during Network Agent installation on the device through an installation package:

  1.  In the main menu, go to OPERATIONSREPOSITORIES → INSTALLATION PACKAGES.
  2. Click the Kaspersky Security Center Network Agent <version number> package.
  3. In the properties window, open the Settings tab.
  4. Turn off the Automatically install applicable updates and patches for components that have the Undefined status toggle button.

Network Agent with disabled automatic updating and patching for Kaspersky Security Center components will be installed from this package. You can enable automatic updating and patching later by using a policy.

If this check box was selected (or cleared) during Network Agent installation on the device, you can subsequently enable (or disable) automatic updating by using the Network Agent policy.

To enable or disable automatic updating and patching for Kaspersky Security Center components by using the Network Agent policy:

  1. In the main menu, go to DEVICESPOLICIES & PROFILES.
  2. Click the Network Agent policy.
  3. In the policy properties window, open the Application settings tab.
  4. In the Manage patches and updates section, turn on or off the Automatically install applicable updates and patches for components that have the Undefined status toggle button to enable or disable, respectively, automatic updating and patching.
  5. Set the lock () for this toggle button.

The policy will be applied to the selected devices, and automatic updating and patching for Kaspersky Security Center components will be enabled (or disabled) on these devices.

See also:

Scenario: Regular updating Kaspersky databases and applications

Automatic updating and patching for Kaspersky Security Center components

Page top
[Topic 180747]

Automatic installation of updates for Kaspersky Endpoint Security for Windows

You can configure automatic updates of databases and software modules of Kaspersky Endpoint Security for Windows on client devices.

To configure download and automatic installation of updates of Kaspersky Endpoint Security for Windows on devices:

  1. In the main menu, go to DEVICES TASKS.
  2. Click the Add button.

    The Add Task Wizard starts. Follow the steps of the Wizard.

  3. For the Kaspersky Endpoint Security for Windows application, select Update as the task subtype.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. Choose the task scope.
  6. Specify the administration group, the device selection, or the devices to which the task applies.
  7. At the Finish task creation step, if you want to modify the default task settings, enable the Open task details when creation is complete option. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  8. Click the Create button.

    The task is created and displayed in the list of tasks.

  9. Click the name of the created task to open the task properties window.
  10. On the Application settings tab of the task properties window, define the update task settings in local or mobile mode:
    • Local mode: Connection is established between the device and the Administration Server.
    • Mobile mode: No connection is established between Kaspersky Security Center and the device (for example, when the device is not connected to the internet).
  11. Enable the update sources that you want to use to update databases and application modules for Kaspersky Endpoint Security for Windows. If required, change positions of the sources in the list by using the Move up and Move down buttons. If several update sources are enabled, Kaspersky Endpoint Security for Windows tries to connect to them one after another, starting from the top of the list, and performs the update task by retrieving the update package from the first available source.
  12. Enable the Install approved application module updates option to download and install software module updates together with the application databases.

    If the option is enabled, Kaspersky Endpoint Security for Windows notifies the user about available software module updates and includes software module updates in the update package when running the update task. Kaspersky Endpoint Security for Windows installs only those updates for which you have set the Approved status; they will be installed locally through the application interface or through Kaspersky Security Center.

    You can also enable the Automatically install critical application module updates option. If any updates are available for software modules, Kaspersky Endpoint Security for Windows automatically installs those that have Critical status; the remaining updates will be installed after you approve them.

    If updating the software module requires reviewing and accepting the terms of the License Agreement and Privacy Policy, the application installs updates after the terms of the License Agreement and Privacy Policy have been accepted by the user.

  13. Select the Copy updates to folder check box in order for the application to save downloaded updates to a folder, and then specify the folder path.
  14. Schedule the task. To ensure timely updates, we recommend that you select the When new updates are downloaded to the repository option.
  15. Click Save.

When the Update task is running, the application sends requests to Kaspersky update servers.

Some updates require installation of the latest versions of management plug-ins.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 180749]

Approving and declining software updates

The settings of an update installation task may require approval of updates that are to be installed. You can approve updates that must be installed and decline updates that must not be installed.

For example, you may want to first check the installation of updates in a test environment and make sure that they do not interfere with the operation of devices, and only then allow the installation of these updates on client devices.

To approve or decline one or several updates:

  1. In the main menu, go to OPERATIONSKASPERSKY APPLICATIONS, and in the drop-down list select SEAMLESS UPDATES.

    A list of available updates appears.

    Updates of managed applications may require a specific minimum version of Kaspersky Security Center to be installed. If this version is later than your current version, these updates are displayed but cannot be approved. Also, no installation packages can be created from such updates until you upgrade Kaspersky Security Center. You are prompted to upgrade your Kaspersky Security Center instance to the required minimum version.

  2. Select the updates that you want to approve or decline.
  3. Click Approve to approve the selected updates or Decline to decline the selected updates.

    The default value is Undefined.

The updates to which you assign Approved status are placed in a queue for installation.

The updates to which you assign Declined status are uninstalled (if possible) from all devices on which they were previously installed. Also, they will not be installed on other devices in future.

Some updates for Kaspersky applications cannot be uninstalled. If you set Declined status for them, Kaspersky Security Center will not uninstall these updates from the devices on which they were previously installed. However, these updates will never be installed on other devices in future.

If you set Declined status for third-party software updates, these updates will not be installed on devices for which they were planned but have not yet been installed. Updates will remain on devices on which they were already installed. If you have to delete the updates, you can manually delete them locally.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 180195]

Updating Administration Server

You can install Administration Server updates by using Update Administration Server Wizard.

To install an Administration Server update:

  1. In the main menu, go to OPERATIONS → KASPERSKY APPLICATIONS → SEAMLESS UPDATES.
  2. Run the Update Administration Server Wizard in one of the following ways:
    • Click the name of an Administration Server update in the list of updates, and in the window that opens, click the Run Update Administration Server Wizard link.
    • Click the Run Update Administration Server Wizard link in the notification field at the top of the window.
  3. In the Update Administration Server Wizard window, select one of the following to specify when to install an update:
    • Install now. Select this option if you want to install the update now.
    • Postpone installation. Select this option if you want to install the update later. In this case, a notification about this update will be displayed.
    • Ignore update. Select this option if you do not want to install an update and do not want to receive notifications about this update.
  4. Select the Create backup copy of Administration Server before update installation option if you want to create a backup of Administration Server before installing the update.
  5. Click the OK button to finish the Wizard.

In the backup process is interrupted, the update installation process is also interrupted.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 209563]

Enabling and disabling the offline model of update download

We recommend that you avoid disabling the offline model of update download. Disabling it may cause failures in update delivery to devices. In certain cases, a Kaspersky Technical Support specialist may recommend that you disable the Download updates and anti-virus databases from Administration Server in advance option. Then, you will have to make sure that the task for receiving updates for Kaspersky applications has been set up.

To enable or disable the offline model of update download for an administration group:

  1. In the main menu, go to DEVICES POLICIES & PROFILES.
  2. Click Groups.
  3. In the administration group structure, select the administration group for which you need to enable the offline model of update download.
  4. Click the Network Agent policy.

    The properties window of the Network Agent policy opens.

    By default, settings of child policies are inherited from parent policies and cannot be modified. If the policy that you want to modify is inherited, you first need to create a new policy for Network Agent in the required administration group. In the newly created policy, you can modify the settings that are not locked in the parent policy.

  5. In the Application settings tab, select the Manage patches and updates section.
  6. Enable or disable the Download updates and anti-virus databases from Administration Server in advance (recommended) option to enable or disable, respectively, the offline model of update download.

    By default, the offline model of update download is enabled.

The offline model of update download will be enabled or disabled.

See also:

Scenario: Regular updating Kaspersky databases and applications

Offline model of update download

Page top
[Topic 181202]

Updating Kaspersky databases and software modules on offline devices

Updating Kaspersky databases and software modules on managed devices is an important task for maintaining protection of the devices against viruses and other threats. Administrators usually configure regular updates through usage of the Administration Server repository or repositories of distribution points.

When you need to update databases and software modules on a device (or a group of devices) that is not connected to the Administration Server (primary or secondary), a distribution point or the internet, you have to use alternative sources of updates, such as an FTP server or a local folder. In this case you have to deliver the files of the required updates by using a mass storage device, such as a flash drive or an external hard drive.

You can copy the required updates from:

  • The Administration Server.

    To be sure the Administration Server repository contains the updates required for the security application installed on an offline device, at least one of the managed online devices must have the same security application installed. This application must be configured to receive the updates from the Administration Server repository through the Download updates to the Administration Server repository task.

  • Any device that has the same security application installed and configured to receive the updates from the Administration Server repository, a distribution point repository, or directly from the Kaspersky update servers.

Below is an example of configuring updates of databases and software modules by copying them from the Administration Server repository.

To update Kaspersky databases and software modules on offline devices:

  1. Connect the removable drive to the device where the Administration Server is installed.
  2. Copy the updates files to the removable drive.

    By default, the updates are located at: \\<server name>\KLSHARE\Updates.

    Alternatively, you can configure Kaspersky Security Center to regularly copy the updates to the folder that you select. For this purpose, use the Copy downloaded updates to additional folders option in the properties of the Download updates to the Administration Server repository task. If you specify a folder located on a flash drive or an external hard drive as a destination folder for this option, this mass storage device will always contain the latest version of the updates.

  3. On offline devices, configure the security application (for example, Kaspersky Endpoint Security for Windows) to receive updates from a local folder or a shared resource, such as an FTP server or a shared folder.
  4. Copy the updates files from the removable drive to the local folder or the shared resource that you want to use as an update source.
  5. On the offline device that requires update installation, start the update task of Kaspersky Endpoint Security for Windows.

After the update task is complete, the Kaspersky databases and software modules are up-to-date on the device.

See also:

Scenario: Regular updating Kaspersky databases and applications

Creating the Download updates to the Administration Server repository task

Page top
[Topic 180902]

Adjustment of distribution points and connection gateways

A structure of administration groups in Kaspersky Security Center performs the following functions:

  • Sets the scope of policies

    There is an alternate way of applying relevant settings on devices, by using policy profiles. In this case, you set the scope of policies with tags, device locations in Active Directory organizational units, or membership in Active Directory security groups.

  • Sets the scope of group tasks

    There is an approach to defining the scope of group tasks that is not based on a hierarchy of administration groups: use of tasks for device selections and tasks for specific devices.

  • Sets access rights to devices, virtual Administration Servers, and secondary Administration Servers
  • Assigns distribution points

When building the structure of administration groups, you must take into account the topology of the organization's network for the optimum assignment of distribution points. The optimum distribution of distribution points allows you to save traffic on the organization's network.

Depending on the organizational schema and network topology, the following standard configurations can be applied to the structure of administration groups:

  • Single office
  • Multiple small remote offices

Devices functioning as distribution points must be protected, including physical protection, against any unauthorized access.

In this section

Standard configuration of distribution points: Single office

Standard configuration of distribution points: Multiple small remote offices

Assigning distribution points automatically

Assigning distribution points manually

Modifying the list of distribution points for an administration group

Forced synchronization

Enabling a push server

See also:

Scenario: Regular updating Kaspersky databases and applications

Main installation scenario

Page top
[Topic 92429_1]

Standard configuration of distribution points: Single office

In a standard "single-office" configuration, all devices are on the organization's network so they can "see" each other. The organization's network may consist of a few separate parts (networks or network segments) linked by narrow channels.

The following methods of building the structure of administration groups are possible:

  • Building the structure of administration groups taking into account the network topology. The structure of administration groups may not reflect the network topology with absolute precision. A match between the separate parts of the network and certain administration groups would be enough. You can use automatic assignment of distribution points or assign them manually.
  • Building the structure of administration groups, without taking the network topology into account. In this case, you must disable automatic assignment of distribution points, and then assign one or several devices to act as distribution points for a root administration group in each of the separate parts of the network, for example, for the Managed devices group. All distribution points will be at the same level and will feature the same scope spanning all devices on the organization's network. In this case, each Network Agent in version 10 Service Pack 1 or later will connect to the distribution point that has the shortest route. The route to a distribution point can be traced with the tracert utility.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 92430_1]

Standard configuration of distribution points: Multiple small remote offices

This standard configuration provides for a number of small remote offices, which may communicate with the head office over the internet. Each remote office is located behind the NAT, that is, connection from one remote office to another is not possible because offices are isolated from one another.

The configuration must be reflected in the structure of administration groups: a separate administration group must be created for each remote office (groups Office 1 and Office 2 in the figure below).

A Managed devices node includes the Root group for offices folder that contains Administration Servers, and groups Office 1 and Office 2.

Remote offices are included in the administration group structure

One or multiple distribution points must be assigned to each administration group that correspond to an office. Distribution points must be devices at the remote office that have a sufficient amount of free disk space. Devices deployed in the Office 1 group, for example, will access distribution points assigned to the Office 1 administration group.

If some users move between offices physically, with their laptops, you must select two or more devices (in addition to the existing distribution points) in each remote office and assign them to act as distribution points for a top-level administration group (Root group for offices in the figure above).

Example: A laptop is deployed in the Office 1 administration group and then is moved physically to the office that corresponds to the Office 2 administration group. After the laptop is moved, Network Agent attempts to access the distribution points assigned to the Office 1 group, but those distribution points are unavailable. Then, Network Agent starts attempting to access the distribution points that have been assigned to the Root group for offices. Because remote offices are isolated from one another, attempts to access distribution points assigned to the Root group for offices administration group will only be successful when Network Agent attempts to access distribution points in the Office 2 group. That is, the laptop will remain in the administration group that corresponds to the initial office, but the laptop will use the distribution point of the office where it is physically located at the moment.

See also:

Adjustment of distribution points and connection gateways

Requirements for a distribution point

About distribution points

Scenario: Regular updating Kaspersky databases and applications

Scenario: Discovering networked devices

Page top
[Topic 92431_1]

Assigning distribution points automatically

We recommend that you assign distribution points automatically. In this case, Kaspersky Security Center will select on its own which devices must be assigned distribution points.

To assign distribution points automatically:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Select the Automatically assign distribution points option.

    If automatic assignment of devices as distribution points is enabled, you cannot configure distribution points manually or edit the list of distribution points.

  4. Click the Save button.

Administration Server assigns and configures distribution points automatically.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 181627]

Assigning distribution points manually

Expand all | Collapse all

Kaspersky Security Center allows you to manually assign devices to act as distribution points.

We recommend that you assign distribution points automatically. In this case, Kaspersky Security Center will select on its own which devices must be assigned distribution points. However, if you have to opt out of assigning distribution points automatically for any reason (for example, if you want to use exclusively assigned servers), you can assign distribution points manually after you calculate their number and configuration.

Devices functioning as distribution points must be protected, including physical protection, against any unauthorized access.

To manually assign a device to act as distribution point:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Select the Manually assign distribution points option.
  4. Click the Assign button.
  5. Select the device that you want to make a distribution point.

    When selecting a device, keep in mind the operation features of distribution points and the requirements set for the device that acts as distribution point.

  6. Select the administration group that you want to include in the scope of the selected distribution point.
  7. Click the OK button.

    The distribution point that you have added will be displayed in the list of distribution points, in the Distribution points section.

  8. Select the newly added distribution point in the list to open its properties window.
  9. Configure the distribution point in the properties window:
    • The General section contains the setting of interaction between the distribution point and client devices:
      • SSL port

        The number of the SSL port for encrypted connection between client devices and the distribution point using SSL.

        By default, port 13000 is used.

      • Use multicast

        If this option is enabled, IP multicasting will be used for automatic distribution of installation packages to client devices within the group.

        IP multicasting decreases the time required to install an application from an installation package to a group of client devices, but increases the installation time when you install an application to a single client device.

      • IP multicast address

        IP address that will be used for multicasting. You can define an IP address in the range of 224.0.0.0 – 239.255.255.255

        By default, Kaspersky Security Center automatically assigns a unique IP multicast address within the given range.

      • IP multicast port number

        Number of the port for IP multicasting.

        By default, the port number is 15001. If the device with Administration Server installed is specified as the distribution point, port 13001 is used for SSL connection by default.

      • Deploy updates

        Updates are distributed to managed devices from the following sources:

        • This distribution point, if this option is enabled.
        • Other distribution points, Administration Server, or Kaspersky update servers, if this option is disabled.

        If you use distribution points to deploy updates, you can save traffic because you reduce the number of downloads. Also, you can relieve the load on the Administration Server and relocate the load between the distribution points. You can calculate the number of distribution points for your network to optimize the traffic and load.

        If you disable this option, the number of update downloads and load on the Administration Server may increase. By default, this option is enabled.

      • Deploy installation packages

        Installation packages are distributed to managed devices from the following sources:

        • This distribution point, if this option is enabled.
        • Other distribution points, Administration Server, or Kaspersky update servers, if this option is disabled.

        If you use distribution points to deploy installation packages, you can save traffic because you reduce the number of downloads. Also, you can relieve the load on the Administration Server and relocate the load between the distribution points. You can calculate the number of distribution points for your network to optimize the traffic and load.

        If you disable this option, the number of installation package downloads and load on the Administration Server may increase. By default, this option is enabled.

      • Run push server

        In Kaspersky Security Center, a distribution point can work as a push server for the devices managed through the mobile protocol and for the devices managed by Network Agent. For example, a push server must be enabled if you want to be able to force synchronization of KasperskyOS devices with Administration Server. A push server has the same scope of managed devices as the distribution point on which the push server is enabled. If you have several distribution points assigned for the same administration group, you can enable push server on each of the distribution points. In this case, Administration Server balances the load between the distribution points.

      • Push server port

        The port number for the push server. You can specify number of any unoccupied port.

    • In the Scope section, specify the scope to which the distribution point will distribute updates (administration groups and / or network location).

      Only devices running a Windows operating system can determine their network location. Network location cannot be determined for devices running other operating systems.

    • In the Source of updates section, you can select a source of updates for the distribution point:
      • Source of updates

        Select a source of updates for the distribution point:

        • To allow the distribution point to receive updates from the Administration Server, select Retrieve from Administration Server.
        • To allow the distribution point to receive updates by using a task, select Use update download task, and then specify a Download updates to the repositories of distribution points task:
          • If such a task already exists on the device, select the task in the list.
          • If no such task yet exists on the device, click the Create task link to create a task. The Add Task Wizard starts. Follow the instructions of the Wizard.

      • Download diff files

        This option enables the downloading diff files feature.

        By default, this option is enabled.

    • In the KSN Proxy section, you can configure the application to use the distribution point to forward KSN requests from the managed devices:
      • Enable KSN Proxy on distribution point side

        The KSN proxy service is run on the device that is used as a distribution point. Use this feature to redistribute and optimize traffic on the network.

        The distribution point sends the KSN statistics, which are listed in the Kaspersky Security Network statement, to Kaspersky. By default, the KSN statement is located in %ProgramFiles%\Kaspersky Lab\Kaspersky Security Center\ksneula.

        By default, this option is disabled. Enabling this option takes effect only if the Use Administration Server as a proxy server and I agree to use Kaspersky Security Network options are enabled in the Administration Server properties window.

        You can assign a node of an active-passive cluster to a distribution point and enable KSN proxy server on this node.

      • Forward KSN requests to Administration Server

        The distribution point forwards KSN requests from the managed devices to the Administration Server.

        By default, this option is enabled.

      • Access KSN Cloud / Private KSN directly over the Internet

        The distribution point forwards KSN requests from managed devices to the KSN Cloud or Private KSN. The KSN requests generated on the distribution point itself are also sent directly to the KSN Cloud or Private KSN.

        The distribution points that have Network Agent version 11 (or earlier) installed cannot access Private KSN directly. If you want to reconfigure the distribution points to send KSN requests to Private KSN, enable the Forward KSN requests to Administration Server option for each distribution point.

        The distribution points that have Network Agent version 12 (or later) installed can access Private KSN directly.

      • Ignore KSC proxy server settings when connecting to Private KSN

        Enable this option, if you have the proxy server settings configured in the distribution point properties or in the Network Agent policy, but your network architecture requires that you use Private KSN directly. Otherwise, requests from the managed applications cannot reach Private KSN.

        This option is available if you select the Access KSN Cloud / Private KSN directly over the Internet option.

      • TCP port

        The number of the TCP port that the managed devices will use to connect to KSN proxy server. The default port number is 13111.

      • UDP port

        If you need the managed devices to connect to KSN proxy server through a UDP port, enable the Use UDP port option and specify a UDP port number. By default, this option is enabled. The default UDP port to connect to the KSN proxy server is 15111.

    • Configure the polling of Windows domains, Active Directory, and IP ranges by the distribution point:
      • Windows domains

        You can enable device discovery for Windows domains and set the schedule for the discovery.

      • Active Directory

        You can enable network polling for Active Directory and set the schedule for the poll.

        If you select the Enable Active Directory polling check box, you can select one of the following options:

        • Poll current Active Directory domain.
        • Poll Active Directory domain forest.
        • Poll selected Active Directory domains only. If you select this option, add one or more Active Directory domains to the list.
      • IP ranges

        You can enable device discovery for IP ranges.

        If you select the Enable range polling check box, you can add scan ranges and set the schedule for them.

        You can add IP ranges to the list of scanned ranges.

    • In the Advanced section, specify the folder that the distribution point must use to store distributed data:
      • Use default folder

        If you select this option, the application uses the Network Agent installation folder on the distribution point.

      • Use specified folder

        If you select this option, in the field below, you can specify the path to the folder. It can be a local folder on the distribution point, or it can be a folder on any device on the corporate network.

        The user account used on the distribution point to run Network Agent must have read/write access to the specified folder.

  10. Click the OK button.

The selected devices act as distribution points.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 181511]

Modifying the list of distribution points for an administration group

You can view the list of distribution points assigned to a specific administration group and modify the list by adding or removing distribution points.

To view and modify the list of distribution points assigned to an administration group:

  1. In the main menu, go to DEVICES → MANAGED DEVICES.
  2. In the Current path field above the list of managed devices, click the path link.
  3. In the left-side pane that opens, select an administration group for which you want to view the assigned distribution points.

    This enables the DISTRIBUTION POINTS menu item.

  4. In the main menu, go to DEVICES → DISTRIBUTION POINTS.
  5. To add new distribution points for the administration group, click the Assign button above the list of managed devices and select devices from the pane that opens.
  6. To remove the assigned distribution points, select devices from the list and click the Unassign button.

Depending on your modifications, the new distribution points are added to the list or existing distribution points are removed from the list.

See also:

Scenario: Regular updating Kaspersky databases and applications

Page top
[Topic 181540]

Forced synchronization

Although Kaspersky Security Center automatically synchronizes the status, settings, tasks, and policies for managed devices, in some cases you might want to run the synchronization for a specified device forcibly. You can run forced synchronization for the following devices:

  • Devices that have Network Agent installed
  • Devices running KasperskyOS

    Before running forced synchronization for a KasperskyOS device, ensure that the device is included in a distribution point scope and that a push server is enabled on the distribution point.

  • iOS devices
  • Android devices

    Before running forced synchronization for an Android device, you must configure Google Firebase Cloud Messaging.

Synchronizing a single device

To force synchronization between the Administration Server and a managed device:

  1. In the main menu, go to DEVICES → MANAGED DEVICES.
  2. Click the name of the device that you want to synchronize with the Administration Server.

    A property window opens with the General section selected.

  3. Click the Force synchronization button.

The application synchronizes the selected device with the Administration Server.

Synchronizing multiple devices

To force synchronization between the Administration Server and multiple managed devices:

  1. Open the device list of an administration group or a device selection:
    • In the main menu, go to DEVICES → MANAGED DEVICES, click the path link in the Current path field above the list of managed devices, then select the administration group that contains devices to synchronize.
    • Run a device selection to view the device list.
  2. Select the check boxes next to the devices that you want to synchronize with the Administration Server.
  3. Above the list of managed devices, click the ellipsis button (), and then click the Force synchronization button.

    The application synchronizes the selected devices with the Administration Server.

  4. In the device list, check that the time of last connection to the Administration Server has changed, for the selected devices, to the current time. If the time has not changed, update the page content by clicking the Refresh button.

The selected devices are synchronized with the Administration Server.

Viewing the time of a policy delivery

After changing a policy for a Kaspersky application on the Administration Server, the administrator can check whether the changed policy has been delivered to a specific managed device. A policy can be delivered during a regular synchronization or a forced synchronization.

To view the date and time that an application policy was delivered to a managed device:

  1. In the main menu, go to DEVICES → MANAGED DEVICES.
  2. Click the name of the device that you want to synchronize with the Administration Server.

    A property window opens with the General section selected.

  3. Select the Applications tab.
  4. Select the application for which you want to view the policy synchronization date.

    The application policy window opens with the General section selected and the policy delivery date and time displayed.

See also:

Policy setup and propagation: Device-centric approach

Scenario: Configuring network protection

Enabling a push server

Page top
[Topic 175431]

Enabling a push server

In Kaspersky Security Center, a distribution point can work as a push server for the devices managed through the mobile protocol and for the devices managed by Network Agent. For example, a push server must be enabled if you want to be able to force synchronization of KasperskyOS devices with Administration Server. A push server has the same scope of managed devices as the distribution point on which the push server is enabled. If you have several distribution points assigned for the same administration group, you can enable push server on each of the distribution points. In this case, Administration Server balances the load between the distribution points.

You might want to use distribution points as push servers to make sure that there is continuous connectivity between a managed device and the Administration Server. Continuous connectivity is needed for some operations, such as running and stopping local tasks, receiving statistics for a managed application, or creating a tunnel. If you use a distribution point as a push server, you do not have to use the Do not disconnect from the Administration Server option on managed devices or send packets to the UDP port of the Network Agent.

A push server supports the load of up to 50,000 simultaneous connections.

To enable push server on a distribution point:

  1. Click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Click the name of the distribution point on which you want to enable the push server.

    The distribution point properties window opens.

  4. On the General section, enable the Run push server option.
  5. In the Push server port field, type the port number. You can specify number of any unoccupied port.
  6. In the Address for remote hosts field, specify the IP address or the name of the distribution point device.
  7. Click the OK button.

The push server is enabled on the selected distribution point.

See also:

Forced synchronization

Using a distribution point as a push server

Page top
[Topic 214620]