PSHyperv Work Item Rss Feed

Commented Issue: In Windows 8, module load fails with 'Missing argument in parameter list' error. [9620]

andreww9r — Wed, 23 Jan 2013 17:15:03 GMT

PowerShell V3 in Windows 8 seems to be more strict about syntax and HyperV module fails to load:
 
PS>Import-Module .\HyperV.psd1
At D:\HyperV\Menu.ps1:276 char:79
+ 20 { $SelectedVHD = (Select-List -InputObject $vhd -Property ,@ ...
+ ~
Missing argument in parameter list.
At D:\HyperV\Menu.ps1:1141 char:79
+ 20 { $SelectedVHD = (Select-List -InputObject $vhd -Property ,@ ...
+ ~
Missing argument in parameter list.
 + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
 + FullyQualifiedErrorId : MissingArgument
Comments: ** Comment from web user: andreww9r **

Got the same on 2008 R2 as well. Not just Windows 8 by the look of it.

Created Issue: Feature Request: PsGet Installation Support [9807]

legigor — Sun, 30 Dec 2012 15:57:42 GMT

https://github.com/psget/psget

Would be cool to have this lib available there

Commented Issue: In Windows 8, module load fails with 'Missing argument in parameter list' error. [9620]

johnroster — Wed, 03 Oct 2012 09:43:29 GMT

This worked for me. It appears in two places within the menu.ps1 file

Commented Issue: Change time synchronisation setting [4641]

sjwarren — Wed, 26 Sep 2012 15:43:47 GMT

Hi,

I would like to change the time synchronisation setting for a virtual machine but cannot get this to work. Is it possible to include this in the library?

It's the time sync option under Integrated Services. I want it to go to disabled.

Regards

Mozart
Comments: ** Comment from web user: sjwarren **

I meant, do you have a code example of how to set this time sync setting?

Commented Issue: Change time synchronisation setting [4641]

sjwarren — Wed, 26 Sep 2012 15:41:57 GMT

Do you have an example of how to set this time sync setting?

Created Issue: Mount-VHD, Dismount-VHD do not work for remote server. [9621]

vladimia — Wed, 05 Sep 2012 20:59:48 GMT

Mount-VHD and Dismount-VHD cmdlets have -Server parameter but not really using it and all intrinsic WMI calls are executed against the local computer. This parameter is not exposed in the help for those cmdlets as well. This is quite embarrassing and must be an oversight, since it is very easy to fix and affects so many scenarios.

Commented Issue: In Windows 8, module load fails with 'Missing argument in parameter list' error. [9620]

vladimia — Wed, 05 Sep 2012 18:09:53 GMT

PowerShell V3 in Windows 8 seems to be more strict about syntax and HyperV module fails to load:

PS>Import-Module .\HyperV.psd1
At D:\HyperV\Menu.ps1:276 char:79
+ 20 { $SelectedVHD = (Select-List -InputObject $vhd -Property ,@ ...
+ ~
Missing argument in parameter list.
At D:\HyperV\Menu.ps1:1141 char:79
+ 20 { $SelectedVHD = (Select-List -InputObject $vhd -Property ,@ ...
+ ~
Missing argument in parameter list.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArgument
Comments: ** Comment from web user: vladimia **

Suggested fix:

change from

20 { $SelectedVHD = (Select-List -InputObject $vhd -Property ,@{Name="Name"; expression={$_.Name -replace ($folder+"\").replace("\","\\"),""}}).name }

20 { $SelectedVHD = (Select-List -InputObject $vhd -Property @(@{Name="Name"; expression={$_.Name -replace ($folder+"\").replace("\","\\"),""}}).name) }

Created Issue: In Windows 8, module load fails with 'Missing argument in parameter list' error. [9620]

vladimia — Wed, 05 Sep 2012 18:00:38 GMT

Created Issue: Add a compatibility layer for the Windows 8 Hyper-V module [9284]

jstangroome — Wed, 04 Apr 2012 10:51:40 GMT

In Windows 8, a PowerShell module for managing Hyper-V is included:
http://technet.microsoft.com/library/hh848559.aspx

However this module appears to only work with the version of Hyper-V included with Windows 8.

To minimise the scripting effort in a mixed environment of old and new Hyper-V hosts this module for the Server 2008 version Hyper-V should have aliases and basic wrapper functions added so that it has the same cmdlet names, accepts the same parameters and returns objects with the same properties wherever feasible.

Commented Issue: Scripts forget $HyperVNamespace [8362]

jstangroome — Sat, 31 Mar 2012 22:00:12 GMT

After a while using the pshyperv stuff, I get "Get-WmiObject : Invalid class"

If I set $HyperVNamespace back to 'root\virtualization', it starts working again.
Comments: ** Comment from web user: jstangroome **

Using a root script module to dot-source the module's *.ps1 files instead of referring to them using the ModuleManifest's NestedModules fixes this bug. See attachment for updated files.

Commented Issue: Setup failed [8326]

andreww9r — Tue, 27 Mar 2012 11:22:05 GMT

At the last step of the setup, when the console pops up, I got the following error message:

Import-Module : File C:\Program Files\modules\hyperV\en-us.ps1 cannot be loaded
because the execution of scripts is disabled on this system. Please see "get-h
elp about_signing" for more details.
At line:1 char:14
+ Import-Module <<<< 'C:\Program Files\modules\hyperV'
+ CategoryInfo : NotSpecified: (:) [Import-Module], PSSecurityExc
eption
+ FullyQualifiedErrorId : RuntimeException,Microsoft.PowerShell.Commands.I
mportModuleCommand
Comments: ** Comment from web user: andreww9r **

Unblock, but be CAREFUL you don't run that command from your filesystem root !! Unzip files to c:\psv for example and do

cd c:\psv
unblock -d -s *.*

Created Issue: SET-VMNICVlan - failing due to moved parameters in source code [9254]

KamilRT — Mon, 19 Mar 2012 04:32:59 GMT

There is wrong syntax in Network.ps1 file - line 524, column 62.
Original source code:
foreach-object {Get-WmiObject -Namespace -ComputerName $Nic.__Server $HyperVNamespace -q "associators of {$_} where assocClass=MSVM_NetWorkElementSettingData"}

should be:
foreach-object {Get-WmiObject -ComputerName $Nic.__Server -Namespace $HyperVNamespace -q "associators of {$_} where assocClass=MSVM_NetWorkElementSettingData"}

Created Issue: Add-VMNewHardDisk [9245]

DanielHeth — Wed, 14 Mar 2012 23:20:55 GMT

The original code within the R2 version was incorrectly working. I've fixed it as written below.

Issues:
1. The VHDPath variable was being ignored if it was an absolute path and not a scriptblock.
2. corrected the ParentVHDPath by adding the documented "ParentVHD" as an alias
3. Also corrected the ParentVHD variable within the function which was calling a completely different variable... resulting in the inability to create a differencing disk.

Function Add-VMNewHardDisk
{# .ExternalHelp MAML-VMDisk.XML
[CmdletBinding(SupportsShouldProcess=$True)]
param(
[parameter(Mandatory = $true, ValueFromPipeline = $true)]
$VM,
[int]$ControllerID=0,
[int]$LUN=0,

[ValidateNotNullOrEmpty()]
$VHDPath,

[ValidateRange(1,2040GB)]
[long]$Size = 127GB,

[ValidateNotNullOrEmpty()][Alias("ParentDiskPath","ParentPath","ParentVHD")]
$ParentVHDPath,

[ValidateNotNullOrEmpty()]
[string]$Server = ".",
[switch]$Fixed,
[switch]$SCSI,
$PSC,
[switch]$Force
)
process {
if ($psc -eq $null) {$psc = $pscmdlet} ; if (-not $PSBoundParameters.psc) {$PSBoundParameters.add("psc",$psc)}
if ($VM -is [String]) {$VM = Get-VM -Name $VM -Server $Server}
if ($VM.count -gt 1 -and -not $VHdPath) {[Void]$PSBoundParameters.Remove("VM") ; $VM | ForEach-object {Add-VMNewHardDisk -VM $_ @PSBoundParameters}}
if ($VHDPath -is [scriptblock]) { $NewVHD = Invoke-Expression ".{$VHDPath}" } else { $NewVHD = $VHDPath }
if ($VM.__CLASS -eq 'Msvm_ComputerSystem') {
if (-not $NewVHD) { $NewVHD = (Get-VhdDefaultPath $vm.__Server) + "\" + ($vm.elementname + ".VHD") }

if ($ParentVHDPath) { $vhd = New-VHD -wait -Psc $PSC -force:$force -Server $VM.__Server -VhdPath $NewVHD -ParentVHD $parentVHDPath }
elseif ($fixed) { $vhd = New-VHD -wait -Psc $PSC -force:$force -Server $VM.__Server -VhdPath $NewVHD -Size $size -Fixed }
else { $vhd = New-VHD -wait -Psc $PSC -force:$force -Server $VM.__Server -VhdPath $NewVHD -Size $size }
$drive = Add-VMDRIVE -psc $PSC -force:$force -VM $VM -ControllerID $ControllerID -LUN $LUN -scsi:$scsi
Add-VMDISK -psc $PSC -force:$force -DriveRASD $Drive -VHDPath $vhd.path
}
}
}

Created Issue: Importing Module twice cause Invalid Class issue [9137]

VirtuallyAware — Mon, 23 Jan 2012 17:21:40 GMT

When importing the HyperV module twice, there you get a WMI Invalid Class error. See Screen print. Check to see if module is already loaded?

Created Issue: Export-VM get-help -detailed has erratum in Parameters -VM section [8727]

olbilyk — Mon, 26 Sep 2011 11:06:19 GMT

It states

PARAMETERS
-VM [<>]
The Virtual Machine(s) to IMPORT.

Created Issue: Feature Req: Need to get and Set VM "Scope of Residence" [8716]

xWakawaka — Fri, 23 Sep 2011 00:12:06 GMT

I've been doing a lot of hyper-v delegation work recently, where I have to set the scope of the VM so I can assocaite permissions to that scope.

Doing this requires going through some WMI gymnastics and assocaitors. I can get the scope with a series of WMI queries, but can't figure out how to set it with this method http://msdn.microsoft.com/en-us/library/cc136809(v=VS.85).aspx . Please add this functionality (getting and setting VM scope) to your wonderful module.

Commented Issue: Set-VMDisk Problem [5474]

djsecrist — Tue, 06 Sep 2011 20:28:17 GMT

Hi, I have tried the Set-VMDisk to mount the dvd drive on my vm "abc" by the following command:

Set-VMDisk "abc" 1 1 (Get-WmiObject -Query "Select * From win32_cdromdrive Where ID='D:' " ).deviceID

however I got the following error:
Comments: ** Comment from web user: djsecrist **

I am getting this same error using the same command as the original commenter. I am running Hyper-V Server R2 SP1 and using the latest library download for R2 SP1. The only difference is the error trace shows the error on line 57 in the new script (was line 56 in the original). Can you please help? Thanks.

Created Issue: VMIntegrationComponent how to localize [8610]

Jobau — Sun, 14 Aug 2011 18:35:48 GMT

The functions Get-VMIntegrationComponent and Set-VMIntegrationComponent (and as a result also the function Get-VMBuildScript) are not working on some localized installations of windows server. The problem result from the localized value of the wmi element "AllocationUnits" (in e.g. Msvm_VssComponentSettingData) which has e.g. in German the translated value "Integrationskomponenten" instead of "Integration Components".
A solution could replace for function Get-VMIntegrationComponent (VMConfig.ps1) the original line
(Get-vmSettingData -vm $vm -Server $Vm.__server).getRelated() | Where-Object {$_.allocationUnits -eq "integration Components"} |
with
(Get-vmSettingData -vm $vm -Server $Vm.__server).getRelated() | Where-Object {$_.allocationUnits -like "Integration*"} |

Additional replace for function Set-VMIntegrationComponent (VMConfig.ps1) the original line
where-object {($_.allocationUnits -eq "integration Components") -and ($_.elementName -like "$c*")} |
with
where-object {($_.allocationUnits -like "Integration*") -and ($_.elementName -like "$c*")} |
I’m not sure if this will work with all localizations but at least it works for English an German.

Created Issue: Typo in column name [8578]

Fiury — Sat, 06 Aug 2011 18:28:24 GMT

After sumbiting following command:
get-vm -name 10165* | get-vmmemory
I got the following output:
WARNING: column "Buffer" does not fit into the display and was removed.

VMElmentName Dynamic Enabled Virtual Quantity Limit Reservation Weight
------------ --------------- ---------------- ----- ----------- ------
10165A-NYC-DC1-B True 256 1024 256 0
10165A-NYC-DC1-A True 256 1536 256 0

As you can see there is a typo in the first coulmn name. The first "e" letter is omitted.

Regards,
Tomek A.

Created Issue: Import-VM ImportVirtualSystem Method Deprecated [8567]

jeffpatton — Wed, 03 Aug 2011 17:19:35 GMT

Per the online help of the Import-VM cmdlet, ImportVirtualSystem has been deprecated in favor of ImportVirtualSystemEx. This most likely is why the import-vm cmdlet doesn't seem to do anything at all.