It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

Step 2: Left side you will find the Role Section, Click On Roles.

It how to install hyper-v virtualization on windows server 2008 r2

Step 3: Roles page will open seperately, Click on Add Roles on the right side to add the Hyper-V role.

It how to install hyper-v virtualization on windows server 2008 r2

Step 4: Now the Add Role Wizard will open, Click Next to Continue.

It how to install hyper-v virtualization on windows server 2008 r2

Step 5: In the list you will find the Hyper-V, Select Hyper-V and Click Next to continue.

It how to install hyper-v virtualization on windows server 2008 r2

Step 6: The following screen will the introduction for the Hyper-V, if you like read it. Otherwise click Next to continue.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

Step 8: Click on Install to start the installation Hyper-V.

It how to install hyper-v virtualization on windows server 2008 r2

The following screen shows the initialzing the installation of Hyper-V.

It how to install hyper-v virtualization on windows server 2008 r2

Step 9: Once the intialization is completed it will prompt you to reboot the server. Clic Yes on the Reboot window.

It how to install hyper-v virtualization on windows server 2008 r2

Step 10: Once the machine reboot, log in with your credential. The server manager start to resume the installation automatically.

Hello,
I am trying to install Hyper V on Windows 2008 Sever R2 (x64) as a part of installing Team Foundattion Server (VSTS 2010 RC Ultimate Edition)on the machine, the issue I am having with Hyper V is that I can’t configure it on server, whenever I try to install it (through ‘Add Roles’) on server, I get “Hyper-V cannot be installed The processor on this computer is not compatible with Hyper-V. To install this role, the processor must have a supported version of hardware-assisted virtualization, and that feature must be turned on in this BIOS.”

I am running Windows Server 2008 R2(x64) as a virtual machine in HyperV, so I am installing Hyper-V in a mahcine which is being run through Hyper-V. Also because it is a virtual machine, i can’t access the BIOS setting (setting that lets us enable/disable the virtualization) but that base machine on which the Windows Server 2008 R2(x64) is running, has Vitualization enabled.

Should I be able to install Hyper-V in a machine which is running on Hyper-V, or this cannot be done.

  • Moved by YiChun Chen Tuesday, March 2, 2010 7:10 AM It’s Hyper-V issue (From:Visual Studio 2010 Install and Setup)

Answers

It seems that you want to enable Hyper-V role inside a VM, if so, it’s impossible. Hyper-V is a hardware virtualization technology, and it can only be running on a physical computer.

  • Marked as answer by Vincent Hu Wednesday, March 3, 2010 9:00 AM

As Vincent mentions, you cannot enable the Hyper-V Role in a VM.
(the hypervisor needs to own the hardware – in a Vm this is not possible)

If you require the Hyper-V Management Console – that is installed under the Remote Administration _Feature_ .

Brian Ehlert (hopefully you have found this useful)

  • Marked as answer by Vincent Hu Wednesday, March 3, 2010 9:00 AM

All replies

It seems that you want to enable Hyper-V role inside a VM, if so, it’s impossible. Hyper-V is a hardware virtualization technology, and it can only be running on a physical computer.

  • Marked as answer by Vincent Hu Wednesday, March 3, 2010 9:00 AM

As Vincent mentions, you cannot enable the Hyper-V Role in a VM.
(the hypervisor needs to own the hardware – in a Vm this is not possible)

If you require the Hyper-V Management Console – that is installed under the Remote Administration _Feature_ .

Brian Ehlert (hopefully you have found this useful)

  • Marked as answer by Vincent Hu Wednesday, March 3, 2010 9:00 AM

m face same issue, plz help me

Irshad Ahmed MCS-MCSE-MCITP-MCTS-MCP-CCNA

Well you can cheat it in to get the management interface available in a VM.

Usely I do it from Scvmm, just add the server as a Hyper-V and it will install the role for you, but I quess the powershell commands will work

Start Powershell and type in the following commands:

1. Import-Module servermanager

2. Add-WindowsFeature Hyper-V

Use this if you want it to automaticly reboot
2. Add-WindowsFeature Hyper-V -restart

This article describes an update for the latest integrated components for Windows virtual machines (VMs) that are running on a Windows 10-based or Windows Server 2016-based host, or a Windows Server 2012 R2-based host. This update is available on Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 Service Pack 1 (SP1)-based Hyper-V guest. Before you install this update, check out the Prerequisites section.

Issues fixed in this update

Consider the following scenario:

You connect a VM to a virtual switch that uses a physical adapter.

You enable the single-root I/O virtualization (SR-IOV) option in Virtual Switch Manager.

You disable the physical adapter on the Hyper-V guest while network I/O is running on the VM.

In this scenario, the VM crashes.

The current Write Ahead Logging (WAL) implementation incorrectly assumes that the Virtual Hard Disk (VHD) ownership never changes. However, the ownership does change in multiple VM group replication in a shared VHD scenario.

How to get this update

You can get this update through Windows Update and the Microsoft Download Center. Even though this issue has only been observed in Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 SP1, the update also applies to Windows 8.1 and Windows 7 SP1.

Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Method 1: Windows Update

This update is provided as a Recommended update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.

Method 2: Microsoft Download Center

The following files are available for download from the Microsoft Download Center.

All supported x86-based versions of Windows 8.1

Download the package now.

All supported x64-based versions of Windows 8.1

Download the package now.

All supported x64-based versions of Windows Server 2012 R2

Download the package now.

All supported x64-based versions of Windows Server 2012

Download the package now.

All supported x86-based versions of Windows 7

Download the package now.

All supported x64-based versions of Windows 7

Download the package now.

All supported x64-based versions of Windows Server 2008 R2

Download the package now.

Note This download is not self-installing. Please see Managing Hyper-V Integration Services for guidance on how to manage and install integrated components. To start the download, click the Download button.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Update detail information

Prerequisites

Registry information

To use the update in this package, you don’t have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this update.

Update replacement information

