Hasta el momento cubrimos los pasos necesarios para capturar una imagen del sistema con haber instalado Hiperactiva-v, y cómo instalar Windows e Hiperactivo-v al mismo tiempo sin ocuparse de imágenes del sistema en todos.

Tomemos una medida detrás y hablemos de imágenes del sistema otra vez. Las imágenes son una gran manera de desplegar una versión modificada para requisitos particulares de Windows a muchos diversos sitios de trabajo o servidores sin tener que pasar con el esfuerzo de configurar cada sistema independientemente de uno a.

Aunque usted es justo fijando Windows Vista o el servidor 2008 de Windows para arriba de un DVD, usted todavía está utilizando una imagen para hacer la instalación. Si usted mira en el DVD en \ carpeta de las fuentes, usted encontrará un archivo llamado install.wim. WIM está parado para la imagen de Windows, y es una imagen real de una instalación verdadera de Windows que la disposición aplique directamente a su impulsión dura (y entonces manipula un pedacito, pero que es una diversa historia).

Usted puede también hacer sus el propios El usar de los archivos de WIM imagex.exe herramienta ese naves con Windows AIK, que ligaré a otra vez.

La cosa fresca sobre WIMs (y hay realmente muchos, pero soy el ir justo a pegarse

Represéntelo: Sicilia, 1914. Usted tiene un manojo de los servidores en los cuales usted necesita instalar y configurar el servidor 2008 y RC0 Hiperactivo-v de Windows. Usted no se siente como ensuciar alrededor con Sysprep. ¿Qué usted hace?

¿Bien, puesto que ningunas de estas cosas existieron en 1914, usted es probablemente caja fuerte bonita, pero ésa realmente no ayuda a cualquier persona ahora, él?

Qué usted necesita, es una manera de hacer una instalación desatendida de Windows e Hiperactivo-v así que usted no tiene que sentar allí el conjunto - tiempo y tipo comandos cuando el sistema es listo para usted. 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

…