Примеры использования Protected virtual machines на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
Create new temporary protected virtual machines from the updated template.
Use the new snapshot to recreate the pool of temporary protected virtual machines.
Used for servers- the number of protected virtual machines with a server operating system.
The last application database and module update is rolled back on protected virtual machines.
Tasks running on protected virtual machines with the Light Agent for Windows component installed.
Kaspersky Security will use these settings on the protected virtual machines after the policy is applied.
Turn on the protected virtual machine whose template was used to create the pool of temporary protected virtual machines.
Used for desktop machines- the number of protected virtual machines with a desktop operating system.
If you have chosen the Inactive policy option, the created policy is not applied on the protected virtual machines.
For a server ordesktop key- the number of protected virtual machines on which the key is used as the active key;
For operation of the Integration Server that serves no more than 30 hypervisors and2,000 to 2,500 protected virtual machines- 300 MB.
The policy is applied on all protected virtual machines belonging to the administration group for which the policy is configured.
Licensing by number of cores used in the physical processors on the hypervisors on which protected virtual machines are running.
For all SVMs and protected virtual machines connected to them, it is recommended to use only one of the above two licensing schemes.
Kaspersky Security Center transfers these settings to the protected virtual machines when the policy is applied.
If the editing of component settings via the local interface is blocked, Kaspersky Security uses the policy-configured component operation settings on all protected virtual machines.
Determines the parameters of operation of Light Agents installed on protected virtual machines with Windows guest operating systems.
Network Agent provides an interface between Kaspersky Security Center Administration Server and protected virtual machines.
Upgrading the Light Agent component on protected virtual machines see section"Upgrading the Light Agent for Windows component" on page 132.
This mode may be used to monitor andanalyze traffic in the network segment that the SVM and protected virtual machines are operating in.
Total keys used as active for servers- the number of protected virtual machines with a server operating system on which the key is used as an active key.
In the Managed computers folder of the console tree,open the folder with the name of the administration group to which the relevant protected virtual machines belong.
Task for sets of computers- a task for one or several SVMs or protected virtual machines included or not included in administration groups.
In the Managed computers folder of the console tree, select the folder with the name of the administration group for whose protected virtual machines you want to create a policy.
If you choose the option of licensing by the number of protected virtual machines, the type of additional key must match the guest operating system of the virtual machines. .
After the application database and module update has been rolled back on the SVM, the last update is rolled back on all protected virtual machines connected to this SVM.
If you are using a licensing scheme based on the number of protected virtual machines, the type of additional key must match the guest operating system of the virtual machines. .
The Executable files folder contains a list of the executable files that have ever been started on protected virtual machines or that have been detected during Kaspersky Security's inventory task.
After installation of Kaspersky Security in the virtual infrastructure, the SVMs and protected virtual machines on which Network Agent is installed forward information about themselves to Kaspersky Security Center.