- The Unofficial M365 Changelog
- Podcasts Toggle children
- Enterprise Dish
- M365 Knowledge
- MJF Chat
- Petri Dish
- Resources Toggle children
Prepare Your Windows Server 2008 R2 for Hyper-V Role
Update Hyper-V Hosts
Installing Hyper-V on Windows Server 2008 R2
To install Hyper-V on Windows Server 2008 R2 you can use one of the following approaches. Note that all methods require a reboot after completion.
Important note: This article does NOT deal with the tasks required to pre-configure the Hyper-V host itself. For that, please read my Prepare Your Windows Server 2008 R2 for Hyper-V Role article.
Method #1 – Through the GUI
Probably the easiest for this specific role. I would use this method.
1. Open Server Manager, wait for it to load.
2. Click on “Roles”, wait for it to load.
Subscribe to Petri Newsletters This Week in IT
! Already a Petri.com member? Login here for 1-click registration.
3. On the “Before you begin” page, click “Next”.
4. In the “Select Server Roles” page, click to select the Hyper-V role. Click “Next”.
6. Select all the Network Interface Cards (NICs) that you wish to assign for the Virtual Machines. Make sure you leave one NIC un-selected for host management. If you only have one NIC, select it, but make a note that it is best to have at least 2 NICS – one for the host and one for the VMs. These settings can be changed later.
7. In the “Confirm Installation Selections” page click “Install”.
8. One finished, you will need to reboot the server. Click on the “Close” button, and then click “Yes” when you are prompted to reboot the server.
9. 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.
Note: Make sure you do not forget to enable the CPU Virtualization Mode and the Execute Disable bit. Again, read my Prepare Your Windows Server 2008 R2 for Hyper-V Role article. If you fail to do so, you will receive an error when attempting to start a VM.
Method #2 – Using the Command Prompt
Using the servermanagercmd.exe command is easy, and only requires 3 words… A reboot is required at the end of the installation (which can also be added to the command, making it 4 words…). However, Hyper-V network connections will need to be changed after the installation.
1. Open a Command Prompt window with elevated permissions.
servermanagercmd -i Hype-V
If you want to automatically reboot the server when the installation is finished, type:
servermanagercmd -i Hyper-V -restart
Easy and simple. This is probably why Microsoft decided to deprecate the usage of servermanagercmd.exe… 🙁
Method #3 – Using PowerShell
In Windows Server 2008 R2, PowerShell is installed by default. However, in order to install roles with it, you need to import the Server Manager module.
1. Open a PowerShell window and type:
2. Once imported, type:
If you want to automatically reboot the server when the installation is finished, type:
Add-WindowsFeature Hyper-V -restart
Easy and simple, but here too, Hyper-V network connections will need to be changed after the installation.
Just for Share
Windows Server 2008 R2 and later releases of the product ship with a virtualization platform called Hyper-V, which works quite well since it’s built into Windows. Today we’re going to show you how to install it.
Note: this is part of our ongoing series teaching IT administration basics, and might not apply to everybody.
- An x64-based processor. Hyper-V is available in x64-based versions of Windows Server 2008—specifically, the x64-based versions of Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datacenter.
- Hardware-assisted virtualization. This is available in processors that include a virtualization option—specifically, Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V).
- Hardware-enforced Data Execution Prevention (DEP) must be available and be enabled. Specifically, you must enable the Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).
Launch the Server Manager, by clicking on the pinned icon or using the Start Menu.
When the Server Manager launches, right-click on roles and select Add Roles from the context menu.
Click next on the Before You Begin screen.
Now select Hyper-V from the list of available roles and click next.
Click next to skip past the Introduction to Hyper-V, now select the network adapter that you want to use to create a virtual network for your virtual machines, then click next.
You will be asked to confirm that you want to install Hyper-V, just click the install button to kick off the installation.
When the installation is complete you will be told that you need to restart the server, you can do so by clicking on the link.
When your server has restarted you will be able to manage Hyper-V from Server Manager under the roles node, you can also manage it by launching a dedicated Hyper-V MMC from the Administrative Tools section of the Start Menu.
Want to improve this question? Update the question so it’s on-topic for Server Fault.
Closed 8 years ago .
I have one computer that running windows 7 and want to have a Dev Environment running on this machine.
I tried to install Windows Server 2008 r2 with Hyper-V role on a VirtualBox virtual machine, but I can’t get this role to be installed, since it’s need a raw access to the processor.
My goal is to have a virtualized windows server that running Hyper-V, that I can install on it all the machines that I want to have in my environment: 2 IIS servers, 1 SQL Server, Load Balancer, and build server.
Can I get a little help from you guys, to help me achieve this?
3 Answers 3
Simple: by getting rid of the illusion that you can do that.
A Hyper-Visor needs raw hardware access. So, it can not run virtualized. Get usedto it.
What you CAN do is install WIndows Server in a VHD file and then boot from that instead your Windows 7.
My goal is to have a virtualized windows server that running Hyper-V,
When deluisions meet reality, reality wins. Reality says: Hyper-V does not run within a virtual machine.
- Boot into Server 2008 R2 installed in Hyper-V
- Dump Windows 7. Install Server 2008 R2 and use that as primary operating system. You CAN make it behave and look like a Windows 7 install.
I personally do – depending what I do:
- Develop in a virtual machine on a number of larger virtualizing servers
- Use my own workstation to boot into a vhd mounted server 2008 to use virtualiaztion there (mostly for training – allows me to show off a domain without bringing more than a little cube with 16gb RAM).
Today I decided to build my lab environment from scratch just so that everyone here will be able to follow up on things that I will be building in future.
Lets get back to the basics, so what have I done here? I just installed a Windows Server 2008 R2 on my PC from the ISO image that I had and went through the Initial Configuration task window and made sure that all the updates were installed and my machine was upto date. I also set a static IP address for my machine. You can do that from Network and Sharing center.
The next step was to install the Hyper-V role on the Server so that I can spin up some virtual machines and do some useful tutorials in the coming days. Hyper-V in Windows Server 2008 and Windows Server 2008 R2 enables you to create a virtualized server computing environment. Each virtual machine is a virtualized computer system that operates in an isolated execution environment. This allows you to run multiple operating systems simultaneously on one physical computer.
Since you are here, you must be knowing that Windows Server 2008 R2 is very modular in design and I can install specific roles and features on a single machine. It comes with 17 server roles and 42 features.
Anyways lets get installing the Hyper-V role.
Go to Start > Server Manager > Add roles.
Add role installation wizard comes up. It gives you the basic overview as to what this wizard does. Click on Next.
Select the Hyper-V role from the next step and click on Next.
On the next page, it will give a brief overview of what the Hyper-V role is and what you can achieve with it. Click Next.
On the next page, it will ask you to select a virtual network, go ahead and select your LAN connection. In my case, I just have one NIC card, so I have selected that.
Now you are on the confirmation page, go ahead and click on the Install button.
Once the installation is complete, it will ask you to restart the machine for the changes to take effect.
After the server reboots, it automatically continues to the remaining part of the installation here it configures the services. Once it is complete, click on Close.
There you go! You have successfully installed the Hyper-V role and you can access the Hyper-V Manager console from either the Server Manager or from the Administrative tools from the Start button. You can spin up as many virtual machines you want and play around now.
Hope this was informative and do leave your comments. Any suggestions are always great! Thank you again for reading.
I am Adil Arif, working as a Senior Technical Support Engineer at Rubrik as well as an independent blogger and founder of Enterprise Daddy. In my current role, I am supporting infrastructure related to Windows and VMware datacenters.
Vembu has a new offering – Vembu BDR Essentials
How to Install Project Honolulu on Windows Server 2019 Tech Preview
How to Install Windows Server 2019 Tech Preview in Azure
Very nice! Thank you for taking the time to publish this. I am an aspiring system administrator keep up the great work!
Thank you! Keep visiting for more articles on System Administration!
Iam new to this administration world pls suggest from where to start as iam working as helpdesk support, to grow as a system admin on server 2012 . pls give me some notes ..thank you
There are a lot of resources available online. You just have to get to it and start learning.
You can find the below link to Microsoft Virtual Academy, which is a great learning site.
I am upgrading a client’s 2003 Terminal Server soon and they still need to run a 16 bit DOS app. I know R2 won’t support this, but would prefer to use it anyway if there was a way around it via virtualization.
Would it be possible to install a 32bit guest OS to run the 16 bit app, and have the remote desktop sessions run the app using Remote App? I’ve not used Hyper-V before, so am unsure about this whole area. What are the licensing requirements?
Will probably be going with a dual-proc quad-core machine, I would presume this should be more than enough to handle around 10 remote desktop sessions making use of this 32bit OS?
3 Answers 3
I’m not sure if I’m reading what you’re describing correctly; if you virtualize the system, you’d be running an older version of Windows within the terminal server and having them connect to that older version in order to run the app from within.
I’m not even sure it’s recommended that you run virtualization within a terminal server for multiple users. Things like Hyper-V are meant to create a dedicated virtualization server (i.e., a hyper-V server running a mail server, DNS server, etc., not a terminal server virtualizing sub-sessions. That’s what the Win32 sub-system is basically for).
If you’re going to get the server, hyper-v it, then run a terminal server within it as a guest with an older version of Windows, I’m not sure what you’re standing to gain in doing that unless you’re migrating other servers or consolidating on the same hyper-v server. You’d be taking a performance hit that needs to be offset by the advantages of adding other servers to the same hyper-V server.
What you might be able to do is install virtualbox and see if you can run a version of DOS (like FreeDOS) within their session, if the application will run in it. Or an older version of DOS. You would have to test it to see if that is compatible with multiple sessions, though, as you may need to tweak access to hardware settings to make sure Windows doesn’t crash or the Virtualbox session doesn’t crash.
I might just be confused though. It’s early in the morning right now. but depending on what you’re going to be adding to the hyper-v server additionally, I’d first test Virtualbox for individual sessions.
How-To: Installing Windows Virtualization Services (Hypervisor) on Windows Server 2008 RC0
Windows Server 2008 RC0 is out and available to download, peeps. Burn it to a DVD, find a spare machine and have at it.
It was a little confusing for me to find my way around, download, get a product key, etc, so here’s what worked for me.
Note that I’m not involved with that group, so this is GEEK TO GEEK. For official stuff, visit the Virtualization Team’s blog. My stuff may be wrong and isn’t meant to replace the docs. No warranty, your mileage may vary, no complaints taken. 😉
Download Windows Server RC0
- Go to the Download: Windows Server 2008 RC Site to get your Product Key.
- You’ll be sent to a Shopping Cart looking dealie, but everything is $0. Proceed to “buy” the $0 copy and make note of your Product Key. I recommend the “Enterprise” version. I got the 64-bit one.
- You can download the ISOs directly from the bottom of this page. You can skip entering the Product Key, but you’ll need it within a month if you keep going, so regardless of what order you do things, hang on to your key. Make sure you notice if you’re getting the x86 version or the 64bit version.
- Downloading slow or unreliable? Try GetRight. Works great for slow connections, downloads in parallel and generally kicks. They don’t know me, and they don’t pay me, but they are awesome.
- Burn to a DVD. I use ImgBurn now exclusively and it’s wonderful. Works on 64-bit also. More on DVD Burning in another post.
One of the big cool things in WS2008R0 is Virtualization Stuff built in to the OS as a “Server Role.” You can add the role to an WS2008 Installation or to a “Server Core” (read: uber-minimal) installation for maximum CPU going to the VMs.
When the product is released, you’ll probably be able to go “Check for Roles” and get a list of other roles for your server to download and install. However, not in this RC0 that I can see, so it can be a little roundabout.
Initially if you click Add-Roles, there will be a bunch of Roles but not Virtualization. As an aside, I really like the whole “Roles” metaphor. It really works for me and my workflow. I want this machine to be a print server, that one a file server and virtualization server, etc.
It’s cool because you say “I want this machine to host Applications” and you’ll get a dialog like this. It shows a description, and “What are these features required.” It really sets the bar high when it comes to integrated documentation. I think that more and more apps (certainly ones I write) will have features like these “what the heck is going on” hints at every step of the way.
And, since you’re in a wizard, as you add Roles, you’ll see the new Wizard Steps added dynamically to the list on the left. It’s a great UI metaphor, IMHO.
Anyway, I digress. here’s how to get the Virtualization Role.
Do note that the Virtualization Role is a Preview Release and a separate install (as we saw) from the RC0 of Windows Server 2008 itself.
Enabling Virtualization for Windows Server 2008 RC0
Details about the “Virtualization Role” are here. Make sure you have the prerequisites:
- x64 base Processor with Hardware-Assisted Virtualization (VT) technology. Most newer CoreDuos and AMDs and Xeons have this.
- For my installation, I’m using a Dell Precision Desktop Xeon 5150 with 4GBs of RAM running 64-but 2008 Enterprise.
- DEP (Data Execution Protection) turned on by default (it is in this RC)
- Buttloads of RAM
- Optionally Recommended: Two network cards, one for the Virtual Machines, and one for Remote Administration.
After you’ve installed Windows, go to C:\windows\wsv and install the two files you’ll find there.
Next, go to the Server Manager and Add Roles and you’ll see “Windows Server Virtualization” has been added to the list. Note the pre-release warning so you’re on your own, OK?
Some wizard steps and a reboot later, you should have Windows Server Virtualization in the Roles Tree to the left of the Server Manager. Note that there are still a few steps and you need to drill into the Tree into Virtualization Services to setup your VHDs.
GOTCHA NOTE: You might get an error saying “The virtual machine could not be started because the hypervisor is not running.” That can be a little confusing, but the dialog has three things you can confirm in order to get things going.
In my case, I had forgotten that most machines ship with the VMM (Virtualization) hardware bit turned OFF by default. You’ll have to go into the BIOS and turn it on. Note also that you’ll often need to CUT POWER COMPLETEY after you’ve flipped the bit. a soft reboot doesn’t always work.
So, into the BIOS, cut power, reboot, loading back up, and.
BETA GOTCHA NOTE #2: After you load up the Virtualization Services MMC Console and start up a machine you might get an error when you try to “Connect” to the machine. The machine is running, you just can’t see it and the message is “Your credentials did not work: [snip]. does not allow the user of default credentials to log on to the remote computer. “.
This can be fixed in one of two ways (I’m sure it’s already fixed in newer builds, so for now it’s just an obscure edge case for me):
1. Try running vmconnect out of c:\program files\windows virtualization as an elevated command prompt.
2. run “net stop vmms” then “ipconfig /release” then “net start vmms” then “ipconfig /renew” and run vmconnect. Some certificates or something aren’t lining up, probably because I’m on a Workgroup, not a Domain.
That’s pretty much it.
A couple gotchas (this always happens to me. it’s karma) but otherwise very smooth and easy. It’ll be even easier when you can just pull the Virtualization Role out of the Cloud and double click. All in all, a good clean install so far. I’ll start working with my VMs off this machine and report my findings back to you Dear Reader.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
Starting with Windows Server 2008 Microsoft entered in the era of true Windows server virtualization with Hyper-V. Hyper-V is a level 1 virtualization software from Microsoft. I sad level one because it work directly with the hardware, meaning there is no operating system between Hyper-V and the hardware (this are also known as Hypervisors). Level two virtualization software is running on top of the operating system (VMware Workstation, Virtual Server, Virtual PC etc). For a better understanding a think a picture might help.
Before we proceed with the installation the hardware must meet the minimum requirements, and I’m not talking specifically about RAM and CPU, witch are very important, I’m talking about the Virtualization Technology that the CPU must support. This technology improves the performance of the hypervisor allot, and if your processor does not support it, an info box appears just before Hyper-V installation.
But with now days hardware I don’t think this is going to be a problem since almost all processors support this technology. If you want to see if your processor supports Virtualization Technology you can check using this application. For detailed information about minimum system requirements for Hyper-V click here.
To start installing Hyper-V just open Server Manager by going to Start > Administrative Tools > Server Manager. Here right click Roles and choose Add Roles. Click next to pass the initial page. On the second page of the wizard we can see all the roles that can be installed, but we are interested only of Hyper-V. Check the box next to the Hyper-V role then hit Next. The page that come after is just an information page witch I’m going to skip, but if you want to read more about Hyper-V just click the links on the page.
The Create Virtual Networks screen is where you create the networks, so that virtual machines can communicate with your part of the lan. Think of this virtual network as a real switch that connects devices. You simply attach the network card from a virtual machine, or multiple virtual machines to this virtual network and you created a LAN. In this case I am going to choose just LAN to create the virtual network, because the other one is for management only, not required, but recommended.
Now just click the Install and setup wizard will copy the necessarily files for the next part of the installation. At the end just click the Close button then OK when the message pops-up to reboot the server and continue with the installation.
After reboot another wizard appears that configures the Hyper-V role, so don’t start using the server until this wizard finish his job.
The lest step is to see if we got Hyper-V installed, and for that we need to go to Start > Administrative Tools > Hyper-V Manager or just open Server Manager and expand roles.
As you can see installing the Hyper-V role is a straight forward process that any junior admin can do, without any headache.
Want content like this delivered right to your
This is purely a licensing limit. And only controls the number of included licenses that come with Enterprise Edition. You can install as many VMs as your hardware supports, Enterprise doesn’t care. But if you install more than 4 copies of Windows Server then you’ll need to buy licenses for the additional virtual machines.
- Proposed as answer by Peter Forster Saturday, June 19, 2010 8:46 PM
- Marked as answer by John Paul Cook Sunday, June 20, 2010 5:32 PM
Every post so far is correct, but the complete story has not been told yet.
Technically all versions of Hyper-V allow as many virtual machines as the hardware can support. There are licensing limits. Here is the best explanation of licensing I’ve found: http://blogs.technet.com/b/mattmcspirit/archive/2008/11/13/licensing-windows-server-in-a-virtual-environment.aspx
Here is a very important point that many people miss: Standard edition grants you a license for one server operating system. Enterprse edition grants you a license for four server operating systems. If you want to run a desktop operating system in a vm, it will have to have its own license. You can’t have Enterprise runing Hyper-V and claim that the license covers, for example, three server vms and one desktop vm.
Notice from the provided link that you can assign virtual license rights from one physical server to another. You can reassign licenses provided you don’t reassign within 90 days of the previous reassignment. License reassignment means that you might not have to purchase additional licenses depending on how your running vms are allocated.
Notice that I emphaized running virtual machines. You can have more than four server vms on a copy of Enterprise and as long as no more than four are running at any given time, you will be in license compliance.
Even if you are in license compliance, you still have to activate your virtual machines. You may find yourself needing volume licensed media to make it practical to activate a bunch of vms.
If you put four running virtual machines on Enterprise and you want to run a fifth vm that is 2003 Server and you happen to have some unused 2003 Server licenses, you can use those licenses. You don’t have to use only the license rights that come with 2008 Server.
Hyper-V is one of the hardware virtualization technology used in the industry. This is based on hypervisor and one of the important features of Windows Server 2008. it offers a flexible, reliable and highly powerful virtualization platform.
It also offers a ability to manage various things by using the features like quick migration of the physical servers to the hyper-v virtual machines and another physical hosts, possible to integration with SCVMM (ie. System Center Virtual Machine Manager).
Lets, begin with the installation process of hyper-v on windows server 2008. Before starting with the installation procedure make sure you have the following required things.
Requirements for Installing Hyper-V:
Hyper-V required following Specific requirement to run.
1) x64-based Processor: The hyper-v can only be installed on the x64-based versions of Windows Server 2008, which are Windows Server 2008 Standard, Enterprise and DataCenter Edition.
2) Must have a processor that consists of virtualization options enabled or the HAV should be enabled in the BIOS. The Intel VT and AMD Virtualization includes such options. Along with the HAV, the Data Execution Protection should also be enabled in the BIOS. Make sure you enable the Intex XD bit or AMD NX bit.
Step 1: Click Start —–> Server Manager.
Step 2: Left side you will find the Role Section, Click On Roles.
Step 3: Roles page will open seperately, Click on Add Roles on the right side to add the Hyper-V role.
Step 4: Now the Add Role Wizard will open, Click Next to Continue.
Step 5: In the list you will find the Hyper-V, Select Hyper-V and Click Next to continue.
Step 6: The following screen will the introduction for the Hyper-V, if you like read it. Otherwise click Next to continue.
Step 7: You can create connections to a whole network simply by clicking one or more network adapters on the “Create Virtual Networks” window. It is recommended to have at least two network adapters, which can be used for different purposes. One for virtual network and another for server management.
it does the following.
- Communications between virtual servers only.
- Communications between the virtualization server and virtual servers.
- Communications between a virtual servers and a physical network by creating an association to a physical network adapter on the virtualization server.
Step 8: Click on Install to start the installation Hyper-V.
The following screen shows the initialzing the installation of Hyper-V.
Step 9: Once the intialization is completed it will prompt you to reboot the server. Clic Yes on the Reboot window.
Step 10: Once the machine reboot, log in with your credential. The server manager start to resume the installation automatically.
Step 11: Once the installation is over, click close on Result window.
Now the Hyper-V successfully installed on Windows server 2008.