在 更加早期的岗位我说您应该安装窗口服务器2008 RC1与亢奋V beta，如果您在窗口服务器得到错误61658，当设法安装综合化组分2003年时。

并且您应该。

但某些人仍然看见它。  如果您偶然是他们中的一个，这为什么：

您真正地大概没有安装窗口服务器2008 RC1与亢奋V beta; 您大概安装了窗口服务器2008 RC1，包含亢奋V CTP。

我不会进入原因在有之后二一起相似地名为发行，很接近，因为我未介入讨论，因此所有企图解释它是完全猜测在我的part。  不用说，我们寻找自己的情况是有有我们的beta位在它的窗口服务器有我们的老CTP位的2008年，和一。

如果您有

…

要继续我“这为什么”岗位系列，我计算我会谈论很多我们的用户跑了的其他-臭名昭著的消失的老鼠，当您设法使用一个亢奋V客人，当茶匙’ (是终端服务-时时或遥远的桌面)到主机里的d。

这情景：  您有您需要使用的VM，因此您茶匙入您的主机，发动亢奋V管理工具，连接到您的VM和设法使用它。  突然，您的老鼠不再工作，因此您设法使用CTRL ALT左箭头hotkey发布它。  那不运作。  现在您在您的主人不可能甚而使用老鼠操作系统。

如果您结束您的茶匙会议并且重新开始它，您让您的老鼠回到，但这发生，每次您设法控制您的客人。

Some of you are probably saying "Yes - that happens to me all the time, and it’s annoying!"  Others may think I’m making it up, since they’ve never

…

I’ve seen a lot of users having issues with installing the Hyper-V Integration Components on Windows Server 2003 in the last few days.  The error code seems to differ slightly, but it’s usually similar to the message below:

If you’re seeing this error message, it’s because you’re still using the Hyper-V CTP release, and the certificate that was used to digitally sign the driver catalogs for the CTP Integration Components expired back in November.

The solution isn’t very elegant - you have to install Windows Server 2008 RC1 with Hyper-V Beta. 

It’s also important to note that it is not supported to move VMs created with

…

I’ve been watching the comments - both internally and externally - about yesterday’s launch of the Hyper-V Beta (yes, I know I’m on vacation, but this is exciting to watch), and I thought I’d list the answers to a few commonly asked questions.

1. Q: How do I install Hyper-V on my 32-bit server?
   A: You don’t. Hyper-V is 64-bit only, and requires that you have an Intel or AMD processor with Virtualization extensions (Intel calls their’s VT, AMD calls their’s AMD-V).
2. Q: How do I manage Hyper-V remotely?
   A: It’s not terribly easy to do with the beta. If you’re running Windows Server 2008 with Hyper-V Beta on another machine besides your Hyper-V server, you can use the MMC Management Console to connect to your Hyper-V server remotely (which, in fact, you *must* do if your server is running Server Core).

   If you’ve only got one server, you can use Terminal Services to connect to your Hyper-V server and run the MMC Management Console - though, you’ll run into issues controlling the Virtual Machines with VMConnect if you don’t have the Integration Components installed.

   You can also use WMI calls to manage a Hyper-V server remotely. The

…

The bits are available here: http://www.microsoft.com/downloads/details.aspx?FamilyId=8F22F69E-D1AF-49F0-8236-2B742B354919&displaylang=en

There has been a lot of progress made on Hyper-V since the Tech Preview that shipped with Server RC0 and RC1. The entire system is much more stable and performant. Even better, installing Hyper-V is now a great deal easier. You no longer need to apply any hotfixes (those pesky .MSU files from RC0 and RC1) before you install Hyper-V - it’s now fully integrated into the Role Management tool from the start.

Secondly, installing Windows Server 2008 in a Hyper-V VM is now a much better experience. The Integration Components are now part of Windows Server 2008 and are installed automatically in a Hyper-V VM.

Last, but certainly not least, installation of the Hyper-V role is now available on Server Core.

I’ll post more information about the new Beta release later on, so stay tuned!

[Mike is on vacation, so posts and responses will likely be delayed.]

Those of you who have followed my blog for a while know that I’ve - for one reason or another - been referring to Windows Server virtualization by its codename, which caused some initial confusion. There’s a reason that I did this - I knew that the name was changing, and I didn’t want to send a whole lot of information out into the web with a name that wasn’t going to stick. I’m sure there were times when I actually said “Windows Server virtualization”, but I tried to keep it to a minimum.

At any rate, the product

…