Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » virtualization » microsoft » hyper-v
Trace: • licensing_rds
virtualization:microsoft:hyper-v

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
virtualization:microsoft:hyper-v [2013/01/21 12:57]
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://www.sonoracomm.com/wiki/doku.php?do=search&id=hyper-v|more Hyper-V pages]]**. +See also **[[https://virtualarchitects.com/wiki/doku.php?do=search&id=start&q=hyper-v|more Hyper-V pages]]** 
 + 
 +See also **[[computing:windows:windows_core|Windows Core Configuration]]**
  
 http://blogs.technet.com/b/keithmayer/archive/2012/09/07/getting-started-with-hyper-v-server-2012-hyperv-virtualization-itpro.aspx http://blogs.technet.com/b/keithmayer/archive/2012/09/07/getting-started-with-hyper-v-server-2012-hyperv-virtualization-itpro.aspx
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:microsoft:hyper-v-remote-mgmt|Hyper-V Remote Management]]**
  
 On a Windows management workstation: On a Windows management workstation:
Line 72: Line 76:
  
 ===== NIC Teaming (NIC Bonding) ===== ===== 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 is now built into Windows Server 2012 and is vendor independent.
  
 NIC Teaming User Guide: http://www.microsoft.com/en-us/download/details.aspx?id=30160 NIC Teaming User Guide: http://www.microsoft.com/en-us/download/details.aspx?id=30160
 +
 +http://www.aidanfinn.com/?p=12646
  
 http://blogs.technet.com/b/privatecloud/archive/2012/06/19/nic-teaming-in-windows-server-2012-brings-simple-affordable-traffic-reliability-and-load-balancing-to-your-cloud-workloads.aspx http://blogs.technet.com/b/privatecloud/archive/2012/06/19/nic-teaming-in-windows-server-2012-brings-simple-affordable-traffic-reliability-and-load-balancing-to-your-cloud-workloads.aspx
Line 81: Line 91:
 http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/02eaa377-8a1e-43f1-ad8b-4227138742d0 http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/02eaa377-8a1e-43f1-ad8b-4227138742d0
  
 +==== NIC Team Creation with PowerShell ====
 +
 +<file>
 +Get-NetAdapter -Physical
 +
 +New-NetLbfoTeam Team1 "Network 2","Network 3" -LoadBalancingAlgorithm HyperVPort
 +</file>
  
 +  * List NIC names
 +  * Load Balancing + Failover
 +  * Name is "Team1"
 +  * Switch Independent Mode
 +    * Switch does **not** require advanced features (LACP)
 +  * 'Generic' or 'Static' team
 +    * 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 139: Line 164:
  
 ===== Hyper-V Management ===== ===== Hyper-V Management =====
 +
 +See also **[[computing:windows:windows_core|Windows Core Configuration]]**
  
  * Microsoft Hyper-V Server only has a limited text console (sconfig.cmd) for local management.  There is also a command prompt available.  * Microsoft Hyper-V Server only has a limited text console (sconfig.cmd) for local management.  There is also a command prompt available.
Line 145: Line 172:
  
  * The **Microsoft System Center Virtual Machine Manager (SCVMM)** has been renamed to **Microsoft System Center 2012**.  These are commercial tools for managing Hyper-V.  * The **Microsoft System Center Virtual Machine Manager (SCVMM)** has been renamed to **Microsoft System Center 2012**.  These are commercial tools for managing Hyper-V.
- 
-==== vtUtilities for Local Management ==== 
- 
-https://vttechnology.com/Products/vtUtilities 
  
 ==== Hyper-V Manager MMC ==== ==== Hyper-V Manager MMC ====
virtualization/microsoft/hyper-v.1358798228.txt.gz · Last modified: 2013/01/21 12:57 by gcooper

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki