It’s release day and we have another terrific update ready for you. VMware PowerCLI 10.1.1 includes some very important updates specifically for the Horizon View folks!
PowerCLI 10.1.1 includes brand new support for Horizon View 7.5. This is quite significant because Horizon View was released just a few short weeks ago and had quite a few amazing updates as well. More information about the Horizon View 7.5 release is available: Horizon 7.5 View Release Notes
There are two other notable improvements which came thanks to the community! The first is around an issue where users were receiving ‘insufficient privileges’ when attempting to connect to the Horizon View server. The second is around an issue where users would occasionally receive an error message of ‘the request channel timed out while waiting for a reply after 00:01:39.9969495’. Both of these have been updated and should now work as intended!
Summary
VMware PowerCLI 10.1.1 is continuing to show the evolution in our processes to be able to bring the latest and greatest features to you faster and faster. With this release, there are new APIs available from Horizon View 7.5 plus a couple improvements to the way PowerCLI interacts with the Horizon View server.
It’s as simple as ‘Update-Module -Name VMware.PowerCLI’ to update your PowerCLI version!
For more information on changes made in VMware PowerCLI 10.1.1, including improvements, security enhancements, and deprecated features, see the VMware PowerCLI Change Log. For more information on specific product features, see the VMware PowerCLI 10.1.1 User’s Guide. For more information on specific cmdlets, see the VMware PowerCLI 10.1.1 Cmdlet Reference.
Pingback: New Release: VMware PowerCLI 10.1.1 – VMPRO.AT – all about virtualization
Pingback: New Horizon API calls in PowerCLI 10.1.1 – Retouw.nl
I just started encountering the timeout issue, I was hopeful that this would fix it, but unfortunately it did not.
If you have not already, can you please open a new support request regarding the issue? We definitely want to get it fixed.
I’m sure this would be a useful tool if there were a way to download it besides using Powerhell Gallery. None of my networks connect to the internet. I have Wyse box in my building that has internet access and Powershell is not loaded on Windows 7 Embedded. VMware needs to make tools like this available for companies that are a bit more security aware than your average Facebook user.
Pingback: VMware NSX-T Data Center 2.2 and PowerCLI 10.1.1 Released | Virtual Allan
tell us again why this isn’t a standalone download? not ALL systems are connected to the internet (especially Mgt systems) and its a PITA to port this over. WTF?
+1 for an offline installer – none of our systems are internet connected, forcing us to use PSGallery is a real pain.
Now, my update is failing…
PackageManagement\Install-Package : Authenticode issuer ‘System.Object[]’ of the new module ‘VMware.VimAutomation.HorizonView’ with version ‘7.5.0.8827468’ is
not matching with the authenticode issuer ‘System.Object[]’ of the previously-installed module ‘VMware.VimAutomation.HorizonView’ with version ‘7.1.0.7547311’.
If you still want to install or update, use -SkipPublisherCheck parameter.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:2089 char:20
+ … $sid = PackageManagement\Install-Package @PSBoundParameters
Update-Module does not have a -SkipPublisherCheck parameter, so ended up deleting the old modules and installing afresh.
Why all the angst and moaning about needing internet access? Regardless of the mechanism used, you still need some form of internet access to download the bits. So go to the machine that has internet access and use Save-Module to save it locally and then install the module wherever you need it.
Remembering that Save-Module exports are PoSh version specific. I exported on a Wndows 10 box, import fails on Windows 2012R2 server – both using default versions of PoSh.
Yeah, older versions of PowerShell don’t handle the folder structure properly. In a prior post, I included a script which can be used to remove those incompatible nested folders. The script is at the bottom of the following blog post: PowerCLI Offline Installation Walkthrough
I just upgraded to this as the command ‘Connect-HVServer’ has never worked for me.
I get the following every time:
Connect-HVServer : ExceptionType : VMware.Hv.EntityNotFound
ErrorMessage : Could not find user or group in AD
This was tracked as a bug in previous versions and the error persists in this latest version.
If you have not already, can you please open a new support request regarding the issue? We definitely want to get it fixed.
Anyone have an issue where it’s not upgrading the Mac OS version? I’m stuck on 10.1.0 still on my Mac.
How are you checking the version?
The most reliable way is: Get-Module -Name VMware.PowerCLI -ListAvailable | Sort-Object Version -Descending | Select-Object -First 1
More info: https://blogs.vmware.com/PowerCLI/2017/08/finding-powercli-version.html
I was using Get-PowerCLIVersion. Your command is showing the correct version installed. I’ll go ahead and stop using Get-PowerCLIVersion from now on. Thanks Kyle!