Skip to main content

Implementing Hyper-V in Windows Server 2008

Perform a Clean Installation

The first thing that I recommend doing is to perform a clean installation of Windows Server 2008. Server virtualization is extremely resource intensive, far more so than most other server applications, so I recommend using a clean Windows installation on a dedicated server.
Installing the Hyper-V Role

Now, log in using an account with local administrative privileges, and then open the Server manager. In case you aren’t familiar with the Server Manager, it’s the new tool that acts as a centralized management utility for Windows Server 2008. You can access it by entering the ServerManager.msc command at the server’s Run prompt.

When Server Manager opens, right click on the Roles container, and then choose the Add Roles command from the resulting shortcut menu. Windows will now launch the Add Roles Wizard.

Click Next to bypass the wizard’s Welcome screen and then you should see a screen similar to the one shown in Figure A, asking you which roles you would like to install. Select the Hyper-V check box, and then click Next.

You must choose the Hyper-V Role.

At this point, you will see the screen that’s shown in Figure B. Basically, this screen just tells you that you may end up needing to enable virtualization at the BIOS level prior to installing the Hyper-V roll. Some servers require this, and others don’t. The screen also tells you that after installation is complete, you can use the Hyper-V Manager to create and configure your virtual machines. The serene also contains a few links that you can use to access more information about the Hyper-V role.

This screen allows you to access more information about the role that you are installing.

Click Next, and you will be taken to a screen similar to the one that’s shown in Figure C. As you can see in the figure, your virtual machines require virtual networks in order for them to be able to communicate with other network hosts. Essentially, this screen allows you to choose the physical network adapter that you want to bind the virtual network adapter to.

You must bind the virtual network adapter to at least one physical network adapter.

You have the option of choosing multiple network adapters for load balancing, but you also have the option of using a single physical network adapter for all of your virtual machines. When you have made your selection, click Next.

You should now see a screen confirming that you are about to install the Hyper-V role, and warning you that the server may require a reboot after installing the role. Now, just click the Install button to install the role. The actual amount of time that it takes to install the role varies depending on your server’s performance, but the entire process took about 20 seconds on my server.

When the installation process completes, click the Close button, and then click Yes when you are prompted to reboot the server. When the server reboots, log back into the server and the Server Manager should automatically load and resume the installation process. After about a minute, you should see a message telling you that Hyper-V has installed successfully. Click Close to complete the wizard.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N