Hariba's Blog

MED-V – Desktop Hosted Solution

2009-02-23T08:00:00Z

Microsoft has virtualization products from Datacenter to Desktop. In the desktop space, Microsoft has two different offerings namely VDI and MED-V.

MED-V is a hosted desktop solution, an integral component of Microsoft Desktop Optimization Pack (MDOP) which is available only for the Software Assurance customers.

In VDI, the desktop VMs are installed on a centralized location (server) and accessed by desktops and thin clients by using Remote desktop protocol (RDP)

In MED-V, the VMs are installed locally on every desktop rather than on a server. Now, let's take a look at where MED-V is used against VDI

In an enterprise org, what prevent them to upgrade to the latest Operating Systems is legacy applications that are incompatible with the latest OS. With the MED-V technology, it enables the organizations to install such applications on compatible platforms (say, Windows XP or Windows 2000) and publish it to the host machines (running on Vista). End users can seamlessly access those legacy applications installed on Windows XP / Windows 2000 VPC images side by side with the native applications installed on the host machines. As a result MED-V enables such organizations to take advantage of the latest operating systems without affecting the legacy applications.

Advantages

1. It accelerates upgrades to the new operating systems

2. Enable legacy applications

3. Centralize management of desktop images.

4. Non-technical folks don't require any specialized trainings

Components Involved

1. Server

MED-V Management Server running on Windows Server 2008 Standard / Enterprise editions, should be member of a domain

Image Repository: Web server(s) based on IIS (this server contains pre defined VMs, contains OS + applications)

Database (optional): SQL Server 2005 Enterprise / SQL 2008 Express / Standard / Enterprise - For the reporting purpose.

2. Client Machines (nothing but the host machines)

Operating Systems - Windows Vista SP1 and Windows XP SP2 or SP3 (only 32 bit)

Virtual PC: VPC 2007 SP1 is required

3. Guest OS (the images reside in the VM)

Windows XP SP2 or SP3 (32bit)

Windows 2000 SP4 (32bit)

How it works

MED-V client and VPC software can be deployed by using the Configuration Manager as standard “.MSI" format or by using self service package which allows end users to download the MED-V client and VPC software over a self service website. It can be distributed thru removable Medias (CD, DVD, and USB) as well.

Once the MED-V client is installed, the Virtual image (from the Image repository server) can be retrieved over the network by using HTTP/HTTPS tunnel. VMs can be distributed thru removable Medias (CD, DVD, USB) as well along with the MED-V clients and VPC software.

When it retrieves, MED-V uses a "Trim transfer" technology which will accelerate the download speed and reduce the required bandwidth. Trim transfer is a technology which transfers only the data that was not found on the local machine.

Once the workspace (VM) is installed on the host machine then the end user can see the VM applications in the start menu on the host machine. When the user clicks on the application, it authenticates against the management server to check if any latest update found on the image repository server against the downloaded VM and executes the application.

I'm confused, how do I identify whether the physical RAM is sufficient for the number of virtual machines that I wanted to run on any given box.

2008-11-07T08:39:00Z

It's become pretty easy now. All you have to do is download the excel sheet from here. Enter the amount of physical RAM and the memory requirement for the number of virtual machines you want to run. Say, you would like to run four virtual machines with each 4GB assigned on a 32GB physical machine, the excel sheet would calculate the following things "how much memory the host need", "Hyper-V service required" and let you know the remaining physical memory.

Where do I use Hyper-V Server 2008 against Windows Server 2008 Hyper-V.

2008-10-28T10:37:00Z

Firstly, understand the limitations of Hyper-V server 2008 to find out where it can fit in.

Where there is no high availability feature is required -

Maximum number of VMs that you can run on Hyper-V box are 192 or the number of VMs are limited to 32GB physical memory.

VMs installed on Hyper-V box can only be managed thru remotely (Even a Windows Vista machine with Hyper-V manager can be used to manage the basic things)

Branch offices server consolidation

Test and development

Supported MS applications on Virtualization environments

2008-08-27T07:39:00Z

Microsoft has released the Microsoft applications support on the virtualization environments below:

Windows Server 2008 with Hyper-V (The OS with Hyper-V enabled)

Microsoft Hyper-V Server 2008 (It's a standalone SKU)

Supported partners' virtualization software (Third party virtualization products)

To see the list of supported applications, click here http://support.microsoft.com/?kbid=957006

--Hari

You can find the list of Hyper-V enabled hardware.

2008-07-22T17:55:00Z

Step - 1 Go to http://www.windowsservercatalog.com/

Step - 2 Click on "Certified Servers"

Step - 3 Click on Hyper-V under "Additional qualifications" section

Step -4 Now you can find the list of Hyper-V enabled hardware from various vendors

Cheers

Hariba

Do we have a tool to find out hardware is Hyper-V ready

2008-07-22T10:57:00Z

Yes, There are some third party tools.

Download a Securable tool from http://www.grc.com/securable.htm

Once SecurAble is running and displaying its findings, click on each of the three display sections to view specific context-sensitive information about what SecurAble has determined for each processor characteristic.

You must have a 64bit Windows Server 2008 + Hardware "Data Execution Prevention" (DEP) and Hardware "virtualization" enabled on BIOS. These BIOS settings will be available only if you have Intel-VT or AMD-V processors.