Finora abbiamo riguardato i punti necessari per bloccare un'immagine del sistema con Iper-v installata e come installare Windows e Iper-v allo stesso tempo senza immagini dealing with del sistema affatto.

Prendiamo una misura indietro e parliamo delle immagini del sistema ancora. Le immagini sono un senso grande schierare una versione su misura di Windows a molte stazioni di lavoro differenti o assistenti senza dovere passare con lo sforzo di configurazione dell'ogni sistema indipendentemente da a vicenda.

Anche se siete giusti regolando Windows Vista o l'assistente 2008 di Windows in su da un DVD, ancora state usando un'immagine per fare l'installazione. Se osservate sul DVD \ dispositivo di piegatura di fonti, troverete una lima denominata install.wim. WIM corrisponde all'immagine di Windows ed è un'immagine reale di un'installazione reale di Windows che la messa a punto applica direttamente al vostro azionamento duro (ed allora maneggia una punta, ma che è una storia differente).

Potete anche fare il vostri propri Usando delle lime di WIM imagex.exe attrezzo quel navi con Windows AIK, che collegherò a ancora.

La cosa fredda circa WIMs (e ci sono realmente molti, ma sono andare giusto attaccare

Descrivalo: La Sicilia, 1914. Avete ottenuto un mazzo di assistenti su che dovete installare e configurare gli assistenti 2008 e Iper-v RC0 di Windows. Non ritenete come scompigliare intorno con Sysprep. Che cosa fate?

Bene, poiché nessun di queste cose hanno esistito in 1914, siete probabilmente cassaforte graziosa, ma quella realmente non aiuta chiunque ora, esso?

Di che cosa avete bisogno, è un senso fare un'installazione incustodita di Windows e Iper-v in modo da non dovete sedere là il tempo pieno e scrivere gli ordini quando il sistema è aspettano per voi. 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

…