여태까지는 우리는 하이퍼 V 설치하는을 가진 체계 심상을 붙잡게 필요했던 단계를, 창을 동시에 설치하는 방법 체계 심상을 전혀 취급 없이 하이퍼 V 커버했다.

조치를 후에 취하고 체계 심상에 대해서 다시 이야기하자. 심상은 많은 다른 워크스테이션에 창의 커스트마이징 버젼을 또는 서로은 별도로 각 체계 형성의 노력을 통해 가는 것을 하기 없이 서버 배치하는 중대한 방법 이다.

비록 당신이 정당한 조정 창 비스타 또는 DVD에서 창 서버 2008 위로이더라도, 당신은 아직도 임명을 하기 위하여 심상을 이용하고 있다. 당신이 \ 근원 폴더에 있는 DVD에 보는 경우에, 당신은 파일을 불리 찾아낼 것이다 install.wim. WIM는 창 심상을 뜻하고, 체제가 당신의 하드드라이브에 직접적으로 적용하는 진짜 창 임명의 실제적인 심상이다 (와 그 때 조금을 교묘히 다룬다, 그러나 다른 이야기가) 인.

당신은 또한 당신의 자신을 만들 수 있다 WIM는을 사용하여 신청한다 imagex.exe 공구 저로 발송한다 창 AIK, 나가 다시에 연결할.

WIMs에 관하여 차가운 것 (실제로 많은 것이 있고, 그러나 나는 찌르기 위하여 정당한 가는 이다

그것을 그리십시오: 시실리 1914년. 당신은 당신이 창 서버 2008년 그리고 하이퍼 V RC0를 설치하고 형성할 필요가 있는 서버의 낱단을 가지고 있다. 당신은 Sysprep로 주변에 흩뜨리기 같이 느끼지 않는다. 당신은 무엇을 하는가?

이 것의 아무도가 1914년에 존재하지 않았기 때문에 잘, 당신은 아마 매우 안전한가, 그러나 저것은 진짜로 누군가를, 그렇지 지금 돕지 않는가?

당신이 필요로 하는 무엇을, 창의 무인 상태 임명을 하는 방법 하이퍼 V이고 그래서 체계가 당신 이 준비되어 있을 때 당신은 전시간을 거기 앉고 명령을 타자를 칠 필요없다. Lucky for you, we've already thought of that.

Before you begin, I strongly recommend that you download the Windows AIK for Windows Server 2008 and Windows Vista SP1. The AIK contains tools and documentation specifically for helping administrators just like you to roll-out Windows on a large scale. With the AIK, you'll get a nifty little tool that will help you build

Before we jump right into this, I thought it would be best if we got a few things straight.  For the remainder of this post, everytime I say "sysprep," I'm referring to running Sysprep with the /generalize switch.  This is the best way to make sure that the Windows installation image that you capture and apply to other systems actually works when you put it on those other systems.

For more details on what Sysprep with and without the /generalize switch does, I encourage you to read the documentation, which I have conveniently provided a hyperlink to.

So, you're planning to sysprep a Windows Server 2008 box with Hyper-V installed?  Good choice.  I'm sure you'll be happy with the result, but there are few things that you'll have to do to make sure Hyper-V functions properly after you apply the image to a different computer.  A KB article that

As you may have heard, we've shipped Hyper-V RC0. Sorry for the lack of posts - it seems like I'm always on vacation when we ship a major release like this, so my posts lag a few days behind.

Installing Hyper-V isn't exactly a difficult task, but if you have to do it on multiple machines, installing Windows, installing Hyper-V and then applying the RC0 patch can be a bit time consuming. The purpose of this series of posts is to offer a few different ways to help you speed up your Hyper-V deployments.

Here are the major topics I'm planning to post about:

• Sysprep and Hyper-V
• Unattended Installation of Windows and Hyper-V RC0
• Integrated Installation - The Beauty of the Win6 servicing stack

If you've got any other suggestions for topics, please let me know.

In an earlier post, I said that you should install Windows Server 2008 RC1 with Hyper-V Beta if you’re getting error 61658 while trying to install the Integration Components in Windows Server 2003.

And you should.

But some people are still seeing it.  If you happen to be one of them, here’s why:

You probably didn’t really install Windows Server 2008 RC1 with Hyper-V Beta; you probably installed Windows Server 2008 RC1, which contained the Hyper-V CTP.

I won’t go into the reason behind having two similarly named releases so close together because I wasn’t involved in that discussion, so any attempt to explain it would be pure speculation on my part.  Needless to say, the situation we find ourselves in is that there is a Windows Server 2008 that has our beta bits in it, and one that has our old CTP bits.

If you’ve yet to

…

To continue my "here’s why" series of posts, I figured I’d talk about something else that a lot of our users have run into - the infamous disappearing mouse when you try to use a Hyper-V guest while TS’d (that’s Terminal Services - or Remote Desktop) into the host machine.

Here’s the scenario:  You’ve got a VM that you need to use, so you TS into your host machine, start up the Hyper-V Management Tool, connect to your VM and try to use it.  Suddenly, your mouse doesn’t work anymore, so you try to release it using the CTRL-ALT-Left Arrow hotkey.  That doesn’t work.  Now you can’t even use the mouse on your host operating system.

If you close your TS session and restart it, you get your mouse back, but this happens each time you try to control your guest.

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

…