Kaspersky Security Center Linux 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 Linux 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:
In the main menu, click the settings icon () next to the name of the required Administration Server.
The Administration Server properties window opens.
On the General tab, select the Distribution points section.
Select the Manually assign distribution points option.
Click the Assign button.
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.
Select the administration group that you want to include in the scope of the selected distribution point.
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.
Click the newly added distribution point in the list to open its properties window.
Configure the distribution point in the properties window:
The General section contains the settings of interaction between the distribution point and client devices.
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.
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.
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.
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.
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.
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.
Password of the account under which the task will be run.
In the Connection gateway section, you can configure the distribution point to act as a gateway for connection between Network Agent instances and Administration Server:
If a direct connection between Administration Server and Network Agents cannot be established due to organization of your network, you can use the distribution point to act as the connection gateway between Administration Server and Network Agents.
Enable this option if you need the distribution point to act as a connection gateway between Network Agents and Administration Server. By default, this option is disabled.
If Administration Server is located outside the demilitarized zone (DMZ), on local area network, Network Agents installed on remote devices cannot connect to Administration Server. You can use a distribution point as the connection gateway with reverse connectivity (Administration Server establishes a connection to distribution point).
Enable this option if you need to connect Administration Server to the connection gateway in DMZ.
Enable this option if you need the connection gateway in DMZ to open a port for Web Console that is in DMZ or on the internet. Specify the port number that will be used for the connection from Web Console to the distribution point. The default port number is 13299.
This option is available if you enable the Establish connection to gateway from Administration Server (if gateway is in DMZ) option.
When connecting mobile devices to Administration Server via the distribution point that acts as a connection gateway, you can enable the following options:
Enable this option if you need the connection gateway to open a port for mobile devices and specify the port number that mobile devices will use for connection to distribution point. The default port number is 13292. The mobile device will check the Administration Server certificate. When establishing the connection, only Administration Server is authenticated.
Enable this option if you need connection gateway to open a port that will be used for two-way authentication of Administration Server and mobile devices. Mobile device will check the Administration Server certificate, and Administration Server will check the mobile device certificate. Specify the following parameters:
Port number that mobile devices will use for connection to the distribution point. The default port number is 13293.
DNS domain names of the connection gateway that will be used by mobile devices. Separate domain names with commas. The specified domain names will be included in the distribution point certificate. If the domain names used by mobile devices do not match the common name in the distribution point certificate, mobile devices do not connect to the distribution point.
The default DNS domain name is the FQDN name of the connection gateway.
In both cases, the certificates are checked during the TLS session establishment on distribution point only. The certificates are not forwarded to be checked by the Administration Server. After a TLS session with the mobile device is established, the distribution point uses the Administration Server certificate to create a tunnel for synchronization between the mobile device and Administration Server. If you open the port for two-way SSL authentication, the only way to distribute the mobile device certificate is via an installation package.
Configure the polling of IP ranges by the distribution point.
You can enable device discovery for IPv4 ranges and IPv6 networks.
If you enable the Enable range polling option, you can add scanned ranges and set the schedule for them. You can add IP ranges to the list of scanned ranges.
If you enable the Use Zeroconf to poll IPv6 networks option, the distribution point automatically polls the IPv6 network by using zero-configuration networking (also referred to as Zeroconf). In this case, the specified IP ranges are ignored because the distribution point polls the whole network. The Use Zeroconf to poll IPv6 networks option is available if the distribution point runs Linux. To use Zerocong IPv6 polling, you must install the avahi-browse utility on the distribution point.
In the Advanced section, specify the folder that the distribution point must use to store distributed data.
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.
) next to the name of the required Administration Server.