Differences

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

--- virtualization:microsoft:hyper-v [2013/01/21 10:25]
gcooper
+++ virtualization:microsoft:hyper-v [2019/05/20 11:29] (current)
gcooper
@@ Line 1: / Line 1: @@
 ====== 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
@@ 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.
+:!: 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:
@@ Line 28: / Line 32: @@
 ===== Driver Installation =====
-==== Remote Management ====
+See also **[[virtualization:microsoft:hyper-v-remote-mgmt|Hyper-V Remote Management]]**
 On a Windows management workstation:
@@ Line 70: / Line 74: @@
 sc delete <service_name>
 </file>
+===== 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://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://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 =====
@@ Line 127: / Line 164: @@
 ===== 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.
@@ Line 133: / 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.
-==== vtUtilities for Local Management ====
-https://vttechnology.com/Products/vtUtilities
 ==== Hyper-V Manager MMC ====
@@ Line 193: / Line 228: @@
 http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d
-  * 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:
+**Start -> Control Panel -> Programs -> Programs and Features -> Turn Windows features on or off -> Remote Server Administration Tools**
+Run the Hyper-V Manager:
+**Start -> Administrative Tools -> Hyper-V Manager**
 ==== Microsoft System Center ====

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools