Azure App Service is a one-of-a-kind cloud service which allows developers to easily build employee, partner and customer-facing vApp for any platform or device.
It is an integrated solution that streamlines development while enabling easy integration with on-premises and SaaS systems while providing the ability to quickly automate business processes.
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.
The information about the Remote PCs project, the differences between ESXi and Hyper-V and virtualization of graphic station environments have been the most interesting topics during the last two weeks according to our followers.
If you didn’t have the chance to read them, you can find the links to these articles below:
Remote PCs with UDS Enterprise & OpenGnSys
If we have a look at how Microsoft Hyper-V and VMware ESXi work, we see many differences in terms of architecture. However, most virtualization administrators aren’t aware of these differences. In fact, many of them don’t really know how Hyper-V hypervisor works on the host operating system.
A very common misunderstanding about Microsoft Hyper-V is that since Windows operating system is required to install Hyper-V, it operates on the host OS instead of directly on the hardwar