This update doesn’t replace a previously released update.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Microsoft puts its forthcoming shift in context as it outlines major changes to its partner programme

Skills has been a problem for a long time, and it’s led to Billy MacInnes wondering if it can ever be sorted

SAP cloud specialist explains the process it went through in settling on a multicloud strategy

Security teams are beefing up enterprise defenses as cloud services become more essential. Zero trust — tailored to assets, as .

A popular JavaScript package was sabotaged by its developer and seeded with messages in support of Ukraine in what has become a .

Trend Micro discovered that the Cyclops Blink botnet, which had originally targeted WatchGuard devices, is now spreading to Asus .

Consider several SSD performance benchmarks, including SSD response time as a key unit of measurement. Also, note the difference .

Kioxia unveils its second-generation 24G SAS SSDs, the PM7, building off its previous generation to provide added performance and.

The Quantum Scalar i6H, along with the Quantum RAIL architecture, enables hyperscalers and enterprises to use tape in a scale-out.

Cradlepoint and Extreme Networks will combine the former’s 5G routers with the latter’s network fabric to build a 5G wireless WAN.

Israeli startup OneLayer has launched from stealth with $8.2 million in seed funding and a software-based platform to secure IoT .

The Russia-Ukraine war, which affects everything from inflation to chip availability, has left half of enterprise tech leaders .

To achieve high availability and fault tolerance in AWS, IT admins must first understand the differences between the two models.

Amazon ECS and EKS are similar, but their differences are enough to set them apart for AWS users. Learn which best fits your .

New storage additions such as Flexible Block Volumes and high availability for ZFS grow Oracle’s cloud platform to compete .

Snowflake is continuing to build out its industry vertical platform offerings, helping users in different market segments collect.

The RKVST platform supports multiple types of blockchain data applications, including secured SBOM data sharing for cybersecurity.

Data privacy laws are changing around the world on a constant basis. These 10 elements can help keep organizations up to speed .

Metadata gives context to data, and during crises like the war in Ukraine when it’s difficult to know what news to trust, context.

Using the BI vendor’s platform, the healthcare marketing and CRM firm has improved speed to insight and increased customer .

Organizations looking to maximize BI use may consider constructing a business intelligence team consisting of four key roles — .

One of the great things about working at a backup appliance vendor is that you find yourself involved with a tremendous number of technologies. Recently, I had a partner ask about Microsoft Hyper-V – in particular the differences between Hyper-V Server 2008 R2 and Windows Server 2008 R2 Server Core with a Hyper-V role only.

Hyper-V exists in essence as two fundamental offerings: a stand-alone product called Hyper-V Server 2008 R2 and as part of Windows Server 2008 R2.

Hyper-V Server 2008 R2

Hyper-V Server 2008 R2 is a variant of Windows Server 2008 Core that includes full Hyper-V functionality with no other Roles possible and with limited services available. Only a command line interface is available; the way that you do management and monitoring is by downloading extended Management Consoles that are installed on another Windows system and by using remote Windows desktop RDP sessions via a command line interface or redirected standard management consoles (MMC).

Hyper-V Server 2008 R2 is free and is primarily positioned by Microsoft to compete against VMware vSphere 4 ESXi’s free version.

Windows Server 2008 R2 with a Hyper-V Role Only

Windows Server 2008 R2 is a licensed product (i.e., you pay money for it) that allows you to run the full version of Enterprise or the Core version of Enterprise and four server (not desktop) versions of Windows Server 2008 R2 (or earlier versions of Windows Server.) Windows Server 2008 R2 has the concept of Roles: one role is Hyper-V. Running a Hyper-V role only refers to using Windows Server 2008 R2 in its Core mode with only the Hyper-V role enabled.

One major advantage to running Windows Server 2008 R2 Core is that you get a license for either one or four Windows Server virtual machines. If you buy Microsoft Windows Server 2008 Standard you get one a licence for one Windows Server virtual machine; if you buy Windows Server 2008 Enterprise you get a license for four Windows Server virtual machines.

The big difference between Hyper-V Server 2008 R2 / Windows Server 2008 R2 Core and Windows Server 2008 R2 Standard / Enterprise is the GUI in the latter. For example, if you want to run anti-virus software, it’s typically easier to find products that work on standard/enterprise than it is to find products that work on Hyper-V server or Core.

Postscript

Is this complicated? Heck yes. This is the reason that Unitrends has its No Limits licensing scheme – to avoid all of this complex licensing stuff.

Hyper V has been in demand when it came into the existence, being a Microsoft product it had a greater value and came up with real good features and enabling the acquaintance with the hosting environment. Hyper-V Server 2008 R2 is the stand alone product of Microsoft. It provides a solution which is reliable and optimized virtualization solution enabling organizations to improve server utilization and reduce costs. It has the compatibility to plug into customers’ existing IT environments, leveraging their existing patching, provisioning, management, support tools, processes, and skills. As this is the only dedicated stand alone product, this has some unique adaptability of containing the Windows Hypervisor, Windows Server driver model and virtualization components, it provides a small footprint and minimal overhead. It has many key features which makes it a different product like live migration, cluster shared volume support and expanded processor and memory support for host systems.

Following are the system requirements for Microsoft Hyper-V Server 2008 R2 :

Supported Operating Systems:

* Windows Server 2008 R2 Standard
* Windows Server 2008 R2 Enterprise
* Windows Server 2008 R2 Datacenter
* Windows Web Server R2 2008

Processor : x64 compatible processor with Intel VT or AMD-V technology enabled.
Hardware Data Execution Prevention (DEP), specifically Intel XD bit (execute disable bit) or AMD NX bit (no execute bit), must be available and enabled.

Minimum CPU speed: 1.4 GHz; Recommended: 2 GHz or faster.

RAM: Minimum: 1 GB RAM; Recommended: 2 GB RAM or greater (additional RAM is required for each running guest operating system); Maximum 1 TB.

Available disk space: Minimum: 8 GB; Recommended: 20 GB or greater (additional disk space needed for each guest operating system).

