Please provide your feedback in this short Flings' survey.
The VSAN Cmdlet functionality of this Fling has been integrated into a release of PowerCLI and due to this we recommend you use the latest supported version of PowerCLI, which can be downloaded here.
Dec 12, 2019

Hello,
can some one tell me why I'm getting this error plz.

PS C:\> import-module vmware.vimautomation.extensions -verbose
VERBOSE: Loading module from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\vmware.vimautomation.extensions.psd1'.
VERBOSE: Loading 'Assembly' from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\InternalVimService60.dll'.
VERBOSE: Loading 'Assembly' from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\InternalVimService60.dll'.
VERBOSE: Loading 'Assembly' from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\VMware.VimAutomation.Extensions.dll'.
VERBOSE: Loading 'Assembly' from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\VMware.VimAutomation.Extensions.dll'.
VERBOSE: Loading 'FormatsToProcess' from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\VMware.VimAutomation.Extensions.Format.ps1xml'.
VERBOSE: Loading module from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\Initialize-VMware_VimAutomation_Extensions.ps1'
.
VERBOSE: Dot-sourcing the script file
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\Initialize-VMware_VimAutomation_Extensions.ps1'
.
VERBOSE: Loading module from path
'C:\Users\Administrator\Documents\WindowsPowerShell\Modules\vmware.vimautomation.extensions\VMware.VimAutomation.Extensions.dll'.
import-module : Method 'get_CreateDate' in type 'VMware.VimAutomation.Extensions.InstantClone.Types.InstantCloneVirtualMachineImpl' from
assembly 'VMware.VimAutomation.Extensions, Version=3.0.0.1649, Culture=neutral, PublicKeyToken=null' does not have an implementation.
At line:1 char:1
+ import-module vmware.vimautomation.extensions -verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Import-Module], TypeLoadException
+ FullyQualifiedErrorId : System.TypeLoadException,Microsoft.PowerShell.Commands.ImportModuleCommand

PS C:\>

Sep 20, 2017

Hello,

I'm using the PowerCLI 6.5 R1 Extenstions in a vSphere 6.5 environment and I'm receiving an error with some hosts in my environment when using the Get-VMHostVFlashConfiguration cmdlet.

$ESXi = "esxi.hostname.fqdn"
$localDisk = Get-ScsiLun -VMHost $ESXi | Where {$_.CapacityGB -eq 372}
### checks occur to ensure $localDisk is marked for Flash
$vFlashConfig = Get-VMHostVFlashConfiguration -VMHost $ESXi
$vFlashDisk = $localDisk | Get-VMHostDisk
If ($vFlashConfig.CapacityGB -eq 0) {Set-VMHostVFlashConfiguration -VFlashConfiguration $vFlashConfig -AddDevice $vFlashDisk}

The error occurs when setting the $vFlashConfig variable.
Get-VMHostVFlashConfiguration The object 'vim.HostSystem:host-xxx' has already been deleted or has not been completely created.

CategoryInfo: NotSpecified: (:) [Get-VMHostVFlashConfiguration], Managed ObjectNotFound
FullQualifiedErrorID: VICore_StorageServiceImpl_GetVMHostVFlashConfigurationViewListSingleHost_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Host.Storage.GetVMHostVFlashConfiguration

This error occurred on several of the ESXi hosts in our environment. We successfully used the extension cmdlets to configure vFlash on most of the hosts which are the same model (Dell M630 blades). I manually configured vFlash successfully on a few of the hosts that had this error (that is to say, every hosts I attempted was configured successfully but I did not attempt to configure them all) but still received the same error message when running the above command after vFlash is configured. Not sure if this is a problem with the cmdlet or there is an issue with my hosts that have this error.

Jul 17, 2016

Trying this with PowerCLI 6.3 R1 with the version for 6.3R1 and higher in the downloads. However, I get this error when attempting to load the module.

PowerCLI C:\> import-module VMware.VimAutomation.Extensions
import-module : Could not load file or assembly 'file:///C:\Program Files (x86)\VMware\Infrastructure\vSphere
PowerCLI\Modules\VMware.VimAutomation.Extensions\VMware.VimAutomation.Extensions.dll' or one of its dependencies.
Operation is not supported. (Exception from HRESULT: 0x80131515)
At line:1 char:1
+ import-module VMware.VimAutomation.Extensions
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Import-Module], FileLoadException
+ FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.ImportModuleCommand

Running on Windows 10

PowerCLI C:\> $PSVersionTable

Name Value
---- -----
PSVersion 5.0.10586.494
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.10586.494
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Jul 18, 2016

Probably because files downloaded from the web are blocked. Can you try go through all the files of the Extensions module and do:

Right Click - > Properties -> Tick "Unblock" check box -> OK

Then try to import the module in a new PS sessions?

-Dimitar Milov

Jul 18, 2016

Thanks Dimitar :)
There was no unblock after I'd unzipped and that's probably why I didn't catch this earlier. I went back to the .Zip and found the unblock, after that, I extracted it and placed it in my module path and everything worked great!

Mar 26, 2016

I'm Japanese.

PowerCLI 6.3 R1 in use.
I get an error similar to the following

Enable-InstantCloneVM : 2016/03/26 99:99:99 Enable-InstantCloneVM メソッドが見つかりません: 'System.Web.Services.Protocols.SoapHttpClientProtocol VMware.Vim.VimClient.get_VimService()'

*メソッドが見つかりません = Not Fount Methods

Might PowerCLI of the problem.
In PowerCLI 6.0 R1, this phenomenon has stored as not to reproduce.