Operation of Kaspersky Thin Client

The standard operating scenario for Kaspersky Thin Client (see the figure below) involves the following:

• After Kaspersky Thin Client system is installed on a thin client, it receives network settings from a DHCP server, or the administrator manually configures these settings.
• The administrator connects and configures interaction between Kaspersky Thin Client and Kaspersky Security Center, and also installs the Kaspersky Security Management Suite web plug-in.
• Kaspersky Thin Client receives trusted certificates, remote environment connection settings, date and time, and other basic settings using a policy created via Kaspersky Security Center Web Console.

  A policy determines settings of Kaspersky Thin Client and defines access to configuration of Kaspersky Thin Client system settings on devices within an administration group. You can create an unlimited number of different policies for Kaspersky Thin Client installed on devices in each administration group, but only one policy at a time can be applied to each Kaspersky Thin Client device within an administration group.

• The user connects to the remote environment.
  

  Any supported remote resource, such as a remote desktop or virtual application, that a thin client user can access for work using remote access technology.

• In case of problems, the user forwards audit and event logs via the Kaspersky Thin Client interface to a log server deployed in your enterprise infrastructure.
  

  The server that will receive Kaspersky Thin Client event and audit logs. This server is deployed within your corporate network.

• The administrator updates Kaspersky Thin Client.

  

  Standard operating scenario for Kaspersky Thin Client

The image below shows a diagram of Kaspersky Thin Client communication with virtualization platforms and remote environments.

Communication between Kaspersky Thin Client and virtualization platforms and remote environments

Page top