diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 7d4497ec89..6b7720091e 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -11739,6 +11739,46 @@ "source_path": "WindowsServerDocs/storage/whats-new-in-storage.md", "redirect_url": "/windows-server/get-started/whats-new-in-windows-server-2022", "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/Hyper-V-Technology-Overview.md", + "redirect_url": "/windows-server/virtualization/hyper-v/hyper-v-overview", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/Hyper-V-on-Windows-Server.md", + "redirect_url": "/windows-server/virtualization/hyper-v/hyper-v-overview", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/Hyper-V-Server-2016.md", + "redirect_url": "/windows-server/virtualization/hyper-v/hyper-v-overview", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/get-started/Get-started-with-Hyper-V-on-Windows.md", + "redirect_url": "/windows-server/virtualization/hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/plan/Plan-Hyper-V-on-Windows-Server.md", + "redirect_url": "/windows-server/virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/deploy/Deploy-Hyper-V-on-Windows-Server.md", + "redirect_url": "/windows-server/virtualization/hyper-v/deploy/configure-virtual-local-areal-networks-for-hyper-v", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/manage/Manage-Hyper-V-on-Windows-Server.md", + "redirect_url":"/windows-server/virtualization/hyper-v/manage/persistent-memory-cmdlets", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/virtualization/hyper-v/deploy/configure-virtual-local-areal-networks-for-Hyper-V.md", + "redirect_url": "/windows-server/virtualization/hyper-v/deploy/configure-virtual-local-area-networks-for-hyper-v", + "redirect_document_id": false } ] } diff --git a/WindowsServerDocs/networking/sdn/deploy/Deploy-a-Software-Defined-Network-infrastructure-using-scripts.md b/WindowsServerDocs/networking/sdn/deploy/Deploy-a-Software-Defined-Network-infrastructure-using-scripts.md index 449313390a..10e502b10f 100644 --- a/WindowsServerDocs/networking/sdn/deploy/Deploy-a-Software-Defined-Network-infrastructure-using-scripts.md +++ b/WindowsServerDocs/networking/sdn/deploy/Deploy-a-Software-Defined-Network-infrastructure-using-scripts.md @@ -1,12 +1,11 @@ --- title: Deploy a Software Defined Network Infrastructure Using Scripts -description: This topic covers how to deploy a Microsoft Software Defined Network (SDN) infrastructure using scripts in Windows Server 2019 and 2016. -manager: grcusanz +description: This topic covers how to deploy a Microsoft Software Defined Network (SDN) infrastructure using scripts in Windows Server. ms.topic: how-to ms.assetid: 5ba5bb37-ece0-45cb-971b-f7149f658d19 ms.author: wscontent author: robinharwood -ms.date: 10/28/2021 +ms.date: 08/13/2024 --- # Deploy a Software Defined Network infrastructure using scripts @@ -15,11 +14,11 @@ ms.date: 10/28/2021 In this topic, you deploy a Microsoft Software Defined Network (SDN) infrastructure using scripts. The infrastructure includes a highly available (HA) network controller, an HA Software Load Balancer (SLB)/MUX, virtual networks, and associated Access Control Lists (ACLs). Additionally, another script deploys a tenant workload for you to validate your SDN infrastructure. -If you want your tenant workloads to communicate outside their virtual networks, you can setup SLB NAT rules, Site-to-Site Gateway tunnels, or Layer-3 Forwarding to route between virtual and physical workloads. +If you want your tenant workloads to communicate outside their virtual networks, you can set up SLB NAT rules, Site-to-Site Gateway tunnels, or Layer-3 Forwarding to route between virtual and physical workloads. You can also deploy an SDN infrastructure using Virtual Machine Manager (VMM). For more information, see [Set up a Software Defined Network (SDN) infrastructure in the VMM fabric](/system-center/vmm/deploy-sdn). -## Pre-deployment +## Predeployment > [!IMPORTANT] > Before you begin deployment, you must plan and configure your hosts and physical network infrastructure. For more information, see [Plan a Software Defined Network Infrastructure](/azure-stack/hci/concepts/plan-software-defined-networking-infrastructure). @@ -27,13 +26,13 @@ You can also deploy an SDN infrastructure using Virtual Machine Manager (VMM). F All Hyper-V hosts must have Windows Server 2019 or 2016 installed. ## Deployment steps -Start by configuring the Hyper-V host's (physical servers) Hyper-V virtual switch and IP address assignment. Any storage type that is compatible with Hyper-V, shared or local may be used. +Start by configuring the Hyper-V host's (physical servers) Hyper-V virtual switch and IP address assignment. Any storage type that is compatible with Hyper-V, shared, or local may be used. ### Install host networking 1. Install the latest network drivers available for your NIC hardware. -2. Install the Hyper-V role on all hosts (For more information, see [Get started with Hyper-V on Windows Server 2016](../../../virtualization/hyper-v/get-started/get-started-with-hyper-v-on-windows.md). +2. Install the Hyper-V role on all hosts. For more information, see [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server). ```PowerShell Install-WindowsFeature -Name Hyper-V -ComputerName -IncludeManagementTools -Restart @@ -48,19 +47,19 @@ Start by configuring the Hyper-V host's (physical servers) Hyper-V virtual switc > [!TIP] > You can skip steps 4 and 5 if you have separate Management NICs. -3. Refer to the planning topic ([Plan a Software Defined Network Infrastructure](/azure-stack/hci/concepts/plan-software-defined-networking-infrastructure)) and work with your network administrator to obtain the VLAN ID of the Management VLAN. Attach the Management vNIC of the newly created Virtual Switch to the Management VLAN. This step can be omitted if your environment does not use VLAN tags. +4. Refer to the planning topic [Plan a Software Defined Network Infrastructure](/azure-stack/hci/concepts/plan-software-defined-networking-infrastructure) and work with your network administrator to obtain the VLAN ID of the Management VLAN. Attach the Management vNIC of the newly created Virtual Switch to the Management VLAN. This step can be omitted if your environment doesn't use VLAN tags. ```PowerShell Set-VMNetworkAdapterIsolation -ManagementOS -IsolationMode Vlan -DefaultIsolationID -AllowUntaggedTraffic $True ``` -4. Refer to the planning topic ([Plan a Software Defined Network Infrastructure](/azure-stack/hci/concepts/plan-software-defined-networking-infrastructure)) and work with your network administrator to use either DHCP or static IP assignments to assign an IP address to the Management vNIC of the newly created vSwitch. The following example shows how to create a static IP address and assign it to the Management vNIC of the vSwitch: +5. Refer to the planning topic [Plan a Software Defined Network Infrastructure](/azure-stack/hci/concepts/plan-software-defined-networking-infrastructure) and work with your network administrator to use either DHCP or static IP assignments to assign an IP address to the Management vNIC of the newly created vSwitch. The following example shows how to create a static IP address and assign it to the Management vNIC of the vSwitch: ```PowerShell New-NetIPAddress -InterfaceAlias "vEthernet ()" -IPAddress -DefaultGateway -AddressFamily IPv4 -PrefixLength ``` -5. [Optional] Deploy a virtual machine to host Active Directory Domain Services ([Install Active Directory Domain Services (Level 100)](../../../identity/ad-ds/deploy/install-active-directory-domain-services--level-100-.md) and a DNS Server. +6. [Optional] Deploy a virtual machine to host Active Directory Domain Services [Install Active Directory Domain Services (Level 100)](../../../identity/ad-ds/deploy/install-active-directory-domain-services--level-100-.md) and a DNS Server. a. Connect the Active Directory/DNS Server virtual machine to the Management VLAN: @@ -73,22 +72,23 @@ Start by configuring the Hyper-V host's (physical servers) Hyper-V virtual switc > [!NOTE] > The network controller supports both Kerberos and X.509 certificates for authentication. This guide uses both authentication mechanisms for different purposes (although only one is required). -6. Join all Hyper-V hosts to the domain. Ensure the DNS server entry for the network adapter that has an IP address assigned to the Management network points to a DNS server that can resolve the domain name. +7. Join all Hyper-V hosts to the domain. Ensure the DNS server entry for the network adapter that has an IP address assigned to the Management network points to a DNS server that can resolve the domain name. ```PowerShell Set-DnsClientServerAddress -InterfaceAlias "vEthernet ()" -ServerAddresses ``` - a. Right-click **Start**, click **System**, and then click **Change Settings**. - b. Click **Change**. - c. Click **Domain** and specify the domain name. """" - d. Click **OK**. + a. Right-click **Start**, select **System**, and then select **Change Settings**. + **Change Settings**. + b. Select **Change**. + c. Select **Domain** and specify the domain name. + d. Select **OK**. e. Type the user name and password credentials when prompted. f. Restart the server. ### Validation -Use the following steps to validate that host networking is setup correctly. +Use the following steps to validate that host networking is set up correctly. 1. Ensure the VM Switch was created successfully: @@ -105,16 +105,16 @@ Use the following steps to validate that host networking is setup correctly. Get-VMNetworkAdapterIsolation -ManagementOS ``` -3. Validate all Hyper-V hosts and external management resources, for example, DNS servers.

Ensure they are accessible via ping using their Management IP address and/or fully qualified domain name (FQDN). +3. Validate all Hyper-V hosts and external management resources, for example, DNS servers. Ensure they're accessible via ping using their Management IP address and/or fully qualified domain name (FQDN). - ``` + ```PowerShell ping ping ``` 4. Run the following command on the deployment host and specify the FQDN of each Hyper-V host to ensure the Kerberos credentials used provides access to all the servers. - ``` + ```PowerShell winrm id -r: ``` @@ -138,8 +138,8 @@ Use the following steps to validate that host networking is setup correctly. | AgentConf | Holds fresh copies of OVSDB schemas used by the SDN Host Agent on each Windows Server 2016 Hyper-V host to program network policy. | | Certs | Temporary shared location for the NC certificate file. | | Images | Empty, place your Windows Server 2016 vhdx image here | - | Tools | Utilities for troubleshooting and debugging. Copied to the hosts and virtual machines. We recommend you place Network Monitor or Wireshark here so it is available if needed. | - | Scripts | Deployment scripts.

- **SDNExpress.ps1**
Deploys and configures the fabric, including the Network controller virtual machines, SLB Mux virtual machines, gateway pool(s) and the HNV gateway virtual machine(s) corresponding to the pool(s) .
- **FabricConfig.psd1**
A configuration file template for the SDNExpress script. You will customize this for your environment.
- **SDNExpressTenant.ps1**
Deploys a sample tenant workload on a virtual network with a load balanced VIP.
Also provisions one or more network connections (IPSec S2S VPN, GRE, L3) on the service provider edge gateways which are connected to the previously created tenant workload. The IPSec and GRE gateways are available for connectivity over the corresponding VIP IP Address, and the L3 forwarding gateway over the corresponding address pool.
This script can be used to delete the corresponding configuration with an Undo option as well.
- **TenantConfig.psd1**
A template configuration file for tenant workload and S2S gateway configuration.
- **SDNExpressUndo.ps1**
Cleans up the fabric environment and resets it to a starting state.
- **SDNExpressEnterpriseExample.ps1**
Provisions one or more enterprise site environments with one Remote Access Gateway and (optionally) one corresponding enterprise virtual machine per site. The IPSec or GRE enterprise gateways connects to the corresponding VIP IP address of the service provider gateway to establish the S2S tunnels. The L3 Forwarding Gateway connects over the corresponding Peer IP Address.
This script can be used to delete the corresponding configuration with an Undo option as well.
- **EnterpriseConfig.psd1**
A template configuration file for the Enterprise site-to-site gateway and Client VM configuration. | + | Tools | Utilities for troubleshooting and debugging. Copied to the hosts and virtual machines. We recommend you place Network Monitor or Wireshark here so it is available if needed. | + | Scripts | Deployment scripts.

- **SDNExpress.ps1**
Deploys and configures the fabric, including the Network controller virtual machines, SLB Mux virtual machines, gateway pool(s), and the HNV gateway virtual machine(s) corresponding to the pool(s).
- **FabricConfig.psd1**
A configuration file template for the SDNExpress script. You'll customize this for your environment.
- **SDNExpressTenant.ps1**
Deploys a sample tenant workload on a virtual network with a load balanced VIP.
Also provisions one or more network connections (IPSec S2S VPN, GRE, L3) on the service provider edge gateways which are connected to the previously created tenant workload. The IPSec and GRE gateways are available for connectivity over the corresponding VIP IP Address, and the L3 forwarding gateway over the corresponding address pool.
This script can be used to delete the corresponding configuration with an Undo option as well.
- **TenantConfig.psd1**
A template configuration file for tenant workload and S2S gateway configuration.
- **SDNExpressUndo.ps1**
Cleans up the fabric environment and resets it to a starting state.
- **SDNExpressEnterpriseExample.ps1**
Provisions one or more enterprise site environments with one Remote Access Gateway, and (optionally) one corresponding enterprise virtual machine per site. The IPSec or GRE enterprise gateways connects to the corresponding VIP IP address of the service provider gateway to establish the S2S tunnels. The L3 Forwarding Gateway connects over the corresponding Peer IP Address.
This script can be used to delete the corresponding configuration with an Undo option as well.
- **EnterpriseConfig.psd1**
A template configuration file for the Enterprise site-to-site gateway and Client VM configuration. | | TenantApps | Files used to deploy example tenant workloads. | 6. Verify the Windows Server 2016 VHDX file is in the **Images** folder. @@ -150,28 +150,26 @@ Use the following steps to validate that host networking is setup correctly. 9. Run the script as a user with domain administrator credentials: - ``` + ```PowerShell SDNExpress\scripts\SDNExpress.ps1 -ConfigurationDataFile FabricConfig.psd1 -Verbose ``` 10. To undo all operations, run the following command: - ``` + ```PowerShell SDNExpress\scripts\SDNExpressUndo.ps1 -ConfigurationDataFile FabricConfig.psd1 -Verbose ``` - #### Validation Assuming that the SDN Express script ran to completion without reporting any errors, you can perform the following step to ensure the fabric resources have been deployed correctly and are available for tenant deployment. Use [Diagnostic Tools](../troubleshoot/troubleshoot-windows-server-software-defined-networking-stack.md) to ensure there are no errors on any fabric resources in the network controller. - ``` + ```PowerShell Debug-NetworkControllerConfigurationState -NetworkController ``` - ### Deploy a sample tenant workload with the software load balancer Now that fabric resources have been deployed, you can validate your SDN deployment end-to-end by deploying a sample tenant workload. This tenant workload consists of two virtual subnets (web tier and database tier) protected via Access Control List (ACL) rules using the SDN distributed firewall. The web tier's virtual subnet is accessible through the SLB/MUX using a Virtual IP (VIP) address. The script automatically deploys two web tier virtual machines and one database tier virtual machine and connects these to the virtual subnets. @@ -180,13 +178,13 @@ Now that fabric resources have been deployed, you can validate your SDN deployme 2. Run the script. For example: - ``` + ```PowerShell SDNExpress\scripts\SDNExpressTenant.ps1 -ConfigurationDataFile TenantConfig.psd1 -Verbose ``` 3. To undo the configuration, run the same script with the **undo** parameter. For example: - ``` + ```PowerShell SDNExpress\scripts\SDNExpressTenant.ps1 -Undo -ConfigurationDataFile TenantConfig.psd1 -Verbose ``` @@ -194,17 +192,17 @@ Now that fabric resources have been deployed, you can validate your SDN deployme To validate that the tenant deployment was successful, do the following: -1. Log into the database tier virtual machine and try to ping the IP address of one of the web tier virtual machines (ensure Windows Firewall is turned off in web tier virtual machines). +1. Log in to the database tier virtual machine and try to ping the IP address of one of the web tier virtual machines (ensure Windows Firewall is turned off in web tier virtual machines). 2. Check the network controller tenant resources for any errors. Run the following from any Hyper-V host with Layer-3 connectivity to the network controller: - ``` + ```PowerShell Debug-NetworkControllerConfigurationState -NetworkController ``` 3. To verify that the load balancer is running correctly, run the following from any Hyper-V host: - ``` + ```PowerShell wget /unique.htm -disablekeepalive -usebasicparsing ``` @@ -213,4 +211,4 @@ To validate that the tenant deployment was successful, do the following: > [!TIP] > Search for the `VIPIP` variable in TenantConfig.psd1. - Run this multiple times to see the load balancer switch between the available DIPs. You can also observe this behavior using a web browser. Browse to `/unique.htm`. Close the browser and open a new instance and browse again. You will see the blue page and the green page alternate, except when the browser caches the page before the cache times out. + Run this multiple times to see the load balancer switch between the available DIPs. You can also observe this behavior using a web browser. Browse to `/unique.htm`. Close the browser and open a new instance and browse again. You'll see the blue page and the green page alternate, except when the browser caches the page before the cache times out. diff --git a/WindowsServerDocs/virtualization/TOC.yml b/WindowsServerDocs/virtualization/TOC.yml index eba1bed065..aed070c608 100644 --- a/WindowsServerDocs/virtualization/TOC.yml +++ b/WindowsServerDocs/virtualization/TOC.yml @@ -4,10 +4,9 @@ - name: Guarded fabric and shielded VMs href: ../security/guarded-fabric-shielded-vm/guarded-fabric-and-shielded-vms-top-node.md - name: Hyper-V - href: hyper-v/Hyper-V-on-Windows-Server.md items: - - name: Technology Overview - href: hyper-v/Hyper-V-Technology-Overview.md + - name: Hyper-V overview + href: hyper-v/hyper-v-overview.md - name: System requirements href: hyper-v/System-requirements-for-Hyper-V-on-Windows.md - name: Supported Windows guest operating systems @@ -36,7 +35,6 @@ - name: Feature compatibility by generation and guest href: hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md - name: Get started - href: hyper-v/get-started/Get-started-with-Hyper-V-on-Windows.md items: - name: Install Hyper-V href: hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server.md @@ -45,12 +43,9 @@ - name: Create a virtual machine href: hyper-v/get-started/create-a-virtual-machine-in-Hyper-V.md - name: Plan - href: hyper-v/plan/Plan-Hyper-V-on-Windows-Server.md items: - - name: Compatibility - items: - - name: Guest operating system and application supportability - href: hyper-v/plan/guest-operating-system-application-supportability.md + - name: Guest operating system and application supportability + href: hyper-v/plan/guest-operating-system-application-supportability.md - name: VM Generation href: hyper-v/plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md - name: Networking @@ -68,8 +63,9 @@ - name: Virtual Fibre Channel for Hyper-V href: hyper-v/plan/virtual-fibre-channel-for-hyper-v.md - name: Deploy - href: hyper-v/deploy/Deploy-Hyper-V-on-Windows-Server.md items: + - name: Configure virtual local area networks for Hyper-V + href: hyper-v/deploy/configure-virtual-local-area-networks-for-hyper-v.md - name: Export and import virtual machines href: hyper-v/deploy/Export-and-import-virtual-machines.md - name: Set up hosts for live migration @@ -91,7 +87,6 @@ - name: Use GPUs with clustered VMs href: hyper-v/deploy/use-gpu-with-clustered-vm.md - name: Manage - href: hyper-v/manage/Manage-Hyper-V-on-Windows-Server.md items: - name: Configuring Persistent Memory Devices for Hyper-V VMs href: hyper-v/manage/persistent-memory-cmdlets.md diff --git a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-Server-2016.md b/WindowsServerDocs/virtualization/hyper-v/Hyper-V-Server-2016.md deleted file mode 100644 index 8c45cef6c3..0000000000 --- a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-Server-2016.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -description: "Learn more about: Microsoft Hyper-V Server 2016" -title: Microsoft Hyper-V Server 2016 -ms.topic: how-to -ms.assetid: f815ada0-4c63-4e73-9c24-dc5eb21526c7 -ms.author: wscontent -author: robinharwood -ms.date: 07/26/2017 ---- -# Microsoft Hyper-V Server 2016 - -Microsoft Hyper-V Server 2016 is a stand\-alone product that contains only the Windows hypervisor, a Windows Server driver model, and virtualization components. It provides a simple and reliable virtualization solution to help you improve your server utilization and reduce costs. - -The Windows hypervisor technology in Microsoft Hyper-V Server 2016 is the same as what's in the Hyper\-V role on Windows Server 2016. So, much of the content available for the Hyper\-V role on Windows Server 2016 also applies to Microsoft Hyper-V Server 2016. - -## Hyper\-V Server resources for IT Pros - -|Tasks|Resources| -|-|-| -|![Meets requirements symbol](media/All_Symbols_MeetsRequirements.png)|**Evaluate Hyper-V**

- [Hyper-V Technology Overview](hyper-v-technology-overview.md)
- [What's new in Hyper-V on Windows Server 2016](what-s-new-in-hyper-v-on-windows.md)
- [System requirements for Hyper-V on Windows Server 2016](system-requirements-for-hyper-v-on-windows.md)
- [Supported Windows guest operating systems for Hyper-V](supported-windows-guest-operating-systems-for-hyper-v-on-windows.md)
- [Supported Linux and FreeBSD Virtual Machines](supported-linux-and-freebsd-virtual-machines-for-hyper-v-on-windows.md)
- [Feature compatibility by generation and guest](hyper-v-feature-compatibility-by-generation-and-guest.md)

**Plan for Hyper-V**

- Decide which [virtual machine generation](plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v.md) meets your needs.
- If you're moving or importing virtual machines, decide when to [upgrade the version](deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server.md).
- [Scalability](plan/plan-hyper-v-scalability-in-windows-server.md)
- [Networking](plan/plan-hyper-v-networking-in-windows-server.md)
- [Security](plan/plan-hyper-v-security-in-windows-server.md)| -|![Get started symbol](media/All_Symbols_GetStarted.png)|**Get started with Hyper-V Server**

[Download and install Microsoft Hyper\-V Server 2016](https://www.microsoft.com/evalcenter/evaluate-hyper-v-server-2016). This installs the Windows hypervisor, a Windows Server driver model, and virtualization components. It's similar to running the Server Core installation option of Windows Server 2016 and the Hyper\-V role.| -|![Manage symbol](media/All_Symbols_Administrator.png)|**Configure and manage Hyper-V Server**

Hyper\-V Server doesn't have a graphical user interface \(GUI\). You can use the following tools to configure and manage Hyper\-V Server.

- [Configure a Server Core installation of Windows Server 2016 with Sconfig.cmd](../../administration/server-core/server-core-sconfig.md) to update domain or workgroup settings, change Windows Update settings, enable remote management, and more.
- Use an ordinary [command prompt](../../administration/windows-commands/windows-commands.md) for commands not available in Sconfig.
- Use [Hyper\-V Manager](./manage/remotely-manage-hyper-v-hosts.md) or [Virtual Machine Manager](/system-center/vmm) to remotely manage Hyper\-V Server. To use Hyper\-V Manager, [install the Hyper\-V role on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v) or [Windows Server 2016](get-started/install-the-hyper-v-role-on-windows-server.md).
- See [Install Server Core](../../get-started/getting-started-with-server-core.md) for additional management options for basic server functions that aren't specific to Hyper\-V. Most of the management methods documented there also work with Hyper\-V Server.

**Configure and manage Hyper\-V virtual machines**

- [Create a virtual switch for Hyper-V virtual machines](get-started/create-a-virtual-switch-for-hyper-v-virtual-machines.md)
- [Create a virtual machine in Hyper-V](get-started/create-a-virtual-machine-in-hyper-v.md)
- [Choose between standard or production checkpoints](manage/choose-between-standard-or-production-checkpoints-in-hyper-v.md)
- [Enable or disable checkpoints](manage/enable-or-disable-checkpoints-in-hyper-v.md)
- [Manage Windows virtual machines with PowerShell Direct](manage/manage-windows-virtual-machines-with-powershell-direct.md)

**Deploy**

- [Set up hosts for live migration without Failover Clustering](deploy/set-up-hosts-for-live-migration-without-failover-clustering.md)
- [Upgrade Windows Server cluster nodes](../../failover-clustering/cluster-operating-system-rolling-upgrade.md)
- [Upgrade virtual machine version](deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server.md)
| diff --git a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md b/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md index 8d209eb350..4c5437a495 100644 --- a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md +++ b/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md @@ -9,11 +9,14 @@ ms.date: 12/05/2016 --- # Hyper-V feature compatibility by generation and guest ->Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016 +>Applies to: Windows Server 2025 (preview), Windows Server 2022, Windows Server 2019, Windows Server 2016 + +> [!IMPORTANT] +> Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here. The tables in this article show you the generations and operating systems that are compatible with some of the Hyper-V features, grouped by categories. In general, you'll get the best availability of features with a generation 2 virtual machine that runs the newest operating system. -Keep in mind that some features rely on hardware or other infrastructure. For hardware details, see [System requirements for Hyper-V on Windows Server 2016](System-requirements-for-Hyper-V-on-Windows.md). In some cases, a feature can be used with any supported guest operating system. For details on which operating systems are supported, see: +Keep in mind that some features rely on hardware or other infrastructure. For hardware details, see [System requirements for Hyper-V on Windows Server](System-requirements-for-Hyper-V-on-Windows.md). In some cases, a feature can be used with any supported guest operating system. For details on which operating systems are supported, see: * [Supported Linux and FreeBSD virtual machines](Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md) * [Supported Windows guest operating systems](Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md) @@ -53,16 +56,16 @@ Feature | Generation | Guest operating system ------------- | ------------- | ----------- Hot add/removal of virtual network adapter | 2 | Any supported guest Legacy virtual network adapter | 1 | Any supported guest -Single root input/output virtualization (SR-IOV) | 1 and 2 | 64-bit Windows guests, starting with Windows Server 2012 and Windows 8. +Single root input/output virtualization (SR-IOV) | 1 and 2 | 64-bit Windows guests, starting with Windows Server 2012 and Windows 8. Virtual machine multi queue (VMMQ) | 1 and 2 | Any supported guest ## Remote connection experience Feature | Generation | Guest operating system ------------- | ------------- | ----------- -Discrete device assignment (DDA) | 1 and 2 | Windows Server 2016, Windows Server 2012 R2 only with Update 3133690 installed, Windows 10
**Note:** For details on Update 3133690, see [this](https://support.microsoft.com/kb/3133690) support article. -Enhanced session mode | 1 and 2 | Windows Server 2016, Windows Server 2012 R2, Windows 10, and Windows 8.1, with Remote Desktop Services enabled
**Note**: You might need to also configure the host. For details, see [Use local resources on Hyper-V virtual machine with VMConnect](./learn-more/Use-local-resources-on-Hyper-V-virtual-machine-with-VMConnect.md). -RemoteFx | 1 and 2 | Generation 1 on 32-bit and 64-bit Windows versions starting with Windows 8.
Generation 2 on 64-bit Windows 10 versions +Discrete device assignment (DDA) | 1 and 2 | Windows Server 2012 and later, Windows 10 and Windows 11
+Enhanced session mode | 1 and 2 | Windows Server 2012 R2 and later , and Windows 8.1 and later, with Remote Desktop Services enabled
**Note**: You might need to also configure the host. For details, see [Use local resources on Hyper-V virtual machine with VMConnect](./learn-more/Use-local-resources-on-Hyper-V-virtual-machine-with-VMConnect.md). +RemoteFx | 1 and 2 | Generation 1 on 32-bit and 64-bit Windows versions starting with Windows 8.
Generation 2 on 64-bit Windows 10 and Windows 11 versions ## Security @@ -75,8 +78,8 @@ Shielded virtual machines | 2 | **Windows**: All supported versions that can run Feature | Generation | Guest operating system ------------- | ------------- | ----------- -Shared virtual hard disks (VHDX only) | 1 and 2 | Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 +Shared virtual hard disks (VHDX only) | 1 and 2 | Windows Server 2012 and later SMB3 | 1 and 2 | All that support SMB3 -Storage spaces direct | 2 | Windows Server 2016 -Virtual Fibre Channel | 1 and 2 | Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 +Storage spaces direct | 2 | Windows Server 2016 and later +Virtual Fibre Channel | 1 and 2 | Windows Server 2012 and later VHDX format | 1 and 2 | Any supported guest diff --git a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-on-Windows-Server.md b/WindowsServerDocs/virtualization/hyper-v/Hyper-V-on-Windows-Server.md deleted file mode 100644 index d2a920b79f..0000000000 --- a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-on-Windows-Server.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Hyper-V on Windows Server -description: Provides links to key articles about trying out, planning, deploying, and managing Hyper-V -ms.topic: article -ms.assetid: 0baef6b8-598c-4fe0-9f31-5869fc4e0f69 -ms.author: wscontent -author: robinharwood -ms.date: 10/07/2016 ---- -# Hyper-V on Windows Server - ->Applies to: Windows Server 2022, Windows Server 2016, Windows Server 2019 - -The Hyper-V role in Windows Server lets you create a virtualized computing environment where you can create and manage virtual machines. You can run multiple operating systems on one physical computer and isolate the operating systems from each other. With this technology, you can improve the efficiency of your computing resources and free up your hardware resources. - -See the topics in the following table to learn more about Hyper-V on Windows Server. - -## Hyper-V resources for IT Pros - -|Task |Resources| -|---|---| -|![Check mark and document icon to show requirements are met](media/All_Symbols_MeetsRequirements.png)|**Evaluate Hyper-V**

- [Hyper-V Technology Overview](Hyper-V-Technology-Overview.md)
- [What's new in Hyper-V on Windows Server](What-s-new-in-Hyper-V-on-Windows.md)
- [System requirements for Hyper-V on Windows Server](System-requirements-for-Hyper-V-on-Windows.md)
- [Supported Windows guest operating systems for Hyper-V](Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md)
- [Supported Linux and FreeBSD virtual machines](Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md)
- [Feature compatibility by generation and guest](Hyper-V-feature-compatibility-by-generation-and-guest.md)

**Plan for Hyper-V**

- [Should I create a generation 1 or 2 virtual machine in Hyper-V?](plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md)
- [Plan for Hyper-V scalability in Windows Server](plan/plan-hyper-v-scalability-in-windows-server.md)
- [Plan for Hyper-V networking in Windows Server](plan/plan-hyper-v-networking-in-windows-server.md)
- [Plan for Hyper-V security in Windows Server](plan/plan-hyper-v-security-in-windows-server.md)| -|![Cursor and sunburst icon](media/All_Symbols_GetStarted.png)|**Get started with Hyper-V**

- [Download and install Windows Server 2019](https://www.microsoft.com/evalcenter/evaluate-windows-server-2019)

**Server Core or GUI installation option of Windows Server 2019 as virtual machine host**

- [Install the Hyper-V role on Windows Server](get-started/Install-the-Hyper-V-role-on-Windows-Server.md)
- [Create a virtual switch for Hyper-V virtual machines](get-started/Create-a-virtual-switch-for-Hyper-V-virtual-machines.md)
- [Create a virtual machine in Hyper-V](get-started/Create-a-virtual-machine-in-Hyper-V.md)| -|![Person and tools icon](media/All_Symbols_Administrator.png)|**Upgrade Hyper-V hosts and virtual machines**

- [Upgrade Windows Server cluster nodes](../../failover-clustering/Cluster-Operating-System-Rolling-Upgrade.md)
- [Upgrade virtual machine version](deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server.md)

**Configure and manage Hyper-V**

- [Set up hosts for live migration without Failover Clustering](deploy/Set-up-hosts-for-live-migration-without-Failover-Clustering.md)
- [Managing Nano Server remotely](../../get-started/manage-nano-server.md)
- [Choose between standard or production checkpoints](manage/Choose-between-standard-or-production-checkpoints-in-Hyper-V.md)
- [Enable or disable checkpoints](manage/Enable-or-disable-checkpoints-in-Hyper-V.md)
- [Manage Windows virtual machines with PowerShell Direct](manage/Manage-Windows-virtual-machines-with-PowerShell-Direct.md)
- [Set up Hyper-V Replica](manage/Set-up-Hyper-V-Replica.md)| -|![Conversation bubbles icon](media/All_Symbols_Chat.png)|**Blogs**

Check out the latest posts from Program Managers, Product Managers, Developers and Testers in the Microsoft Virtualization and Hyper-V teams.

- [Virtualization Blog](https://blogs.technet.com/b/virtualization/)
- [Windows Server Blog](https://blogs.technet.com/b/windowsserver/)
- [Ben Armstrong's Virtualization Blog](/archive/blogs/virtual_pc_guy/) (archived)| -|![User group icon](media/All_Symbols_Users_Group.png)|**Forum and newsgroups**

Got questions? Talk to your peers, MVPs, and the Hyper-V product team.

- [Windows Server Community](https://techcommunity.microsoft.com/t5/Windows-Server/ct-p/Windows-Server)
- [Windows Server Hyper-V TechNet forum](/answers/topics/windows-server-hyper-v.html)| - -## Related technologies - -The following table lists technologies that you might want to use in your virtualization computing environment. - -|Technology|Description| -|--------------|---------------| -|[Client Hyper-V](/virtualization/hyper-v-on-windows/index)|Virtualization technology included with Windows 8, Windows 8.1 and Windows 10 that you can install through **Programs and Features** in the **Control Panel**.| -|[Failover Clustering](../../failover-clustering/whats-new-in-failover-clustering.md)|Windows Server feature that provides high availability for Hyper-V hosts and virtual machines.| -|[Virtual Machine Manager](/system-center/vmm/overview)|System Center component that provides a management solution for the virtualized datacenter. You can configure and manage your virtualization hosts, networks, and storage resources so you can create and deploy virtual machines and services to private clouds that you've created.| -|[Windows Containers](/virtualization/windowscontainers/)|Use Windows Server and Hyper-V containers to provide standardized environments for development, test, and production teams.| diff --git a/WindowsServerDocs/virtualization/hyper-v/Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md b/WindowsServerDocs/virtualization/hyper-v/Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md index 9fa76f7692..e9e4052409 100644 --- a/WindowsServerDocs/virtualization/hyper-v/Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md +++ b/WindowsServerDocs/virtualization/hyper-v/Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md @@ -1,15 +1,18 @@ --- title: Supported Linux and FreeBSD virtual machines for Hyper-V on Windows Server and Windows -description: Lists the Linux and FreeBSD integration services and features included in each version +description: Lists the Linux and FreeBSD integration services and features included in each version. ms.topic: article ms.assetid: 990ff94a-30fb-434b-b4a2-3804a5245ba6 ms.author: wscontent author: robinharwood -ms.date: 09/26/2023 +ms.date: 08/13/2024 --- # Supported Linux and FreeBSD virtual machines for Hyper-V on Windows Server and Windows -> Applies to: Azure Stack HCI, Windows Server 2022, Windows Server 2019, Windows Server 2016, Hyper-V Server 2016, Windows Server 2012 R2, Hyper-V Server 2012 R2, Windows Server 2012, Hyper-V Server 2012, Windows Server 2008 R2, Windows 10, Windows 8.1, Windows 8, Windows 7.1, Windows 7 +> Applies to: Azure Stack HCI, Windows Server 2025 (preview), Windows Server 2022, Windows Server 2019, Windows Server 2016, Hyper-V Server 2016, Windows Server 2012 R2, Hyper-V Server 2012 R2, Windows Server 2012, Hyper-V Server 2012, Windows Server 2008 R2, Windows 10, Windows 8.1, Windows 8, Windows 7.1, Windows 7 + +> [!IMPORTANT] +> Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here. Hyper-V supports both emulated and Hyper-V-specific devices for Linux and FreeBSD virtual machines. When running with emulated devices, no additional software is required to be installed. However emulated devices do not provide high performance and cannot leverage the rich virtual machine management infrastructure that the Hyper-V technology offers. In order to make full use of all benefits that Hyper-V provides, it is best to use Hyper-V-specific devices for Linux and FreeBSD. The collection of drivers that are required to run Hyper-V-specific devices are known as Linux Integration Services (LIS) or FreeBSD Integration Services (BIS). diff --git a/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md b/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md index 301412224a..8997fda37f 100644 --- a/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md +++ b/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md @@ -4,7 +4,7 @@ description: Lists the Windows operating systems supported for use as a guest in ms.topic: conceptual ms.author: wscontent author: robinharwood -ms.date: 04/02/2024 +ms.date: 08/13/2024 --- # Supported Windows guest operating systems for Hyper-V on Windows Server and Azure Stack HCI @@ -46,7 +46,7 @@ The following table gives links to information about guest operating systems sup |Host operating system|Article| |-------------------------|---------| -|Windows 10|[Supported Guest Operating Systems for Client Hyper-V in Windows 10](/virtualization/hyper-v-on-windows/about/supported-guest-os)| +|Windows 10, 11|[Supported Guest Operating Systems for Client Hyper-V in Windows 10](/virtualization/hyper-v-on-windows/about/supported-guest-os)| |Windows Server 2012 R2 and Windows 8.1|- [Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012 R2 and Windows 8.1](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792027(v=ws.11))
- [Linux and FreeBSD Virtual Machines on Hyper-V](Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md)| |Windows Server 2012 and Windows 8|[Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012 and Windows 8](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792028(v=ws.11))| |Windows Server 2008 and Windows Server 2008 R2|[About Virtual Machines and Guest Operating Systems](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc794868(v=ws.10))| @@ -65,4 +65,4 @@ Microsoft provides support for guest operating systems in the following manner: - [Linux and FreeBSD Virtual Machines on Hyper-V](Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md) -- [Supported Guest Operating Systems for Client Hyper-V in Windows 10](/virtualization/hyper-v-on-windows/about/supported-guest-os) +- [Supported Guest Operating Systems for Client Hyper-V in Windows](/virtualization/hyper-v-on-windows/about/supported-guest-os) diff --git a/WindowsServerDocs/virtualization/hyper-v/System-requirements-for-Hyper-V-on-Windows.md b/WindowsServerDocs/virtualization/hyper-v/System-requirements-for-Hyper-V-on-Windows.md index 1e299ea323..5f89dd7bca 100644 --- a/WindowsServerDocs/virtualization/hyper-v/System-requirements-for-Hyper-V-on-Windows.md +++ b/WindowsServerDocs/virtualization/hyper-v/System-requirements-for-Hyper-V-on-Windows.md @@ -1,21 +1,24 @@ --- title: System requirements for Hyper-V on Windows Server -description: Lists the hardware and firmware requirements for Hyper-V in Windows Server +description: Lists the hardware and firmware requirements for Hyper-V in Windows Server. ms.topic: article ms.assetid: bc4a4971-f727-40cd-91f5-2ee6d24b54cb ms.author: wscontent author: robinharwood -ms.date: 9/30/2016 +ms.date: 08/13/2024 --- # System requirements for Hyper-V on Windows Server ->Applies to: Windows Server 2022, Windows Server 2016, Microsoft Hyper-V Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019 +>Applies to: Windows Server 2022 (preview), Windows Server 2016, Microsoft Hyper-V Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019 -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](https://www.windowsservercatalog.com/). Keep in mind that requirements for Hyper-V exceed the general minimum requirements for Windows Server 2016 because a virtualization environment requires more computing resources. +> [!IMPORTANT] +> Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here. -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 2012 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. +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](https://www.windowsservercatalog.com/). Keep in mind that requirements for Hyper-V exceed the general minimum requirements for Windows Server because a virtualization environment requires more computing resources. -For details about maximum supported configurations for Hyper-V, such as the number of running virtual machines, see [Plan for Hyper-V scalability in Windows Server 2016](./plan/plan-hyper-v-scalability-in-windows-server.md). The list of operating systems you can run in your virtual machines is covered in [Supported Windows guest operating systems for Hyper-V on Windows Server](Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md). +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 2012 R2. But, you'll 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 [Plan for Hyper-V scalability in Windows Server](/windows-server/virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server). The list of operating systems you can run in your virtual machines is covered in [Supported Windows guest operating systems for Hyper-V on Windows Server](/windows-server/virtualization/hyper-v/supported-windows-guest-operating-systems-for-hyper-v-on-windows). ## General requirements @@ -45,7 +48,7 @@ Scroll to the Hyper-V Requirements section to review the report. ## Requirements for specific features -Here are the requirements for discrete device assignment and shielded virtual machines. For descriptions of these features, see [What's new in Hyper-V on Windows Server](What-s-new-in-Hyper-V-on-Windows.md). +This section lists the requirements for discrete device assignment and shielded virtual machines. ### Discrete device assignment diff --git a/WindowsServerDocs/virtualization/hyper-v/deploy/Deploy-Hyper-V-on-Windows-Server.md b/WindowsServerDocs/virtualization/hyper-v/deploy/Deploy-Hyper-V-on-Windows-Server.md deleted file mode 100644 index 97cca2bd99..0000000000 --- a/WindowsServerDocs/virtualization/hyper-v/deploy/Deploy-Hyper-V-on-Windows-Server.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Deploy Hyper-V on Windows Server -description: Gives links to articles on deploying Hyper-V -ms.topic: article -ms.assetid: e13abdca-5412-4c0a-99f3-2ab83666ec66 -ms.author: wscontent -author: robinharwood -ms.date: 08/21/2019 ---- -# Deploy Hyper-V on Windows Server - ->Applies to: Windows Server 2022, Windows Server 2016, Microsoft Hyper-V Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019 - -Use these resources to help you deploy Hyper-V on Windows Server 2016. - -- [Configure virtual local area networks for Hyper-V](configure-virtual-local-areal-networks-for-Hyper-V.md) -- [Set up hosts for live migration without Failover Clustering](Set-up-hosts-for-live-migration-without-Failover-Clustering.md) -- [Upgrade virtual machine version in Hyper-V on Windows 10 or Windows Server 2016](Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server.md) -- [Deploy graphics devices using Discrete Device Assignment](deploying-graphics-devices-using-dda.md) -- [Deploy graphics devices using RemoteFX vGPU](deploy-graphics-devices-using-remotefx-vgpu.md) -- [Deploy storage devices using Discrete Device Assignment](deploying-storage-devices-using-dda.md) diff --git a/WindowsServerDocs/virtualization/hyper-v/deploy/configure-virtual-local-areal-networks-for-Hyper-V.md b/WindowsServerDocs/virtualization/hyper-v/deploy/configure-virtual-local-area-networks-for-hyper-v.md similarity index 99% rename from WindowsServerDocs/virtualization/hyper-v/deploy/configure-virtual-local-areal-networks-for-Hyper-V.md rename to WindowsServerDocs/virtualization/hyper-v/deploy/configure-virtual-local-area-networks-for-hyper-v.md index 5f0511a2e8..409bde2408 100644 --- a/WindowsServerDocs/virtualization/hyper-v/deploy/configure-virtual-local-areal-networks-for-Hyper-V.md +++ b/WindowsServerDocs/virtualization/hyper-v/deploy/configure-virtual-local-area-networks-for-hyper-v.md @@ -5,7 +5,7 @@ ms.topic: article ms.assetid: 8510a709-001c-4eee-b6d6-c451e8a8a836 ms.author: wscontent author: robinharwood -ms.date: 10/03/2023 +ms.date: 08/13/2024 --- # Configure virtual local area networks for Hyper-V diff --git a/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md b/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md index 81e9cb1df0..e154bc66c1 100644 --- a/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md +++ b/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md @@ -1,49 +1,53 @@ --- title: Create a virtual machine in Hyper-V -description: Gives instructions for creating a virtual machine using Hyper-V Manager or Windows PowerShell +description: Gives instructions for creating a virtual machine using Hyper-V Manager or Windows PowerShell. ms.topic: how-to ms.assetid: 59297022-a898-456c-b299-d79cd5860238 ms.author: alalve author: alanalves -ms.date: 02/22/2023 +ms.date: 08/13/2024 --- + # Create a virtual machine in Hyper-V ->Applies to: Windows Server 2022, Windows Server 2016, Microsoft Hyper-V Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019, Windows 11, Windows 10 +>Applies to: Windows Server 2025 (preview), Windows Server 2022, Windows Server 2016, Microsoft Hyper-V Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019, Windows 11, Windows 10 + +> [!IMPORTANT] +> Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here. Learn how to create a virtual machine by using Hyper-V Manager and Windows PowerShell and what options you have when you create a virtual machine in Hyper-V Manager. ## Create a virtual machine -#### [Hyper-V Manager](#tab/hyper-v-manager) +### [Hyper-V Manager](#tab/hyper-v-manager) 1. Open **Hyper-V Manager**. -2. From the **Action** pane, click **New**, and then click **Virtual Machine**. +1. From the **Action** pane, click **New**, and then click **Virtual Machine**. -3. From the **New Virtual Machine Wizard**, click **Next**. +1. From the **New Virtual Machine Wizard**, click **Next**. -4. Make the appropriate choices for your virtual machine on each of the pages. For more information, see [New virtual machine options and defaults in Hyper-V Manager](#options-in-hyper-v-manager-new-virtual-machine-wizard). +1. Make the appropriate choices for your virtual machine on each of the pages. For more information, see [New virtual machine options and defaults in Hyper-V Manager](#options-in-hyper-v-manager-new-virtual-machine-wizard). -5. After verifying your choices in the **Summary** page, click **Finish**. +1. After verifying your choices in the **Summary** page, click **Finish**. -6. In Hyper-V Manager, right-click the virtual machine and select **connect**. +1. In Hyper-V Manager, right-click the virtual machine and select **connect**. -7. In the Virtual Machine Connection window, select **Action** > **Start**. +1. In the Virtual Machine Connection window, select **Action** > **Start**. -#### [PowerShell](#tab/powershell) +### [PowerShell](#tab/powershell) 1. On the Windows desktop, click the Start button and type **Windows PowerShell**. -2. Right-click on **Windows PowerShell** and select **Run as administrator**. +1. Right-click on **Windows PowerShell** and select **Run as administrator**. -3. Get the name of the virtual switch that you want the virtual machine to use by using the [Get-VMSwitch](/powershell/module/hyper-v/get-vmswitch) cmdlet: +1. Get the name of the virtual switch that you want the virtual machine to use by using the [Get-VMSwitch](/powershell/module/hyper-v/get-vmswitch) cmdlet: ```powershell Get-VMSwitch * | Format-Table Name ``` -4. Use the [New-VM](/powershell/module/hyper-v/new-vm) cmdlet to create the virtual machine. See the following examples below: +1. Use the [New-VM](/powershell/module/hyper-v/new-vm) cmdlet to create the virtual machine. See the following examples below: > [!NOTE] > If you move this virtual machine to a Hyper-V host that runs Windows Server 2012 R2, use the **-Version** parameter with **[New-VM](/powershell/module/hyper-v/new-vm)** to set the virtual machine configuration version to 5. The default virtual machine configuration version for Windows Server 2016 isn't supported by Windows Server 2012 R2 or earlier versions. You can't change the virtual machine configuration version after the virtual machine is created. For more information, see [Supported virtual machine configuration versions](../deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server.md#supported-virtual-machine-configuration-versions). @@ -75,9 +79,9 @@ Learn how to create a virtual machine by using Hyper-V Manager and Windows Power New-VM -Name TestVM -MemoryStartupBytes 4GB -BootDevice VHD -NewVHDPath .\VMs\Test.vhdx -Path .\VMData -NewVHDSizeBytes 20GB -Generation 2 -Switch ExternalSwitch ``` - - **New virtual hard disk that boots to operating system image** - To create a virtual machine with a new virtual disk that boots to an operating system image, see the PowerShell example in [Create virtual machine walkthrough for Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/create-virtual-machine). + - **New virtual hard disk that boots to operating system image** - To create a virtual machine with a new virtual disk that boots to an operating system image, see the PowerShell example in [Create virtual machine walkthrough for Hyper-V on Windows](/virtualization/hyper-v-on-windows/quick-start/create-virtual-machine). -5. Start the virtual machine by using the [Start-VM](/powershell/module/hyper-v/start-vm) cmdlet. Run the following cmdlet where Name is the name of the virtual machine you created: +1. Start the virtual machine by using the [Start-VM](/powershell/module/hyper-v/start-vm) cmdlet. Run the following cmdlet where Name is the name of the virtual machine you created: ```powershell Start-VM -Name @@ -89,7 +93,7 @@ Learn how to create a virtual machine by using Hyper-V Manager and Windows Power Start-VM -Name TestVM ``` -6. Connect to the virtual machine by using Virtual Machine Connection (VMConnect): +1. Connect to the virtual machine by using Virtual Machine Connection (VMConnect): ```powershell VMConnect.exe diff --git a/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-switch-for-Hyper-V-virtual-machines.md b/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-switch-for-Hyper-V-virtual-machines.md index ac112abe98..050b640bbc 100644 --- a/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-switch-for-Hyper-V-virtual-machines.md +++ b/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-switch-for-Hyper-V-virtual-machines.md @@ -1,26 +1,27 @@ --- title: Create and configure a virtual switch with Hyper-V -description: Learn how to create and configure a virtual switch for use by the Hyper-V host and guest virtual machines. You can use Hyper-V Manager or PowerShell to create and configure your virtual switch. +description: Learn how to create and configure a virtual switch for use by the Hyper-V host and guest virtual machines. ms.topic: how-to ms.assetid: fdc8063c-47ce-4448-b445-d7ff9894dc17 ms.author: roharwoo author: robinharwood -ms.date: 12/02/2022 +ms.date: 08/13/2024 --- # Create and configure a virtual switch with Hyper-V -> Applies to: Windows Server 2022, Windows 10, Windows Server 2016, Microsoft Hyper-V Server 2016, +> Applies to: Windows Server 2025 (preview), Windows Server 2022, Windows 10, Windows Server 2016, Microsoft Hyper-V Server 2016, > Windows Server 2019, Microsoft Hyper-V Server 2019 +> [!IMPORTANT] +> Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here. + This article shows you how to create and configure your virtual switch using Hyper-V Manager or PowerShell. A virtual switch allows virtual machines created on Hyper-V hosts to communicate -with other computers. When you first install the Hyper-V role on Windows Server, you can optionally -create a virtual switch at the same time. To learn more about virtual switches, see +with other computers. When you first install the Hyper-V role on Windows Server, you can optionally create a virtual switch at the same time. To learn more about virtual switches, see [Hyper-V Virtual Switch](../../hyper-v-virtual-switch/Hyper-V-Virtual-Switch.md). -For more information about how you can set up your networking infrastructure with Windows Server, -review the [Networking](../../../networking/index.yml) documentation. +For more information about how you can set up your networking infrastructure with Windows Server, review the [Networking](../../../networking/index.yml) documentation. ## Prerequisites @@ -206,8 +207,7 @@ command. Learn more about ## Next step -Now you've created and configured your virtual switch, here are other articles to help you continue -with Hyper-V. +Now you've created and configured your virtual switch, here are other articles to help you continue with Hyper-V. - Learn about [Switch Embedded Teaming (SET)](/azure-stack/hci/concepts/host-network-requirements#switch-embedded-teaming-set). - Learn how to [create a virtual machine in Hyper-V](Create-a-virtual-machine-in-Hyper-V.md). diff --git a/WindowsServerDocs/virtualization/hyper-v/get-started/Get-started-with-Hyper-V-on-Windows.md b/WindowsServerDocs/virtualization/hyper-v/get-started/Get-started-with-Hyper-V-on-Windows.md deleted file mode 100644 index 6bde4727b7..0000000000 --- a/WindowsServerDocs/virtualization/hyper-v/get-started/Get-started-with-Hyper-V-on-Windows.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Get started with Hyper-V on Windows Server -description: Gives links to articles on getting started with Hyper-V -ms.topic: how-to -ms.assetid: 9a3f8b74-f3c0-433f-a320-850ca8610757 -ms.author: wscontent -author: robinharwood -ms.date: 10/07/2016 ---- -# Get started with Hyper-V on Windows Server - ->Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Microsoft Hyper-V Server 2019, Microsoft Hyper-V Server 2016 - -Use the following resources to set up and try out Hyper-V on the Server Core or GUI installation option of Windows Server 2022. But before you install anything, check the [System Requirements for Windows Server](../../../get-started/hardware-requirements.md) and the [System Requirements for Hyper-V](../System-requirements-for-Hyper-V-on-Windows.md). - -- [Download and install Windows Server](https://www.microsoft.com/evalcenter/evaluate-windows-server-2019) - -- [Install the Hyper-V role on Windows Server](Install-the-Hyper-V-role-on-Windows-Server.md) -- [Create a virtual switch for Hyper-V virtual machines](Create-a-virtual-switch-for-Hyper-V-virtual-machines.md) -- [Create a virtual machine in Hyper-V](Create-a-virtual-machine-in-Hyper-V.md) diff --git a/WindowsServerDocs/virtualization/hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server.md b/WindowsServerDocs/virtualization/hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server.md index 9b02a2309f..4883750069 100644 --- a/WindowsServerDocs/virtualization/hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server.md +++ b/WindowsServerDocs/virtualization/hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server.md @@ -1,20 +1,23 @@ --- title: Install the Hyper-V role on Windows Server -description: Gives instructions for installing Hyper-V using Server Manager or Windows PowerShell +description: Gives instructions for installing Hyper-V using Server Manager or Windows PowerShell. ms.topic: how-to ms.assetid: 8e871317-09d2-4314-a6ec-ced12b7aee89 ms.author: wscontent author: robinharwood -ms.date: 09/19/2023 +ms.date: 08/13/2023 --- # Install the Hyper-V role on Windows Server ->Applies to: Windows Server 2022, Windows Server 2016, Windows Server 2019 +>Applies to: Windows Server 2025 (preview), Windows Server 2022, Windows Server 2016, Windows Server 2019 + +> [!IMPORTANT] +> Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here. 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 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v). +For Windows 10 and Windows 11, see [Install Hyper-V on Windows](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v). -To learn more about Hyper-V, see the [Hyper-V Technology Overview](../Hyper-V-Technology-Overview.md). To try out Windows Server 2019, you can download and install an evaluation copy. See the [Evaluation Center](https://www.microsoft.com/evalcenter/evaluate-windows-server-2019). +To learn more about Hyper-V, see the [Hyper-V Technology Overview](../Hyper-V-Technology-Overview.md). To learn more about Hyper-V, see the [Hyper-V Overview](../Hyper-V-Technology-Overview.md). To try out Windows Server 2025, you can download and install an evaluation copy. See the [Evaluation Center](https://www.microsoft.com/evalcenter/evaluate-windows-server-2025). Before you install Windows Server or add the Hyper-V role, make sure that: diff --git a/WindowsServerDocs/virtualization/hyper-v/manage/Manage-Hyper-V-on-Windows-Server.md b/WindowsServerDocs/virtualization/hyper-v/manage/Manage-Hyper-V-on-Windows-Server.md deleted file mode 100644 index 3c96397eba..0000000000 --- a/WindowsServerDocs/virtualization/hyper-v/manage/Manage-Hyper-V-on-Windows-Server.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Manage Hyper-V on Windows Server -description: Gives links to articles on managing Hyper-V -ms.topic: article -ms.assetid: 5c06b632-dd19-46ca-9f51-130c321963d8 -author: robinharwood -ms.author: wscontent -ms.date: 01/08/2018 ---- -# Manage Hyper-V on Windows Server - ->Applies to: Windows Server 2022, Windows Server 2016, Windows Server 2019 - -Use the resources in this section to help you manage Hyper-V on Windows Server: - -- [Configuring Persistent Memory Devices for Hyper-V VMs](persistent-memory-cmdlets.md) -- [Choose between standard or production checkpoints](Choose-between-standard-or-production-checkpoints-in-Hyper-V.md) -- [Create a VHD set](Create-VHDSet-file.md) -- [Enable or disable checkpoints](Enable-or-disable-checkpoints-in-Hyper-V.md) -- [Manage hosts with Hyper-V Manager](Remotely-manage-Hyper-V-hosts.md) -- [Manage host CPU resource controls](manage-hyper-v-minroot-2016.md) -- [Using VM CPU Groups](manage-hyper-v-cpugroups.md) -- [Manage hypervisor scheduler types](manage-hyper-v-scheduler-types.md) -- [About Hyper-V scheduler type selection](about-hyper-v-scheduler-type-selection.md) -- [Manage Integration Services](Manage-Hyper-V-integration-services.md) -- [Manage Windows VMs with PowerShell Direct](Manage-Windows-virtual-machines-with-powershell-direct.md) -- [Set up Hyper-V Replica](Set-up-Hyper-V-Replica.md) -- [Enable Intel Performance Monitoring Hardware](Performance-Monitoring-Hardware.md) -- [Move VMs with live migration](Live-migration-overview.md) diff --git a/WindowsServerDocs/virtualization/hyper-v/manage/Set-up-Hyper-V-Replica.md b/WindowsServerDocs/virtualization/hyper-v/manage/Set-up-Hyper-V-Replica.md index 86b05d5aaf..8ad4c80245 100644 --- a/WindowsServerDocs/virtualization/hyper-v/manage/Set-up-Hyper-V-Replica.md +++ b/WindowsServerDocs/virtualization/hyper-v/manage/Set-up-Hyper-V-Replica.md @@ -54,7 +54,7 @@ Here's what you should verify before you begin: ### Step 1: Set up the Hyper-V hosts -You'll need at least two Hyper-V hosts with one or more virtual machines on each server. [Get started with Hyper-V](../get-started/Get-started-with-Hyper-V-on-Windows.md). The host server that you'll replicate virtual machines to will need to be set up as the replica server. +You'll need at least two Hyper-V hosts with one or more virtual machines on each server. Get started and [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server). The host server that you'll replicate virtual machines to will need to be set up as the replica server. 1. In the Hyper-V settings for the server you'll replicate virtual machines to, in **Replication Configuration**, select **Enable this computer as a Replica server**. diff --git a/WindowsServerDocs/virtualization/hyper-v/manage/manage-hyper-v-scheduler-types.md b/WindowsServerDocs/virtualization/hyper-v/manage/manage-hyper-v-scheduler-types.md index 07eb9fede7..099118b519 100644 --- a/WindowsServerDocs/virtualization/hyper-v/manage/manage-hyper-v-scheduler-types.md +++ b/WindowsServerDocs/virtualization/hyper-v/manage/manage-hyper-v-scheduler-types.md @@ -46,7 +46,7 @@ For the purposes of this article, the descriptions of SMT and how it's used by H ### Understand how Hyper-V virtualizes processors -Before considering hypervisor scheduler types, you should understand Hyper-V architecture. You can find a more detailed summary of how this architecture works in the [Hyper-V technology overview](../hyper-v-technology-overview.md), but for now, you should keep the following concepts in mind: +Before considering hypervisor scheduler types, you should understand Hyper-V architecture. You can find a more detailed summary of how this architecture works in the [Hyper-V overview](../hyper-v-overview.md), but for now, you should keep the following concepts in mind: - Hyper-V creates and manages VM partitions, allocating and sharing compute resources across them, under control of the hypervisor. Partitions provide strong isolation boundaries between all guest VMs and between guest VMs and the root partition. diff --git a/WindowsServerDocs/virtualization/hyper-v/plan/Plan-Hyper-V-on-Windows-Server.md b/WindowsServerDocs/virtualization/hyper-v/plan/Plan-Hyper-V-on-Windows-Server.md deleted file mode 100644 index f04fc9b6bd..0000000000 --- a/WindowsServerDocs/virtualization/hyper-v/plan/Plan-Hyper-V-on-Windows-Server.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Plan for Hyper-V on Windows Server 2016 -description: Gives links to articles on planning considerations for Hyper-V -ms.topic: article -ms.assetid: fba1e964-3ac3-4852-83dc-eb20752765fd -ms.author: wscontent -author: robinharwood -ms.date: 08/21/2019 ---- -# Plan for Hyper-V on Windows Server - ->Applies to: Windows Server 2022, Windows Server 2016, Windows Server 2019 - -Use these resources to help you plan your Hyper-V deployment. - -- [Hyper-V scalability in Windows Server](plan-hyper-v-scalability-in-windows-server.md) -- [Hyper-V security in Windows Server](plan-hyper-v-security-in-windows-server.md) -- [Networking in Windows Server](plan-hyper-v-networking-in-windows-server.md) -- [Should I create a generation 1 or 2 virtual machine?](Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md) -- [Plan for GPU acceleration in Windows Server](plan-for-gpu-acceleration-in-windows-server.md) -- [Plan for deploying devices using Discrete Device Assignment](plan-for-deploying-devices-using-discrete-device-assignment.md) diff --git a/WindowsServerDocs/virtualization/virtualization.yml b/WindowsServerDocs/virtualization/virtualization.yml index 80940cc0f0..2244d99a44 100644 --- a/WindowsServerDocs/virtualization/virtualization.yml +++ b/WindowsServerDocs/virtualization/virtualization.yml @@ -32,13 +32,13 @@ landingContent: url: /virtualization/windowscontainers/about/containers-vs-vm # Card - - title: Hyper-V on Windows 10 + - title: Hyper-V on Windows linkLists: - linkListType: overview links: - - text: Hyper-V on Windows 10 overview + - text: Hyper-V on Windows overview url: /virtualization/hyper-v-on-windows - - text: About Hyper-V on Windows 10 + - text: About Hyper-V on Windows url: /virtualization/hyper-v-on-windows/about/ - linkListType: get-started links: @@ -52,16 +52,18 @@ landingContent: linkLists: - linkListType: overview links: - - text: Hyper-V on Windows Server - url: hyper-v/Hyper-V-on-Windows-Server.md - - text: Hyper-V Technology Overview - url: hyper-v/Hyper-V-Technology-Overview.md - - linkListType: reference - links: - - text: Microsoft Hyper-V Server 2016 - url: ./hyper-v/hyper-v-server-2016.md - - text: System requirements for Hyper-V on Windows Server + - text: Hyper-V overview + url: hyper-v/hyper-v-overview.md + - text: System requirements for Hyper-V url: hyper-v/System-requirements-for-Hyper-V-on-Windows.md + - text: Supported Windows guest operating systems + url: hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md + - linkListType: get-started + links: + - text: Install the Hyper-V role + url: hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server.md + - text: Create a virtual machine + url: hyper-v/get-started/create-a-virtual-machine-in-Hyper-V.md # Card - title: Hyper-V Virtual Switch