DVD ROM drive

Display: Super VGA (800 × 600) or higher resolution monitor.

Other: Keyboard and Microsoft Mouse or compatible pointing device.

One of the important factors are that, the actual system requirements will vary based on your system configuration and hosted guest operating systems.

After you have enabled the Hyper-V role on Microsoft Server 2008 R2 and extracted the VPX files, you can use Hyper-V Manager to install SD-WAN VPX. After you import the virtual machine, you must configure the virtual NICs by associating them with the virtual networks created by Hyper-V.

Note: You cannot change any settings while the virtual appliance is running. Shut down the virtual appliance and then make changes.

To install SD-WAN VPX on Microsoft Server 2008 R2 by using Hyper-V Manager

  1. Unzip the SD-WAN distribution that you downloaded from My Citrix.
  2. Start Hyper-V Manager.
  3. In the navigation pane, under Hyper-V Manager, select the server on which you want to install SD-WAN VPX.
  4. On the Actions menu, click Virtual Switch Manager.
  5. In the Import Virtual Machine dialog box, in Location, specify the path to the folder that contains the Branch VPX SD-WAN files.

Note: If you received a compressed file, make sure that you extract the files into a folder before you specify the path to the folder.

  • In the Settings window navigation pane, under IDE Controller 0, select Hard Drive.
  • Click Edit.
  • Follow the steps in the Edit Virtual Hard Disk Wizard to increase the allocation to one of the supported sizes, using the Expand option in the wizard.
  • In the Settings window’s navigation pane, under Hardware, select Memory.
  • Allocate the RAM space by adjusting the memory to one of the supported sizes.
  • Click OK.
  • Right-click the virtual machine, and then click Settings.
  • In the Settings window navigation pane, under Hardware, select Add Hardware.
  • Select Network Adapter from the list of devices, and then click Add.
  • Name the new virtual network as Primary Network 3.
  • Make sure the Enable spoofing of MAC addresses check box is selected.
  • Click OK to apply the changes.

In the file menu, click Action, and then click Start to start the virtual machine.

More configuration

For more configuration instructions, see the documentation for physical SD-WAN and SD-WAN appliances.

Upgrading to a previous release

The software upgrade mechanism built into physical SD-WAN appliances is also supported by SD-WAN VPX. Alternatively, you can install a new virtual machine running the desired release.

In this two parts article , I will show you how to install the Hyper-V role and then in part two I will install Windows Server 2008 as a virtual machine with Hyper-V.

Hyper-V requires specific hardware. You will need the following:

  • An x64-based processor. Hyper-V will be available only in the x64-based versions of Windows Server 2008, 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 VT or AMD Virtualization
  • Hardware Data Execution Protection (DEP) must be available and be enabled. Specifically, you must enable Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).

Before installing Hyper-V, let me show you a table that will summaries the differences between Hyper-V and Virtual Server 2005 R2

Hyper-V Virtual Server 2005 R2
Performance / Scalability
32-bit VMs Yes Yes
64-bit VMs Yes No
Multi-Processor VMs Yes No
VM Memory Support 64 GB per VM 3.6 GB per VM
Resource Management Yes Yes
Availability
Guest to Guest Failover Yes Yes
Host to Host Failover Yes Yes
Host Migration Yes Yes
VM Snapshots Yes Yes
Management
Scriptable/Extensible Yes, WMI Yes, COM
User Interface MMC 3.0 Interface Web Interface

Perform the following steps to install Hyper-V

    Click Start > Server Manager

  • Communications between virtual machines only.
  • Communications between the virtualization server and virtual machines.
  • Communications between a virtual machine and a physical network by creating an association to a physical network adapter on the virtualization server.

You can either select the Network Adapter that will be attached with the Virtual machines now, or you can do this later using the Virtual Network Manager , Click Next

You use the Virtual Network Manager to add, remove, and modify the virtual networks. The Virtual Network Manager is available from Hyper-V Manager.

As a best practice, it is recommended that you have at least two network adapters on your machine, so that one of the Network adapters is used by the host, and the other network adapter is used by the guest virtual machines

    On the Confirm Installation Selection page, click Install

Installation will be initialized and once completed, you will be informed that a restart is required, click Close

In part 1 of this two parts article, I showed you what are the differences between Hyper-V and Virtual Server 2005, also what are the requirement for Hyper-V, and then finally installed Hyper-V on our Windows Server 2008. In part 2 of this article, I will install Windows Server 2008 as a virtual machine using Hyper-V

It how to install hyper-v virtualization on windows server 2008 r2

Microsoft ceased support for Windows 7 earlier this year. Not only that, but Windows Server 2008 and Windows Server 2008 R2 is also being discontinued.

That being said, users are forced to migrate to Windows 10, and Windows Server 2012 respectively.

The discontinuation of Microsoft Server 2008 and 2008 R2 means that those of you still using Hyper-V Server 2008 R2 will also have to upgrade at some point.

While the upgrade isn’t mandatory, you will be exposed to security threats if you do not accept it.

Unlike Microsoft Server 2008, upgrading a Hyper-V Server is a bit more complicated, meaning that an in-place upgrade is impossible.

Thus, and the only way to upgrade is to install a new copy of the operating system.

Note: This installation will remove all your virtual machines from the console, so backing up all of your virtual machines is recommended.

How do I upgrade from Hyper V Server 2008 R2?

For starters, you should move the virtual machines to a new host that is running the version of Hyper-V Server that you want to use. Once all the guest machines have been moved, then you should reinstall the first machine.

However, if you need to upgrade in place then you will need to follow the steps below:

  1. Make sure that you have a backup
  2. Move all the guest virtual machines to known locations
  3. Avoid having configuration files saved in locations like C:\ProgramData
    • This is because any data stored in such locations will get archived
  4. Keep tabs on all the virtual machines, settings and VHD file locations
  5. Make a note of any static MAC addresses set
  6. Make a note of all the iSCSI targets you have configured
  7. Keep tabs on SAN IPs, drive letters or mount points where these are referenced
  8. Make a backup of the virtual switch configuration on the machine
  9. Backup everything again

