Hyper-V Management with PowerShell

This week we were faced with the challenge to Install and configure a Virtual Machine from Windows 2008 Hyper-V Server Core and found these tools and websites essentials for the task of Hyper-V Management with PowerShell:

Hyper-V Remote Management Configuration Utility
http://code.msdn.microsoft.com/HVRemote

Blogger - Senior Program Manager for the Hyper-V Team at Microsoft
http://blogs.technet.com/b/jhoward/archive/2008/11/14/configure-hyper-v-remote-management-in-seconds.aspx

Another blogger PowerShell and Beyond - PowerShell on Server Core
http://dmitrysotnikov.wordpress.com/2008/05/15/powershell-on-server-core/

PowerShell Management Library for Hyper-V
http://pshyperv.codeplex.com/releases/view/38769

All of this is necessary if you don't have any other OS like WIN 7, Vista, or Windows 2008 full feature GUI

NIC Teaming - Broadcom network interface card (NIC) teaming fails.

The following steps may result in a NIC teaming failure:

• One of the Broadcom NICs that was used in NIC teaming fails or is disabled. Due to the availability of the second NIC, private network is still active on this node through the second NIC.
• When the first NICs is still down or disabled, the second NIC in the teaming also fails or is disabled. This failure causes the private network to go down completely on this node. The private IP address on this node cannot be pinged.
• When the second NIC that failed or was disabled becomes enabled, the private network of this node remains inactive.

The most likely cause of this issue is a Spanning Tree Protocol on your switch. If this issue is caused by a Spanning Tree Protocol, perform one of the following procedures:

• Turn off Spanning Tree on the switch.
• Enable Port Fast Learning (or equivalent) on the ports of the switch to which your teamed NICs are attached.
• Use Broadcom's LiveLink feature by right-clicking the team, choosing Enable LiveLink, and following the instructions in the window.