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!
Hey that was really good, but what about non-internet connected servers that you might need to install PowerCLI on? (Off-line install)
At the moment there is no offline install, or at least that what it looks like.
You can download the 6.5 Release 1 version from your my.vmware.com under any vSphere product via the Drivers and Tools Tab.
I was able to work around the offline install failure by copying the “C:\Program Files\WindowsPowerShell\Modules\VMware.*” folders from a machine that updated successfully.
Pingback: VMware PowerCLI 6.5.1 Installation Walkthrough Video
really thanks for the installation video. Definitely helped cleared up some technical misunderstanding on my part.
Pingback: PowerCLI 6.5.1 Installation Walkthrough – Techilia
Pingback: Creating shortcuts for PowerCLI that automatically log you in. | The Lowercase w
great video . I have successfully installed powerCLI 6.5.1 . Thanks for sharing with us .
Still get the error
WARNING: Package ‘VMware.VimAutomation.Core’ failed to download.
PackageManagement\Install-Package : Dependent Package ‘VMware.VimAutomation.Core’ failed to install.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:2089 char:20
+ … $sid = PackageManagement\Install-Package @PSBoundParameters
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidResult: (VMware.VimAutomation.Core:String) [Install-Package], Exception
+ FullyQualifiedErrorId : DependentPackageFailedInstallOrDownload,Microsoft.PowerShell.PackageManagement.Cmdlets.I
nstallPackage
multiple version of windows (10/2008r2/2012r2), multiple PS version (4/5/5.1), running elevated scope current user and all users
Common thing en-NZ (or NOT en-US I guess)
Any ideas?
Hello all,
Having the Problem within loadin a dll/assembly, but its in the $env:PSModulePath
PS H:\> Connect-VIServer -Server vciwtgd01
Connect-VIServer : Could not load file or assembly ‘VMware.VimAutomation.Logging.SoapInterceptor, Version=1.0.0.646, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system cannot find the file specified.
At line:1 char:1
+ Connect-VIServer -Server vciwtgd01
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Connect-VIServer], FileNotFoundException
+ FullyQualifiedErrorId : System.IO.FileNotFoundException,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer
There isnt alot to find by google with that error.
Any ideas?
Thanks
Oli
Hi Oli. I was getting the same issue.. Until I remembered I needed to go to the control panel and uninstall the previous old vmware powercli that was installed using the old traditional setup.exe.. this resolved the error I was getting which is the exact same error your seeing on connecting to a vcenter.
Thanks Chris! That was the solution…
Received a Microsoft Visual C++ Runtime Library runtime error R6034 when attempting to install the vmware.powercli module.
Are you still having this issue?
If so, make sure all prior versions of PowerCLI have been uninstalled. (If you uninstalled any previous version, might be worth rebooting as well)
Try the ‘install-module -name vmware.powercli -scope currentuser’ command again.
If you’re still having issues after that, please send me an email: kruddy at vmware dot com
It seems vmware is highly committed to this decision. Any complaints are met with “But the new way is better!”.
Working in a disconnected, highly secure DoD environment makes this a no go for us. I shouldn’t have to try to find a way around security or download on my home computer to get my updates.
Please swallow your pride and offer an msi in addition to the Gallery.
Chris: I’m not sure where you’re receiving the ‘the new way is better’ treatment, but myself and the the Product Manager have been more than happy to discuss this transition. We’d love to understand what complications this process is adding within your environment. Please drop me an email so we can discuss this further: kruddy at vmware dot com
Great comment Chris . And that’s not all : Improvements (“better”) means you should’nt have this hassles . I’m not a advanced user and i need to strive to be at surface of all this Super(it)Mans coding people … what happened to kiss ? why a normal user has to suffer for the sake of this ? IT used to mean ‘simplification of processes’ … nowadays it means hours of lost work to retrieve solutions for small details . congrats
Can you expand on what you’re suffering with?
With PowerCLI versions 6.5.1 and newer, the PowerCLI installation process was turning into a PowerShell one-liner. It doesn’t get much easier than that!
Hello, I can install and list all modules when I run with an elevated powershell users, but nothing when I run with a normal account. I tried to change the scope to allusers but nothing. What am I missing?
I haven’t been able to reproduce this, but you’re not the only one that has run into this issue. By any chance, have you tired ‘Install-Module -Name VMware.PowerCLI -Scope AllUsers -Force’ ?
Perhaps the force parameter will kick things back into an operational manner for all users.
This is frustrating – I can’t get it to install.
§ DESKTOP Find-Module -Name VMware.PowerCLI
Version Name Repository Description
——- —- ———- ———–
6.5.4.7… VMware.PowerCLI PSGallery This Windows PowerShell module contains VMware.P…
Good! Onto the next step
§ DESKTOP Install-Module -Name VMware.PowerCLI –Scope AllUsers -Force
WARNING: Unable to resolve package source ‘https://www.powershellgallery.com/api/v2/’.PackageManagement\Install-Package : No match was found for the specified search criteria and module name ‘VMware.PowerCLI’. Try Get-PSRepository to see all available registered module repositories.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1809 char:21
+ … $null = PackageManagement\Install-Package @PSBoundParameters
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Microsoft.Power….InstallPackage:InstallPackage) [Install-Package], Exception
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage
Well, let me try again just to find the module
§ DESKTOP Find-Module -Name VMware.PowerCLI
WARNING: Unable to resolve package source ‘https://www.powershellgallery.com/api/v2/’.PackageManagement\Find-Package : No match was found for the specified search criteria and module name ‘VMware.PowerCLI’. Try Get-PSRepository to see all available registered module repositories.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1397 char:3
+ PackageManagement\Find-Package @PSBoundParameters | Microsoft …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Microsoft.Power…ets.FindPackage:FindPackage) [Find-Package], Exception
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage
I’ve fixed my issue. I have a custom PS profile and environment variables. I was able to get this working by saving the VMware.PowerCLI packages locally, then copying the extracted folders underneath several of the $ENV:PSModulePath folders. I had three of them specified and as such, I copied three sets of the extracted folders.
The little mention of AllUsers Module folder location pointed me to C:\Windows\System32\WindowsPowerShell\v1.0\Modules.
The mention of CurrentUser Module folder location pointed me to my profile location\Modules – which was E:\path\My Documents\WindowsPowerShell\Modules
Then of course, there’s another one under C:\Program Files\WindowsPowerShell\Modules…
After that, I was able to install and import.
On my other machine without customized PS profiles and locations, just using Microsoft’s default – the module installed fine from the repo.
Thanks for this, Kyle- super-helpful.