Install the Hyper-V role on Windows Server
To create and run virtual machines, install the Hyper-V role on Windows Server by using Server Manager or the Install-WindowsFeature cmdlet in Windows PowerShell. For Windows 10, see Install Hyper-V on Windows To learn more about Hyper-V, see the Hyper-V Technology Overview. To try out Windows Server , you can download and install an evaluation copy. Note the name of the role we want to install is Hyper-V. Type Install-WindowsFeature Hyper-v –IncludeManagementTools. Note: Adding the –IncludeManagementTools switch will add the Hyper-V graphical management tools, otherwise you will have to install the tools separately. You could also install the feature RSAT-Hyper-V-Tools to add the graphical management tools. Ensure all windows are .
Hyper-V has specific hardware requirements, and some Hyper-V features have additional requirements. Use the details in this article to decide what requirements your system must meet so you can use Hyper-V the way you plan to. Then, review the Windows Server catalog. Keep in mind that requirements for Hyper-V exceed the general minimum requirements for Windows Server because a virtualization environment requires more computing resources.
If you're already using Hyper-V, it's likely that you can use your existing hardware. The general hardware requirements haven't changed significantly from Windows Server R2.
But, you will need newer hardware to use shielded virtual machines or discrete device assignment. Those features rely on specific hardware support, as described below. Other than that, the main difference in hardware is that second-level address translation SLAT is now required instead of recommended.
For details about maximum supported configurations for Hyper-V, such as the number of running virtual machines, see Reqyired for Hyper-V scalability in Windows Server The list of operating systems you can run whah your virtual machines is covered in Supported Windows guest operating systems for What is required to install the hyper- v server role on Windows Server. A bit processor with second-level nistall translation SLAT. More memory is better. You'll need enough memory for the host and all virtual machines that you want to run at the same time.
Hardware-assisted virtualization. For Intel systems, this is the XD bit execute instal, bit. Requirsd are the requirements for how to keep water tanks clean device assignment and shielded virtual machines. For instructions, see the hardware documentation or contact your hardware manufacturer.
For GPU, only certain devices support discrete device assignment. To verify, see the hardware documentation or contact your hardware manufacturer. For details about this feature, including how to use it and considerations, see the post " Discrete Device Assignment -- Description and background " in the Virtualization servsr. These virtual machines rely seever virtualization-based security and are available starting with Windows Server The following two are optional for virtualization-based security in general, but required for the host if you want the thr these features provide:.
Skip to main content. Contents Exit focus mode. Requirements for specific features Here are the requirements for discrete device assignment and shielded virtual machines. Shielded virtual machines These virtual machines rely on virtualization-based security and are available starting with Windows Server Host requirements are: UEFI 2. Yes No. Any additional feedback? Skip Submit. Submit and view feedback for This product This page. View all page feedback.
Is this page helpful?
Windows Server Desktop Experience(GUI) vs Server Core
If you have ever installed Hyper-V role on Windows Server R2 or , the requirements are almost the same. The only different thing is if you are planning to run Shielded Virtual Machines, then you will need newer hardware because, before server , the second-level address level translation (SLAT) was optional, but now it is required, so you will need the x64 bit processor which support SLAT. Install Hyper-V Role using PowerShell commands. Installing the Hyper-V role using PowerShell command in Windows Server is no different from previous versions and is very straight forward. For the GUI version, Run PowerShell as Administrator and run the following command. Cmd: Install-windows feature -Name Hyper-V -IncludeManagementTools.
Before you are able to build a virtualized environment you will need to install and configure the Hyper-V role on your Windows , Windows R2, Windows or Windows R2 server. The procedure is pretty much the same for all the above operating systems. You can install the role either through PowerShell or with the graphical Server Manager. I will demonstrate both methods. Type Get-WindowsFeature to retrieve installed roles and features and to determine the name of the role you want to install.
Note: Adding the —IncludeManagementTools switch will add the Hyper-V graphical management tools, otherwise you will have to install the tools separately.
Create Virtual Switches, if you are going to be connecting the virtual machines to the host machines external interface, you would select the Local Area Connection, click Next.
Note: If you need to support Live Migrations from the get go you can select Allow this server to send and receive live migrations of virtual machines. This setting can be configured post installation of Hyper-V. On the Confirm installation selections, select Restart the destination server automatically if required. Select Yes on the warning screen. Note: Hyper-V does require a restart when installing.
Before clicking on Install, ensure you save all your work and close applications. The server will restart without prompting the user to save their work. After the server restarts logon and if needed launch Server Manager.
A Installation progress screen will appear, click Close when the installation has completed. In this recorded Windows 10 training webinar from December 2, , Windows Server instructor Rick Trader presents the deployment and management of Windows 10 Enterprise and the new Provisioning capability in Windows Also included in his presentation … Continue reading Windows 10 Managing, Deploying and Configuring — December 2, In this recorded Windows 10 webinar from December 1,, Windows Instructor Steve Fullmer presents the navigation and some of the new features associated with Windows 10 including Sysinternals Tools for Windows Client, Windows core concepts, exploring Process Explorer as well as some of the features that are not yet ready for prime time but will … Continue reading Windows 10 Features and Navigation — December 1, In the past, if we had virtualized Domain Controllers and we actually took a snapshot of it and then rolled back to that snapshot, it would break the logon service on that … Continue reading How to clone a Windows Server or R2 Domain Controller.
Save my name, email, and website in this browser for the next time I comment. How to install the Hyper-V role in Windows Server. Subscribe to this author's posts feed via RSS. Videos You May Like. Windows 10 Managing, Deploying and Configuring — December 2, 0 1 In this recorded Windows 10 training webinar from December 2, , Windows Server instructor Rick Trader presents the deployment and management of Windows 10 Enterprise and the new Provisioning capability in Windows Windows 10 Features and Navigation — December 1, 0 1 In this recorded Windows 10 webinar from December 1,, Windows Instructor Steve Fullmer presents the navigation and some of the new features associated with Windows 10 including Sysinternals Tools for Windows Client, Windows core concepts, exploring Process Explorer as well as some of the features that are not yet ready for prime time but will … Continue reading Windows 10 Features and Navigation — December 1, Share your thoughts Cancel reply Please fill out the comment form below to post a reply.
We are OPEN! Learn More.