Once everything is backed up and relocated, you install Hyper-V Server by wiping the server and installing a new copy. There is no upgrade path.

Basically, you back up all of your data, and once you’ve installed Hyper-V Server 2012 or later, you just copy back the data you backed up.

While this workaround may be a bit frustrating, it is the only way you can migrate from Hyper-V Server 2008 without data loss.

Do you think Hyper-V Server should implement an in-place upgrade feature? Let us know in the comment section below.

RELATED ARTICLES YOU SHOULD CHECK OUT:

Still having issues? Fix them with this tool:

How to install and setup Hyper-V role on Windows Server Std. 2008 R2 with SQL Server 2012 already installed. SQL Server is the priority on this machine. Only one virtual machine will be installed and used to test disaster recovery restores from image backups of servers, when done testing the VM can be removed so we can test another server. The other servers are similar or less powerful with less memory.

I am not planning on creating a partition for this. We have plenty of space on our RAID drives for now. I was thinking of using Static Memory and limit the Virtual Machine to 4 GB of RAM and set 12 GB for SQL Server. The server to host Hyper-V is a Dell PowerEdge 2900 with 16 GB RAM, Intel Xeon, E5345 @3.33 GHZ (2 processers).

  1. How much memory will Hyper-V use if we do NOT have any Virtual machines installed or vm’s being used/tested?
  2. How much memory will Hyper-V use if we do have a Virtual machine installed and we are testing the restore (very basic testing).
  3. Is there a way to easily ‘turn off’ Hyper-V when we do not need it? or do we have to change the memory settings all the time?

UPDATE Nov 9

I should have mentioned that the server roles that we have installed are: Active Directory, DNS, File Services, WSUS, IIS. Though IIS is only used for WSUS. We use two domain controllers in our domain. This is perhaps the biggest reason why we should not also have SQL server installed and add the Hyper-V role. Thus we plan to buy a ‘bare-bones’ refurbished Dell server to test disaster recovery and not use Hyper-V at all. This keeps the testing of image restores off of our production server which I think is wise.

1 Answer 1

That depends on your server and the roles installed and if you open the Hyper-V management console or not. In your configuration with a freshly booted server where you have not opened the Hyper-V management console, it would likely be in the range of 10-20 MB of active memory and practically no CPU (probably closer to 10 than 20). A good way to get a pretty good figure for your set up is to boot cleanly with no VMs running and check the memory free then stop the Hyper-V services and check the amount again. Disable those services, reboot, check the amount of memory, then finally start the services and check the amount again. The different between the first two and second two numbers will give you a good idea of how much just Hyper-V takes in your configuration.

Virtualization is a top priority for thousands of companies all over the world. Written by an author team that is part of the Windows virtualization group at Microsoft, Windows Server 2008 R2 Hyper-V will walk you through Hyper-V essentials so you can get you up to speed and down to business with Hyper-V.

Now fully updated for Windows Server 2008 R2 Hyper-V, you will find additional content on new features and capabilities such as Live Migration and support for 64 Logical Processors (LP).

  • Teaches how to manage virtual machines with the latest System Center tools such as Virtual Machine Manager 2008 R2, Data Protection Manager 2010, and Operations Manager 2007 R2
  • Covers all of the new functionalities of Windows Server 2008 R2 Hyper-V, including Live Migration, 64 LP support, Processor Compatibility Mode, enhanced processor functionality support, hot-add and remove of storage, TCP Offload support, and VM Queue support
  • Demonstrates key scenarios for Hyper-V, including server consolidation, testing and development, Business Continuity and Disaster Recovery, and Dynamic IT
  • Provides step-by-step instructions and examples

This insiders guide will help you get the most out of your hardware and reduce cost with Windows Server 2008 R2 Hyper-V.

About the Author

Mike Sterling is a program manager at Microsoft, where he focuses on the functionality of Hyper-V in Windows Server. He is a regular presenter at TechEd and an active contributor to Microsoft’s virtualization team blog.

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.

Installing Hyper-V

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.

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.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

After reboot another wizard appears that configures the Hyper-V role, so don’t start using the server until this wizard finish his job.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

As you can see installing the Hyper-V role is a straight forward process that any junior admin can do, without any headache.

This is the first post in my series about the new features in Windows Server 2008 R2. As in my series about the new features of Windows 7, I will update the articles when I learn about new features. I will discuss some of the new features in more detail soon.

  • Install Boto3 (AWS SDK for Python) in Visual Studio Code (VS Code) on Windows – Wed, Feb 23 2022
  • Automatically mount an NVMe EBS volume in an EC2 Linux instance using fstab – Mon, Feb 21 2022
  • Result of the Windows 11 poll—Only very few admins want to upgrade – Wed, Feb 16 2022

Essentially, the term “virtualization” covers three different technologies in Windows Server 2008 R2: Server Virtualization, Desktop Virtualization, and Presentation Virtualization. Server Virtualization is based on Hyper-V 2.0, which will get quite a few interesting new features. The virtualization technology behind Desktop virtualization, i.e., Virtual Desktop Infrastructure (VDI), is also Hyper-V.

This is probably the most important new feature in Windows Server 2008 R2. Presentation Virtualization is nothing but the good old Terminal Server. Technically, I find it a bit odd to use the term “virtualization” in this context, but from a marketer’s point of view, it probably makes a lot of sense. Note that Microsoft renamed the “Terminal Services” as “Remote Desktop Services” in Windows Server 2008 R2.

Let’s start with the new features in Server Virtualization.

Hyper-V Live Migration ^

  • Moves virtual machines between two hosts without interruption (slight performance drop)
  • Uses the new Cluster Shared Volumes (CSV) file system within Failover Clustering in Windows Server 2008 R2
  • CSV volumes can only be used for the Live Migration feature
  • Requires failover clustering of Windows Server 2008 R2

