Windows 7和虚拟服务器 - 跳过一些虚拟箍！

好的，作为一个教练，我将虚拟化用作教育工具。虚拟机是完美的培训，因为学生可以实验，知道任何错误都可以迅速丢弃另一个尝试 - 远离生产系统的完美安全环境。现在许多生产服务器正在成为虚拟机，提供灵活性，故障转移和高效利用率。Microsoft的Hyper-V管理程序声明了“实时迁移”功能，允许生产VM切换到新硬件而不停止服务。这是Windows Server 2008 R2中的新功能。VMware仍然是市场领导者，但要注意微软！在苍白的比较中，我的要求是我希望虚拟化产品支持使用Virtual PC和Virtual Server构建的现有教育VM。我对Hyper-V非常感兴趣，因为它具有这种兼容性（至少对于VHD文件），但是令人默认的，以了解它仅在64位平台上传送。我正在使用Windows 7 Professional 32位，所以我的选择是什么？嗯，找出您的机器是否支持64位系统（即使您当前正在运行32位操作系统），您可以使用处理器标识实用程序，如英特尔的处理器ID实用程序。 But Hyper-V is not available with Windows 7 anyway so I would need to upgrade to Windows Server 2008 64-bit. There are other Hyper-V requirements you can check on. If you want to migrate from Virtual Server to Hyper-V there is a whole VM Migration guide for that too. Reluctantly, I decided to revert to Virtual Server 2005 SP1 especially since Microsoft Learning VM’s are fully compatible with this version regarding the courses that I teach. Yes, any new VM’s from Microsoft Learning are now fully Hyper-V compatible but I will have to wait for SQL Server 2011 before I see any that are applicable to me. OK, I’ve installed Virtual Server 2005 SP1 many times before so piece of cake, right? Wrong. Much as I love Windows 7, it actively blocks the install of Virtual Server 2005 SP1. So I was caught between a rock and a hard place – or specifically between Windows 7 and Virtual Server. Now Google and Bing are just brilliant, but often you have to sift out the poor quality forum entries from the well crafted, accurate and knowledgeable blog entries. I found a great step-by-step solution that involves a few registry hacks but ultimately worked like a charm and even has a solution for the infamous Microsoft Learning “Lab Launcher”. It is a blog entry by MVP Thomas Lee whose blog is branded “Thomas Lee's collection of random interesting items, views on things, mainly IT related, as well as the occasional rant”. The blog entry is titled: “Windows 7 and Virtual Server”. Thanks Thomas! http://tfl09.blogspot.com/2009/08/windows-7-and-virtual-server.html Now I must get into Hyper-V but I’ll jump through those virtual hoops a little later! Cheers, Brian.