|
Powershell is everywhere. So is Hyper-V. It makes sense that these would find each other. They did. Not in the place where you would expect it but isn't it always like that?
At codeplex you will find the project to provide a PowerShell management library for Hyper-V. It
does pretty much what it says. Note that a lot of the information
available from Hyper-V is only available if Powershell is running with
Elevated privilege
At present there are 66 functions in the
library, some of these are worker functions which are not expected to
be called directly, the others are listed below
Finding a VM
Get-VM, Choose-VM
Connecting to a VM
New-VMConnectSession
Discovering and manipulating Machine states
List-VMState , Set-VMState , Convert-VmState,
Ping-VM , Shutdown-VM , Start-VM, Stop-VM, Suspend-VM
Get-VMKVP
Backing up, exporting and snapshotting VMs
Backup-vm
, Export-VM , Get-VMSnapshot, Choose-VMSnapshot , Apply-VMSnapshot ,
New-VMSnapshot ,Remove-VMSnapshot, Get-VMSnapshotTree
Adding and removing VMs, configuring motherboard settings.
New-VM , Remove-VM , Set-VM , Get-VMCPUCount, Set-VMCPUCount, Get-VMMemory, Set-VMMemory
Manipulating Disk controllers, drives and disk images
Get-VMDiskController
Add-VMSCSIController , Remove-VMSCSIcontroller
Get-VMDrive , Add-VMDRIVE , Remove-VMdrive
Get-VMDisk, Add-VMDISK , Set-VMDisk, List-VMDisk
Get-VMFloppyDisk , Add-VMFloppyDisk
Add-VMNewHardDisk
Manipluating Network Interface Cards
Get-VMNic , List-VMNic , Choose-VMNIC, Add-VMNIC, Remove-VMNIC , Set-VMNICAddress , Set-VMNICConnection , Get-VMNicport ,
Get-VMnicSwitch, Choose-VMSwitch, New-VMSwitchPort, Get-VMByMACaddress
Working with VHD files
Get-VHDDefaultPath, Get-VHDInfo, New-VHD, Compact-VHD, Mount-VHD, Unmount-VHD.
Check it out here .
|