Cluster Node Connectivity Fault Tolerance ^

The CSV architecture supports dynamic I/O redirection (I/O can be rerouted within the failover cluster) for three types of failures:

  • Failure of a cluster node connection to the shared storage between cluster nodes
  • Failure of network connectivity for a cluster node
  • Failure of a cluster node

Other Hyper-V 2.0 features ^

  • Support for 32 logical processor cores in a single virtual machine
  • Hot add of VHD and pass-through disks
  • Second Level Translation (SLAT): Support for Intel’s Enhanced Page Tables and AMD’s Nested Page Tables (improves performance, especially for large applications, due to better memory management; it also reduces the memory requirements for the Windows Hypervisor from approximately 5% to 1% of the total physical memory)
  • Boot physical machines from .vhd files: Allows you to deploy Windows Server 2008 R2 to physical and virtual computers using the same .vhd files.

Virtual Desktop Infrastructure (VDI) ^

Desktop Virtualization is a new feature in Windows Server 2008 R2. I will write more about this topic soon.

  • Windows clients (XP, Vista, Windows 7) run on virtual machines on a centralized server
  • VDI includes the following technologies: Hyper-V, Live Migration, System Center Virtual Machine Manager 2008, Microsoft Application Virtualization version 4.5 in Microsoft Desktop Optimization Pack (MDOP), and Vista Enterprise VECD licensing

Note: It is unclear to me in what way VDI is dependent on these products, e.g., I am unsure whether VMM will be required. Do you know more?

RemoteApp & Desktop Connections (RAD) ^

RemoteApp was introduced with Windows Server 2008. It allows end-users to launch a single application on a remote server via RDP. Desktop Connections are common sessions on a Terminal Server.

  • RAD control panel applet: Allows end-users to connect to RemoteApp programs and Remote Desktops
  • Single management console for RemoteApp, Desktop Web Access, and Remote Desktop
  • RemoteApp and Remote Desktop also work for standalone computers (non-domain members)
  • New apps are automatically populated to users’ desktops and Web Access page
  • Single sign-on (I guess only for domain members)
  • Almost all Remote Desktop Services administrative tasks can now be scripted using PowerShell 2.0
  • Profile cache quota and Group Policy caching speed up user logon
  • Improved compatibility with Microsoft Installer (MSI); no need for “install mode” where users had to log off

Remote Desktop Services Gateway (formerly Terminal Services Gateway) (improved) ^

  • Silent Session Re-authentication: Ensures that changes to user profiles are enforced
  • Secure device redirection: Device redirection settings are always enforced
  • Pluggable Authentication: Allows corporations to use their own authentication and authorization technologies
  • Idle & session timeout: Allows admins to disconnect idle sessions or limit the connection time
  • Consent Signing support: Remote users have to give their consent to corporate terms and conditions
  • Administrative messaging: Broadcast messages to remote users

RAD enhancements for third parties ^

  • Support for Cascading Style Sheets (CSS) and XSL Tranformations (XSLT) to customize the Web Access portal
  • Support for protocols other than RDP
  • Session broker extensibility: Policy (determines the proper farm or VM for a connection), Load Balancing (chooses the proper endpoint based on load), Orchestration (prepares a VM to accept RDP connections)

There are also many new features related to the Remote Desktop Protocol (RDP). I covered some of these in my article about the new networking features in Windows 7.

Subscribe to 4sysops newsletter!

Note: I installed Windows Server 2008 R2 Build 6801. The administration tools of the components discussed in this post look pretty much the same as in Windows Server 2008 RTM. Even the term “Terminal Services” is still used in this release. It seems to me it is a bit too early to explore R2 now. However, I didn’t install Hyper-V because I am testing with VMware Workstation and its virtual CPU doesn’t support VT.

Hyper-V Server 2008 R2 is a free standalone virtualization server. The R2 release is an update to the Hyper-v Server 2008 which adds support for the following new key features:

– Support for up to 64 Logical Processors (up to 4 virtual processors per virtual machine)
– Host Clustering
– Live Migration
– Processor Compatibility Mode for live migration (live migration across different CPU versions within the same processor family)
– Improved network performance
– Improved VHD performance for dynamic and difference disks
– Hot Add/Remove of storage (VHDs and Pass Through Disks)
– Second Level Address Translation (SLAT) processor support
– Core Parking

There are cases when you would prefer to install and use the Hyper-V Server 2008 R2 as a standalone machine in a workgroup environment instead of as a member of a domain. This is where you will hit a problem when trying to connect and manage remotely your Hyper-V R2 server. You might get the following errors:

– “You do not have the required permissions to complete this task. Contact the administrator of the authorization policy for this computer”
– “An error occurred while attempting to connect to server. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server”
– “RPC server unavailable. Unable to establish communication between …”

The scenario when you are using and managing Microsoft Hyper-V Server 2008 R2 remotely from Windows 7 in a workgroup requires special attention and configuration on both sides – the managed Server and the managing Client.

In the following Step-by-Step video tutorial, we demonstrate an elegant, simple and easy to follow approach which will help you to configure correctly and manage remotely your Hyper-V R2 server from a Windows 7 workstation in a workgroup environment.

It how to install hyper-v virtualization on windows server 2008 r2

Comments are closed.

Latest Blog Posts

[email protected]

  • New video: How to Upgrade from Exchange 2013 to Exchange 2019 https://t.co/sfhCGCLazf#exchange2019#upgrade#video… https://t.co/DB66CXJKIf06:14:07 AM March 19, 2022
  • New Infinite Loop Bug in OpenSSL Could Let Attackers Crash Remote Servers https://t.co/RKhX7u2Qlm#ssl#certificate#bug#openssl08:20:26 AM March 16, 2022
  • Configure WSUS products and classifications with PowerShell https://t.co/8hapIJwVwJ03:25:17 AM January 25, 2022
  • Install Amazon WorkSpaces: Virtual Linux or Windows desktop in AWS https://t.co/8V0u4bHwox03:22:14 AM January 25, 2022
  • Control Windows Update for Business using the deployment service and PowerShell https://t.co/trF2wHvIa403:20:53 AM January 25, 2022
  • Check PCs for Windows 11 readiness using Microsoft Update Compliance https://t.co/U0tM20HNFz09:56:21 AM January 20, 2022
  • Bulk restore deleted Azure AD users https://t.co/CZk3gktRSB03:14:27 AM January 17, 2022
  • Root login via SSH and SFTP on EC2 instances running Linux https://t.co/mD0qMjwe0X03:13:31 AM January 17, 2022
  • Windows 10 upgrade – Tools to migrate apps, data and user profiles https://t.co/SPOvIKEhju03:06:44 AM January 17, 2022
  • Monitoring Windows system stability with PowerShell https://t.co/tBaG1VFyOj03:05:53 AM January 17, 2022

New Screencasts

It how to install hyper-v virtualization on windows server 2008 r2

Screencast: How to Upgrade from Exchange 2013 to Exchange 2019

Part 1: Overview of the existing configuration and the upgrade plan Active Directory requirements and…

It how to install hyper-v virtualization on windows server 2008 r2

Video: How to Install a Let’s Encrypt Certificate in Exchange Server 2016

Screencast :Let’s Encrypt Exchange Certificate – Exchange 2016 Configure Exchange 2016 Client Access Namespace and Internal Name…

It how to install hyper-v virtualization on windows server 2008 r2

Letsencrypt Windows Client: How to Install Let’s Encrypt Free SSL Certificates on Windows Server

In this video, we demonstrate how to install Let’s Encrypt SSL certificates on Windows Servers running…

It how to install hyper-v virtualization on windows server 2008 r2

Screencast: How to Install Exchange 2016

Screencast :How to Install Exchange Server 2016 Perform Active Directory Health Check Install Exchange 2016 Prerequisites and Prepare…

It how to install hyper-v virtualization on windows server 2008 r2

Screencast: How to Demote the Last Server 2003 Domain Controller

Screencast :Server 2003 Migrations Perform AD Health Check Clean Up Sites, Services and DNS zones Reconfigure the Time Service Demote…

Late to the virtualization game, Microsoft has been running several lengths behind the competition in this space for years. However, the new features and strong performance present in Windows Server 2008 R2 SP1 show that the company hasn’t been twiddling its thumbs. It’s clearly been working hard at bringing a compelling and competitive virtualization solution to the market.

There’s plenty to like in Hyper-V these days, not the least of which is the price comparison to the other major players. But whereas that lower price used to mean significantly diminished features and performance, that gap has closed. Hyper-V now offers the big features, including live VM migrations, load balancing, and high availability, as well as a more fluid management interface in Microsoft System Center Virtual Machine Manager 2008 R2 (VMM).

One very notable addition to Hyper-V in Windows Server 2008 R2 SP1 is dynamic memory. By specifying a minimum and maximum RAM allotment per virtual machine, as well as a buffer to maintain over actual memory requirements, you can configure Hyper-V to grow and shrink RAM allocations as virtual machines require. This means you could give a virtual machine 2GB of RAM, but allow it to grow up to 4GB as needed. If the VM needs less, Hyper-V can then reduce physical RAM usage on the host. In situations where a host exhausts physical RAM, Hyper-V will begin reducing the allotted RAM to running virtual machines based on their priority.

Like memory management in VMware’s hypervisor, Hyper-V’s dynamic memory allows you to run a higher density of VMs on each host. Microsoft’s method of memory allocation, which utilizes a memory balloon that can expand and contract as needed, has clear benefits, but doesn’t go as far as VMware’s or Red Hat’s, which leverage advanced features such as page sharing and RAM compression. Plus, Hyper-V’s dynamic memory works only with Windows guests; VMware and Red Hat have no such limitation.

Microsoft Windows 2008, with Hyper-V Virtual machine, will not start. The user will receive the following message in Microsoft Windows Hyper-V when starting a virtual machine: “An error occurred while attempting to change the state of the virtual machine “Name of virtual machine” When the message is expanded, the user will receive the following message: “Name of virtual machine” failed to initialize. The virtual machine could not be started because the hypervisor is not running.”

Resolving The Problem

Source

RETAIN tip: H194572

Symptom

Microsoft Windows 2008, with Hyper-V Virtual machine, will not start.

The user will receive the following message in Microsoft Windows Hyper-V when starting a virtual machine:

“An error occurred while attempting to change the state of the virtual machine “Name of virtual machine”

When the message is expanded, the user will receive the following message:

“Name of virtual machine” failed to initialize. The virtual machine could not be started because the hypervisor is not running.”

Affected configurations

The system is configured with at least one of the following:

  • Microsoft Windows Server 2008, Datacenter 32-bit, any service pack
  • Microsoft Windows Server 2008, Datacenter 64-bit, any service pack
  • Microsoft Windows Server 2008, Enterprise 32-bit, any service pack
  • Microsoft Windows Server 2008, Enterprise 64-bit, any service pack
  • Microsoft Windows Server 2008, Standard 32-bit, any service pack
  • Microsoft Windows Server 2008, Standard 64-bit, any service pack

This tip is not hardware specific.

This tip is not option specific.

Note: This does not imply that the network operating system will work under all combinations of hardware and software.

Workaround

This is a Microsoft Windows 2008 Hyper-V requirement.

Make sure Microsoft Windows 2008 with Hyper-V is ServerProven. The ServerProven site is at the following URL:

Make sure to have hardware that supports VT or AMD-V processor and BIOS.

    Click F1 for BIOS.

Additional information

This is a Microsoft requirement.

For Hyper-V to work, both Hyper-V and Processor Execute Disable Bit must be enabled.

This issue is documented in the Microsoft Hyper-V documentation at the following URL:

Note: Hyper-V Server 2008 is a 64-bit only technology and requires a 64-bit capable hardware with Intel VT or AMD-V technology enabled.

