Manage Hyper-V with PowerShell

Windows PowerShell has been gradually gaining in prominence for the past few years, but the release of PowerShell 3.0 with Windows Server 2012 really kicked PowerShell into high gear. Microsoft added 2,300 new cmdlets to Server 2012. More than 160 of them enable you to manage Hyper-V. Prior to Server 2012 and PowerShell 3.0, you had to use either the Hyper-V cmdlets that were part of Microsoft System Center Virtual Machine Manager (VMM) or CodePlex’s PowerShell Management Library for Hyper-V. With Server 2012, PowerShell 3.0 has effectively eliminated the need to use the Hyper-V cmdlets in VMM or the CodePlex library. (Note that if you’re running PowerShell 3.0 on Windows 8, Windows Server 2008 R2, or Windows Server 2008, that’s not the case. You still need to use the Hyper-V cmdlets in VMM or the CodePlex library.)

SHVM30 the all GUI Powershell Hyper-V Manager 

There are two versions:

PSHVM standaloneversion 3.0

Works great and has all the features you need

An intergrated PSHVM 3.0 with Corefig 1.1

Can be accessed as either standalone or from within corefig Main page Hyperv Manger Button

to see the pictures of what the standalone version looks like visit:

Use it from the core 2012 server console or it can even run on the GUI server 2012, I have tested it on both.

SEE DISCUSSIONS IF YOU ALREADY DOWNLOADED AND HAVE A VHOST VIRTUAL PATH ISSUE.

Features:

  1. File Manager with shortcuts at the bottom to launch apps
  2. Set the Virtual Machine and HardDisk paths for the VHost
  3. Create/Remove a vSwitch
  4. Advanced NIC and vSwitch features like NIC Teaming (thanks to Eric Siron)
  5. Create a new vm with a new VHDx file or from and existing VHDx
  6. Start/Stop/Connect to a VM
  7. Manage VM’s DVD/ISO.. Eject/Insert/Insert MS tools
  8. Rename/Remove/Delete a VM (can even save the files for redeploy)
  9. Export a VM
  10. Import a VM
  11. Edit the VM’s Name, RAM Amount, vCPU Count, NIC’s, Networks/vSwitch(s) and Virtual Disks
  12. Gather an Inventory Report of the VHost and VM’s
  13. Tools that link to: Command prompt, Task Manager, Registry Editor, System Info, Services, Event Viewer and Firewall settings.

To see the entire list of new cmdlets for Hyper-V, check out TechNet’s Hyper-V Cmdlets in Windows PowerShell web page. If you’re using Server 2008 R2 or Server 2008, you might want to read the Windows IT Pro article “PowerShell Basics: System Requirements” or TechNet’sInstalling Windows PowerShell web page to see how you can install PowerShell 3.0 on older Windows releases.

Hyper-V is Microsoft’s server virtualization solution that competes with Citrix XenServer, VMware ESXi, and Red Hat Enterprise Virtualization. Windows Server 2012 ships with Hyper-V, which boasts the largest virtual machines currently available and the most flexible virtualization platform with features such as Secure Boot, PXE boot, Live Export, and UEFI firmware support. This article explores Hyper-V via PowerShell version 4.0 on Windows Server 2012 R2.

PowerShell 4.0, the latest version of the scripting language, is the most powerful version to date. To get version 4.0, download and install the Windows Management Framework 4.0 package from theMicrosoft’s Download Center.

Managing Hyper-V with PowerShell

You can install and manage Hyper-V using the GUI or PowerShell. With PowerShell, you can accomplish most of the tasks that you can accomplish with the GUI.

Before you can begin managing Hyper-V with PowerShell or the GUI, you need to make sure the Hyper-V role isinstalled on the Server 2012 systems you want to use as virtualization hosts. You can install the Hyper-V role using Server Manager, or you can install it with the PowerShell command:

Install-WindowsFeature -Name Hyper-V `
-ComputerName ORPORTHV3 -IncludeManagementTools -Restart

This command installs the Windows Feature named Hyper-V on the computer named ORPORTHV3. When running this command, make sure that you include the -IncludeManagementTools parameter. This will install the Hyper-V Manager and the PowerShell module for Hyper-V.

Afterward, you can use the Get-Command cmdlet with the -Module Hyper-V parameter to see the available cmdlets for the Hyper-V module:

Be the first to comment on "Manage Hyper-V with PowerShell"

Leave a comment

Your email address will not be published.