The choice of the hypervisor that best meets business’ needs is a great dilemma for companies when deploying a virtualization platform.
The best solution is not the same for all companies, it depends on the specific requirements in each case. If you need a simple virtualization platform, Microsoft Hyper-V or VMware ESXi free versions may be appropiate for you. They are two of the most popular hypervisors and they feature professional support and updates. On the other hand, Citrix XenServer has interesting advantages for Linux users.
UDS Enterprise fully integrates with Microsoft Hyper-V (version 3 onwards).
UDS Enterprise components are offered in Virtual Appliance format and they are hosted on the Hyper-V platform on which the virtual desktops are going to be deployed.
The integration process is very easy, you can check it reading this presentation:
Microsoft is taking containerization one step further by expanding the scenarios and workloads developers can address with containers.
Microsoft will now offer containers with a new level of isolation previously reserved only for fully dedicated physical or virtual machines, while maintaining an agile and efficient experience with full Docker cross-platform integration.
In this post we are going to describe how to deploy a VDI infrastructure with Microsoft Hyper-V and our VDI connection broker for Windows and Linux UDS Enterprise. The process of integrating UDS Enterprise with Microsoft Hyper-V is a simple task since its components are offered in Virtual Appliance format. Through a simple process, the UDS Enterprise components are hosted on the Microsoft Hyper-V platform on which the virtual desktops are going to be deployed. Once the components have been stored, it is necessary to interconnect all of them between each other as well as with the Microsoft Hyper-V virtual platform.
The initial version of Hyper-V only supported one minimal feature for Linux virtual machines (VM) through the installation of an additional component called Linux Integration Services (LIS). But recently, Microsoft has been working with providers to add new features without having to install SIL in newer Linux distributions.
One of the most awaited is the Dynamic Memory. The addition and removal of memory are now fully compatible with virtual machines running on a Windows Server Linux 2012 R2 Hyper-V host. It is important to note that this function is only available for 64-bit Linux distros and in some of them it is necessary to enable support, for example in CentOS and Red Hat Linux distributions.
To offer the best experiences, we use technologies such as cookies to store and/or access device information. Consent to these technologies will allow us to process data such as browsing behavior or unique identifications on this site. Not consenting or withdrawing consent may negatively affect certain features and functions.
Functional
Always active
The storage or technical access is strictly necessary for the legitimate purpose of allowing the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication through an electronic communications network.
Preferencias
El almacenamiento o acceso técnico es necesario para la finalidad legítima de almacenar preferencias no solicitadas por el abonado o usuario.
Statistics
Storage or technical access that is used exclusively for anonymous statistical purposes.El almacenamiento o acceso técnico que se utiliza exclusivamente con fines estadísticos anónimos. Sin un requerimiento, el cumplimiento voluntario por parte de tu Proveedor de servicios de Internet, o los registros adicionales de un tercero, la información almacenada o recuperada sólo para este propósito no se puede utilizar para identificarte.
Marketing
Storage or technical access is necessary to create user profiles to deliver advertising, or to track the user across one or multiple websites for similar marketing purposes.