Note: Specifically, the user must enable Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).

Hyper-V enables an organization to consolidate several physical server systems into a single host server while still providing isolation between virtual guest session application operations. Hyper-V is only available on the 64-bit editions of Windows Server. The CPU must support hardware-enforced Data Execution Prevention, or DEP found in computer’s BIOS settings.

You can install the Hyper-V role using the Server Manager console or by using the following PowerShell command when the Server Manager module is loaded

Add-WindowsFeature Hyper-V

1. logged on to the server with administrator privileges.

2. Click Start, All Program Files, Administrative Tools, and choose Server Manager and click Add Server Roles.

It how to install hyper-v virtualization on windows server 2008 r2

3. Click Next to continue past the Welcome screen.

It how to install hyper-v virtualization on windows server 2008 r2

4. On the Select Server Roles page, select the Hyper-V Server role, and click Next.

It how to install hyper-v virtualization on windows server 2008 r2

5. Read the notes and information about the role, and then click Next.

It how to install hyper-v virtualization on windows server 2008 r2

6. Select LAN adapters you want to have shared with guest sessions and then Click Next to continue.

It how to install hyper-v virtualization on windows server 2008 r2

7. On Confirm Installation Selections page, review the selections made, and then Click Install.

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.

It how to install hyper-v virtualization on windows server 2008 r2

Add role installation wizard comes up. It gives you the basic overview as to what this wizard does. Click on Next.

It how to install hyper-v virtualization on windows server 2008 r2

Select the Hyper-V role from the next step and click on Next.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

Now you are on the confirmation page, go ahead and click on the Install button.

It how to install hyper-v virtualization on windows server 2008 r2

Once the installation is complete, it will ask you to restart the machine for the changes to take effect.

It how to install hyper-v virtualization on windows server 2008 r2

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.

It how to install hyper-v virtualization on windows server 2008 r2

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.

About Author

  • Website
  • Facebook
  • Twitter
  • Google+
  • LinkedIn

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.

Windows Server 2012 R2 introduce a feature called Automatic Virtual Machine Activation (AVMA). Until Windows Server 2008 R2 the only feature to activate Virtual Servers in HYPER-V Host was to login in Server and follow the steps to Activate with the License Key.

With Automatic Virtual Machine Activation (AVMA) this can change and activate Virtual Servers that are in HYPER-V Host without need the Licenses Keys that you have for different version of Windows.

Now let’s explain how can use this feature

What is Automatic Virtual Machine Activation (AVMA)

It’s a feature that first introduce in Windows Server 2012 R2 that can allow to activate Virtual Machines via HYPER-V Host.

Requirements for Automatic Virtual Machine Activation (AVMA)

Before start to use Automatic Virtual Machine Activation (AVMA) must meet the following requirements

  1. Host must has Windows Server 2012 R2 or 2016 Datacenter Edition with HYPER-V Role installed
  2. Integration Services must run in Virtual Machines and verify that Data Exchange Service running in Virtual Machine

Support Guest Operating Systems for Virtual Machine Activation (AVMA)

Automatic Virtual Machine Activation (AVMA) support specific Guest operating systems

Windows Server 2012 R2 Datacenter Edition in HYPER-V Host

  • Windows Server 2012 R2 Datacenter ,Standard ,Essential Edition

Windows Server 2016 Datacenter Edition in HYPER-V Host

  • Windows Server 2012 R2 Datacenter ,Standard ,Essential Edition
  • Windows Server 2016 Datacenter ,Standard ,Essential Edition

How can use Virtual Machine Activation (AVMA) in Guest Operating System

First of all let’s take a look how works AVMA.

Automatic Virtual Machine Activation (AVMA) always run in Windows Server Datacenter edition with HYPER-V Role installed.

Windows Server Datacenter Edition as Management OS in HYPER-V Host has a feature that monitoring all the Virtual Machines.

Integration Service include the Microsoft Hyper-v Activation Component Driver in Virtual Machine which implement all the parts from the Virtual Machine side.

It how to install hyper-v virtualization on windows server 2008 r2

The communication between Management OS and guest side implemented by Data Exchange Service which included in Integration Services.

It how to install hyper-v virtualization on windows server 2008 r2

As i wrote in the beginning is one of the requirements to verify that Data Exchange Service is enable.

Now let’s go to activate one Virtual Server with Automatic Virtual Machine Activation (AVMA).

  • Login in Virtual Server
  • Open command prompt
  • Type the following command
    slmgr /ipk

It how to install hyper-v virtualization on windows server 2008 r2

AVMA keys are the following. Yes Microsoft has publish specific AVMA keys that can use it base on the OS Version.

Find it here or go in Technet Page of Microsoft Automatic Virtual Machine Activation for more details.

For Windows Server 2012 R2 Datacenter Edition

Datacenter Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
Standard DBGBW-NPF86-BJVTX-K3WKJ-MTB6V
Essentials K2XGM-NMBT3-2R6Q8-WF2FK-P36R2

For Windows Server 2016 Datacenter Edition

  • After run the command you will get the following message

It how to install hyper-v virtualization on windows server 2008 r2

  • If you want to verify that the Virtual Server has activated you can search for Event ID 12310 in HYPER-V Host.
  • Unfortunately the info of the Logs are very limited.

It how to install hyper-v virtualization on windows server 2008 r2

  • If you would like to have more details like full qualified domain name, OS and Service Packs , Processors you can use the Hyper-V Script: Looking at KVP GuestIntrinsicExchangeItems .
  • Find more details in Technet Page of Microsoft Automatic Virtual Machine Activation .

Migration Affect AVMA ?

What happened if you Migrate Virtual Server in another HYPER-V Host?

If you decide to move a Virtual Server which has Activate with AVMA key the new HYPER-V Host must has Windows Server 2012 R2 or 2016 Datacenter Edition.

Unless Virtual Server will change into unlicensed state.

