\n| \n Operating System <\/b><\/p>\n<\/td>\n | \n VMM 2008 <\/b><\/p>\n<\/td>\n | \n VMM 2008 R2 <\/b><\/p>\n<\/td>\n<\/tr>\n\n| \n Microsoft Windows 2000 Server with Service Pack 4 (SP4) or later<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Microsoft Windows 2000 Advanced Server SP4 or later<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows XP Professional with Service Pack 2 (SP2) or later<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows XP 64-Bit Edition SP2 or later<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2003 Standard Edition (32-bit x86)<\/p>\n<\/td>\n | \n Yes (Requires SP1 or later.)<\/p>\n<\/td>\n | \n Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2003 Enterprise Edition (32-bit x86)<\/p>\n<\/td>\n | \n Yes (Requires SP1 or later.)<\/p>\n<\/td>\n | \n Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2003 Datacenter Edition (32-bit x86)<\/p>\n<\/td>\n | \n Yes (Requires SP1 or later.)<\/p>\n<\/td>\n | \n Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2003 x64 Standard Edition<\/p>\n<\/td>\n | \n Yes (Requires SP1 or later.)<\/p>\n<\/td>\n | \n Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2003 Enterprise x64 Edition<\/p>\n<\/td>\n | \n Yes (Requires SP1 or later.)<\/p>\n<\/td>\n | \n Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2003 Datacenter x64 Edition<\/p>\n<\/td>\n | \n Yes (Requires SP1 or later.)<\/p>\n<\/td>\n | \n Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2003 Web Edition<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Small Business Server 2003<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Vista with Service Pack 1 (SP1)<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows Vista with Service Pack 1 (SP1)<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2008 Standard 32-Bit<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2008 Enterprise 32-Bit<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Server 2008 Datacenter 32-Bit<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows Server 2008 Standard<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows Server 2008 Enterprise<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows Server 2008 Datacenter<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Web Server 2008<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows 7<\/p>\n<\/td>\n | \n No<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows 7<\/p>\n<\/td>\n | \n No<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows Server 2008 R2 Standard<\/p>\n<\/td>\n | \n No<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows Server 2008 R2 Enterprise<\/p>\n<\/td>\n | \n No<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n 64-bit edition of Windows Server 2008 R2 Datacenter<\/p>\n<\/td>\n | \n No<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n | \n| \n Windows Web Server 2008 R2<\/p>\n<\/td>\n | \n No<\/p>\n<\/td>\n | \n Yes<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Not Got VMM?<\/u><\/strong><\/p>\nThere is a manual process to convert Virtual Server 2005 R2 SP1 VM\u2019s to Hyper-V if you do not have VMM. There are 3rd party and free tools for this. There are also 3rd party and free tools you can use to V2V from VMware to Hyper-V without VMM. However, these would be very manual processes and VMM makes that all the much easier through it\u2019s job process.<\/p>\n Destination Host Requirements<\/u><\/strong><\/p>\nThe destination machine should have the disk and the RAM to cater for the VM. MS actually recommends RAM of the VM + 256MB for the conversion process. The host should also be in a network that allows all necessary communications with the VMM server.<\/p>\n Original VM Requirements<\/u><\/strong><\/p>\nBefore you migrate any VMware machine to a Microsoft platform you must uninstall the VMware additions\/tools. That\u2019s the VMware equivalent of the Microsoft integration components\/services. You also need to remove any checkpoints.<\/p>\n Library V2V<\/u><\/strong><\/p>\nThere are then two possible ways to do the conversion. As I stated earlier, you can copy a VMware VM into the library and V2V the VM from there. To do this in VMM, choose to use the Convert Virtual Machine Wizard. You cannot V2V a VMware VM that uses raw disks (same idea as pass through disks). You need access to the .VMX file (describes the VM) and the VMDK file(s) (the virtual hard disks). Each VMDK will be converted into a VHD.<\/p>\n Host V2V<\/u><\/strong><\/p>\nIf your VM is on another host, e.g. Virtual Server 2005 R2 SP1 or VMware, then make sure the source host is being managed by VMM. You can then use an offline migration, i.e. power off the VM, right-click the VM and Migrate it. Make sure the hosts filter is adjusted to show your destination Microsoft virtualisation host.<\/p>\n Integration Components<\/u><\/strong><\/p>\nWhen the job is completing, you\u2019ll see that VMM will install the integration components\/services for Hyper-V. That will optimise the performance of the VM and cuts down on the manual labour.<\/p>\n Linux VM\u2019s<\/u><\/strong><\/p>\nInterestingly, Microsoft says<\/a> you can V2V a Linux VM. However, any OS not in the above table will not get the integration components. And remember, only certain enterprise versions of SUSE (no IC\u2019s) and RedHat (no IC\u2019s) are supported<\/a>. If you V2V a supported SLES VM you will have to manually install the Linux integration components<\/a>.<\/p>\n | |