PowerCLI 6.5.1 Installation Walkthrough

We released PowerCLI 6.5.1 two weeks ago and the response has been incredible! The VMware.PowerCLI module is closing in on 4,000 downloads from the PowerShell Gallery and we’ve received a ton of good feedback.

There seems to be quite a few questions and comments over this new installation method so I created a walkthrough video to illustrate the process for PowerShell version 5.0 as well as for versions 3.0 and 4.0. We’ve also collected the most common errors and issues during the installation process and included troubleshooting steps for those below.

Walkthrough Video

Common Troubleshooting Steps

If there happens to be an issue during the installation process, here’s a couple of the top tips we have seen on working around them:

The process cannot access the file ‘C:\Users\…\AppData\Local\Temp\…’
- Ensure previous versions of PowerCLI are uninstalled and all PowerShell sessions are closed.
- Verify the file isn’t being blocked by an antivirus software.
A command with name ‘verb-noun’ is already available on this system.
- This is due to a module already available on the system containing that cmdlet. The more common example modules include FailoverClusters and HyperV.
- Append “-AllowClobber” to the Install-Module command line.
  Example: Install-Module –Name VMware.PowerCLI –Scope CurrentUser –AllowClobber
No match was found for the specified search criteria and module name ‘VMware.PowerCLI’
- This could be due to a lack of connectivity to the PowerShell Gallery.
- If a proxy can be used, the “Install-Module” cmdlet can configure proxy connectivity with the “Proxy” and “ProxyCredential” parameters.
  Example: Install-Module –Name VMware.PowerCLI –Scope CurrentUser –Proxy ‘http://my.proxy.company.com’
Could not get response from query ‘https://www.powershellgallery.com/api/v2/package/VMware.VimAutomation.Core/…’
- This warning is just indicating there is an issue establishing connectivity to the PowerShell Gallery. Retry the installation at a later point in time and it should succeed.

Summary

We are really excited about this release and what this means for the future of PowerCLI! Upgrade to PowerCLI 6.5.1 today, and keep that feedback rolling in!

Common Troubleshooting Steps

If there happens to be an issue during the installation process, here’s a couple of the top tips we have seen on working around them:

The process cannot access the file ‘C:\Users\…\AppData\Local\Temp\…’

Ensure previous versions of PowerCLI are uninstalled and all PowerShell sessions are closed.
Verify the file isn’t being blocked by an antivirus software.

A command with name ‘verb-noun’ is already available on this system.

This is due to a module already available on the system containing that cmdlet. The more common example modules include FailoverClusters and HyperV.
Append “-AllowClobber” to the Install-Module command line.
Example: Install-Module –Name VMware.PowerCLI –Scope CurrentUser –AllowClobber

No match was found for the specified search criteria and module name ‘VMware.PowerCLI’

This could be due to a lack of connectivity to the PowerShell Gallery.
If a proxy can be used, the “Install-Module” cmdlet can configure proxy connectivity with the “Proxy” and “ProxyCredential” parameters.
Example: Install-Module –Name VMware.PowerCLI –Scope CurrentUser –Proxy ‘http://my.proxy.company.com’

Could not get response from query ‘https://www.powershellgallery.com/api/v2/package/VMware.VimAutomation.Core/…’

This warning is just indicating there is an issue establishing connectivity to the PowerShell Gallery. Retry the installation at a later point in time and it should succeed.