If you have lot of Virtual Servers it’s an easy way to Activate it without need to search for License Key’s depends of Windows OS.

Have a nice weekend !!

How many Virtual Servers do you have ? It is worth to use AVMA ? Let’s discuss it in our commented system or find me in Google + and Facebook

Do you want to try out Hyper-V Server 2008 R2 and don’t have a spare machine for testing?

By following the instructions below you can install the following operating systems in a VHD file and then boot directly from VHD. In addition you can backup these “pseudo-partitions” easily since they are contained in a single VHD file:

Hyper-V Server 2008 R2

Windows Server 2008 R2 (Full or Server Core installations)

Requirements: Windows 7 or Windows Server 2008 R2. Windows PowerShell needs to be installed.

Instructions:

1. Download Hyper-V Server 2008 R2 (or Windows 7, Windows Server 2008 R2). Microsoft’s Hyper-V Server DVD Download Page

2. Download Microsoft’s Windows Image installation script. Microsoft Download or BackupChain’s Mirror

3. Open the ISO image by mounting it or by using an archive tool (examples: Virtual Clone Drive and 7-ZIP)

4. Extract the SOURCES folder to your C: drive

5. Copy the script file (Install-WindowsImage.ps1) into the C:\sources folder

6. Open Disk Management. (Click on Start and search for ‘Create and Format Hard Disk Partitions’. Click on the result to start)

7. Click Action -> Create VHD.

8. Right click on the new disk drive and select Initialize Disk, then press OK

9. Right click on the new volume created and click New Simple Volume

10. Click through the Wizard, format the volume and assign it a drive letter, such as X:

11. Open Windows PowerShell as Administrator and run these commands:

For Windows 7 and Hyper-V Server 2008 R2, type:

.\Install-WindowsImage.ps1 –WIM C:\sources\install.wim -Apply -Index 1 -Destination X:

For Windows Server 2008 R2 Enterprise Full Installation, type this instead:

.\Install-WindowsImage.ps1 –WIM C:\sources\install.wim -Apply -Index 3 -Destination X:

For Windows Server 2008 R2 Datacenter Full Installation, type this instead:

.\Install-WindowsImage.ps1 –WIM C:\sources\install.wim -Apply -Index 5 -Destination X:

12. Wait a while until the process is completed, then go back to Disk Management and Detach VHD (right click on volume)

Now you have a VHD that’s ready to boot; however, you may want to set up a boot menu on your machine as well.

Multiboot / Boot Menu Setup Instructions:

1. Open Command Prompt as administrator

bcdedit /copy /d “New Hyper-V Server Instance Name in Boot Menu”

3. Then bcdedit will return a GUID number like this one: . Use the GUID returned for the following instructions below.

4. bcdedit /set device vhd=[C:]\myfolder\myvhdfilename.vhd

5. bcdedit /set osdevice vhd=[C:]\myfolder\myvhdfilename.vhd

6. Optional: If you plan to use Hyper-V’s virtualization features you may want to turn on the hypervisor:

bcdedit /set hypervisorlaunchtype Auto

You may also need to turn on virtualization support in your BIOS if you haven’t done so already.

Congratulations! Now you can reboot and select your VHD to boot from. The reset of the Windows installation will continue once you boot from VHD.

Don’t forget to set up your virtual backup solution for your new Hyper-V Server 2008 R2 installation! Our Hyper-V backup software also works on VMware.

I’m trying to get VirtualBox running on a machine which also runs Hyper-V. The system is:

DELL PowerEdge
2x Intel Xeon E5620
24 GB RAM
Virtualization Enabled in BIOS

Windows Server 2008 R2 Standard
VirtualBox 4.0.4r70112 (64 bit)

The problem: if DEP is enabled in the BIOS, VirtualBox will not allow me to have more than one processor. It also freezes the host computer when a virtual machine is launched — no bluescreen, just freeze. If DEP is disabled, VirtualBox will allow me to select more than one processor and runs fine. However, Hyper-V requires DEP to be enabled in the BIOS, or else it won’t load.

Questions: can Hyper-V and VirtualBox coexist on the same machine? If it is possible, what changes or what settings are required to run both of them. Does it even make sense to run them both, or should I just run all my VB machines in Hyper-V.

Re: Windows Server 2008 R2 Hyper-V + VirtualBox

by Perryg » 11. Mar 2011, 20:14

Re: Windows Server 2008 R2 Hyper-V + VirtualBox

by andreask » 11. Mar 2011, 21:34

Re: Windows Server 2008 R2 Hyper-V + VirtualBox

by Sasquatch » 12. Mar 2011, 00:30

Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we’re talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.

Re: Windows Server 2008 R2 Hyper-V + VirtualBox

by ie12 » 28. Jun 2011, 11:43

You do not have to uninstall the Hyper-V role for virtualbox to run under windows 2008.

Just set the start-up mode of hvmount.sys to ondemand (value 3 in the registry).
Please do a web search for the details.

Alternatively, use bcedit to optionally boot with hyper-v disabled.

I would suggest the first method.

Re: Windows Server 2008 R2 Hyper-V + VirtualBox

by BetsyD » 19. May 2012, 23:53

To get Hyper-V and VirtualBox to coexist, by setting the startup mode of the Hyper-V hypervisor (hvboot.sys) to “on demand”, here are a couple of methods that have worked for me:

(1) Edit the registry. At HKLM\SYSTEM\CurrentControlSet\services\hvboot, change the DWord value “Start” from 1 to 3.

(2) Open a command prompt with Administrator privilege and type: sc config hvboot start= demand
(Must include the space after the “=”. To undo the command, use start= system.)

Either way, it’s a one-time configuration change. A reboot is needed before either version takes effect.

After I’ve done either (1) or (2) above, I can leave both VirtualBox and the Hyper-V role installed. VirtualBox runs with no additional steps. To run Hyper-V, I first close VirtualBox if it’s open, then run a command in an elevated command window: net start hvboot

To run VirtualBox again after running Hyper-V by this method, I have to reboot.