Greetings..
PowerCLI version 5.0
ESXi 5.0 U2 hosts
vCenter 5.5
I am trying to relocate VMs from one Datastore to another and change Disk type to Thick Eager Zeroed from Lazy Zeroed. The following script keeps failing.
Any ideas? or Point me to the discussion that can help on here please?
$DST = Get-Datastore -Name XXDC_41
# Define Target VM and Target Disk
$Disk = Get-VM -Name vCO-x01 | Get-HardDisk -Name "Hard Disk 1"
Set-HardDisk -HardDisk $Disk -Datastore $DST -StorageFormat eagerZeroedThick -Confirm:$false
Set-HardDisk : Cannot bind parameter 'StorageFormat'. Cannot convert value "eagerZeroedThick" to type
"VMware.VimAutomation.ViCore.Types.V1.VirtualDevice.VirtualDiskStorageFormat". Error: "Unable to match the identifier name eagerZeroedThick to a
valid enumerator name. Specify one of the following enumerator names and try again: Thin2GB, Thick, Thick2GB, Thin"
In PowerCLI 5.0 the eager zeroed thick format wasn't a supported option. There's the 5.0 doc (
https://www.vmware.com/support/developer/PowerCLI/PowerCLI50/html/Set-HardDisk.html) showing no EagerZeroedThick option. In PowerCLI 5.5 and later EagerZeroedThick was available (
https://www.vmware.com/support/developer/PowerCLI/PowerCLI55/html/Set-HardDisk.html)
If you can I'd suggest you upgrade to PowerCLI 5.8 (will work fine with vCenter 5.5 and VUM 5.5) and then you'll have what you need, and can be used with your 5.0 hosts without any issues. 6.0 is the latest, however the VUM components are version specific (i.e. 6.0 Update Manager for PowerCLI can't manage VUM 5.5).
Alternatively you'll need to use the underlying API rather than the much easier to use cmdlets
In PowerCLI 5.0 the eager zeroed thick format wasn't a supported option. There's the 5.0 doc (
https://www.vmware.com/support/developer/PowerCLI/PowerCLI50/html/Set-HardDisk.html) showing no EagerZeroedThick option. In PowerCLI 5.5 and later EagerZeroedThick was available (
https://www.vmware.com/support/developer/PowerCLI/PowerCLI55/html/Set-HardDisk.html)
If you can I'd suggest you upgrade to PowerCLI 5.8 (will work fine with vCenter 5.5 and VUM 5.5) and then you'll have what you need, and can be used with your 5.0 hosts without any issues. 6.0 is the latest, however the VUM components are version specific (i.e. 6.0 Update Manager for PowerCLI can't manage VUM 5.5).
Alternatively you'll need to use the underlying API rather than the much easier to use cmdlets
Thank you so much!