Virtual environments are complex and varied. Due to these peculiarities, installing Panda solutions in these environments requires a special procedure which is described below. In environments with very specific characteristics, it may be necessary to follow the recommendations provided by the virtualization vendor to adapt Panda’s general instructions to your needs. Please contact Panda Security Technical Support so that our experts can analyze your particular environment and provide you with a tailor-made solution as soon as possible.
This article offers a step-by-step walkthrough of how to install Panda Security solutions on Aether platform in persistent and non-persistent Virtual Desktop Infrastructure (VDI) environments. Due to their characteristics, virtual computers or instances require that a specific procedure be followed to ensure that the images or templates to be used in virtual environments are up to date, optimized, and don’t have a previously assigned machine ID so that, when a virtual computer is started, it is uniquely wp-signup.phped in the Web console.
The installation procedure requires that a template (for persistent environments) or a gold image (for non-persistent environments) be prepared that will be later deployed to the virtual computers on the network. It is very important to follow this procedure closely to:
- Ensure engine and knowledge updates.
- Optimize resource and bandwidth consumption in non-persistent environments.
- Ensure virtual instances are uniquely identified.
- In persistent environments, computers must have fixed MAC addresses.
- The computer used to generate the template or gold image must have an Internet connection.
Generally, the procedure described in this document works* with the following types of virtual machines:
- VMware Workstation
- VMware Server
- VMware ESX
- VMware ESXi
- Citrix XenDesktop
- MS Virtual Desktop
- MS Virtual Servers
*Bear in mind the considerations at the beginning of the article.
Installing the protection in persistent environments
Installing the protection in non-persistent VDI environments
The procedure for managing non-persistent VDI environments consists of three phases.
If the aforementioned process is followed appropriately, that is, if the step to delete the agent ID is performed correctly selecting and clearing the Is a gold image option as indicated, every time a new machine is started, the system will calculate its machine ID and will determine whether the computer is a new computer or an existing one, based on the selected environment.
- In non-persistent environments, if the maximum number of machines that can be active simultaneously for non-persistent images is set, the server will manage licenses automatically, provided there are available licenses and the number of concurrent machines is not exceeded.
- In persistent environments, if there are multiple machines that are no longer used, delete them from the database in order to free up licenses just as you would do with physical machines. This can be done from the Aether console, by selecting all machines to delete and clicking the Delete button, or individually via the context menu of each machine to delete.