This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
virtualization:microsoft:hyper-v [2013/01/21 10:31] gcooper |
virtualization:microsoft:hyper-v [2019/05/20 11:29] (current) gcooper |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Microsoft Hyper-V Server ====== | ====== Microsoft Hyper-V Server ====== | ||
- | See also **[[https:// | + | See also **[[https:// |
+ | |||
+ | See also **[[computing: | ||
http:// | http:// | ||
Line 10: | Line 12: | ||
:!: Note that Microsoft Hyper-V requires hardware virtualization support in the mainboard and CPU. Windows Server 8 will also require SLAT for Hyper-V. | :!: Note that Microsoft Hyper-V requires hardware virtualization support in the mainboard and CPU. Windows Server 8 will also require SLAT for Hyper-V. | ||
+ | |||
+ | :!: Don't try to run an app directly from the root of C:. Create a folder and run the app from the folder. | ||
Microsoft virtualization comes in two basic flavors: | Microsoft virtualization comes in two basic flavors: | ||
Line 28: | Line 32: | ||
===== Driver Installation ===== | ===== Driver Installation ===== | ||
- | ==== Remote Management | + | See also **[[virtualization: |
On a Windows management workstation: | On a Windows management workstation: | ||
Line 70: | Line 74: | ||
sc delete < | sc delete < | ||
</ | </ | ||
+ | |||
+ | ===== NIC Teaming (NIC Bonding) ===== | ||
+ | |||
+ | :!: You should configure NIC teaming after installing drivers and before network configuration. | ||
+ | |||
+ | :!: You will have to reconfigure the server networking after configuring NIC teaming. | ||
+ | |||
+ | :!: NIC Teaming is now built into Windows Server 2012 and is vendor independent. | ||
+ | |||
+ | NIC Teaming User Guide: http:// | ||
+ | |||
+ | http:// | ||
+ | |||
+ | http:// | ||
+ | |||
+ | http:// | ||
+ | |||
+ | ==== NIC Team Creation with PowerShell ==== | ||
+ | |||
+ | < | ||
+ | Get-NetAdapter -Physical | ||
+ | |||
+ | New-NetLbfoTeam Team1 " | ||
+ | </ | ||
+ | |||
+ | * List NIC names | ||
+ | * Load Balancing + Failover | ||
+ | * Name is " | ||
+ | * Switch Independent Mode | ||
+ | * Switch does **not** require advanced features (LACP) | ||
+ | * ' | ||
+ | * As opposed to IEEE 802.1ax Link Aggregation Control Protocol (LACP) | ||
+ | * Connected to the Hyper-V external switch | ||
===== Hyper-V Server Configuration ===== | ===== Hyper-V Server Configuration ===== | ||
Line 127: | Line 164: | ||
===== Hyper-V Management ===== | ===== Hyper-V Management ===== | ||
+ | |||
+ | See also **[[computing: | ||
* Microsoft Hyper-V Server only has a limited text console (sconfig.cmd) for local management. | * Microsoft Hyper-V Server only has a limited text console (sconfig.cmd) for local management. | ||
Line 133: | Line 172: | ||
* The **Microsoft System Center Virtual Machine Manager (SCVMM)** has been renamed to **Microsoft System Center 2012**. | * The **Microsoft System Center Virtual Machine Manager (SCVMM)** has been renamed to **Microsoft System Center 2012**. | ||
- | |||
- | ==== vtUtilities for Local Management ==== | ||
- | |||
- | https:// | ||
==== Hyper-V Manager MMC ==== | ==== Hyper-V Manager MMC ==== | ||
Line 193: | Line 228: | ||
http:// | http:// | ||
- | * You must be a member of the Administrators user group to run the tools | + | :!: You must be a member of the Administrators user group to run the tools |
Install the tools: | Install the tools: |