Examples of using Protection server in English and their translations into Russian
{-}
-
Official
-
Colloquial
to protection settings and during scan task is performed on the Protection Server.
The Kaspersky Security distribution kit includes archives for installing the Protection Server on hypervisors of various types.
After deploying SVMs with the new version of the Protection Server component, you must perform the following actions.
The Integration Server is a component of Kaspersky Security that transmits information from SVMs with Protection Server installed to Light Agents installed on protected virtual machines.
Installing the Protection Server component of Kaspersky Security see section"Installing the Protection Server component" on page 62.
The upgrade is executed by deploying SVMs with the new version of the Protection Server component on hypervisors.
If Light Agent isn't connected to a single SVM, the Protection Server does not scan the SVM's files.
This step is unavailable if you have enabled the display of advanced Protection Server policy settings in the operating system registry see section"Displaying policy settings" on page 79.
The connection settings are configured when you create a Protection Server policy(see section"Step 5. 84)
When core-based licensing is used, Protection Server can send an event with information about license restriction violations to Kaspersky Security Center.
Create a Protection Server update task for the SVMs on which you want to update application databases and modules see section"Creating a Protection Server update task" on page 123.
The use of Kaspersky Security Network services is configured in the settings of the Protection Server policy.
task to start or start the task manually see section"Starting and stopping a Protection Server update task" on page 121.
The method used by SVMs to transmit information about themselves can be specified in the Protection Server policy.
Another product introduction in November, 2004 included Protection Server 3.0, with Email Firewall
By default, Light Agent connects to the Protection Server on the SVM on the same hypervisor on which the protected virtual machine is running see section"About Light Agent connection to an SVM" on page 31.
By default, the Protection Server Policy Wizard and the properties of the Protection Server policy do not display SVM advanced settings see section"Step 6. Configuring additional settings of SVM operation" on page 85.
Information about the type of KSN used by Kaspersky Security appears in the properties of the Protection Server policy(see section“Configuring the use of Kaspersky Security Network” on page 176)
Create a Protection Server update rollback task for the SVMs on which you want to rollback updates of databases and application software modules see section"Creating a Protection Server update rollback task" on page 127.
If the Protection Server policy includes a configured connection of SVMs to the Integration Server and you have changed the password of the account for connecting SVMs, you have to reconfigure the connection of SVMs to the Integration Server in the Protection Server policy.