Home > Blogs > VMware PowerCLI Blog


New Release: PowerCLI 6.5.3

I’m excited to announce that it’s release day yet again! We have a great new update for you with PowerCLI 6.5.3! Just a few short months ago, two to be exact, the last version of PowerCLI was released. That release introduced a new parameter, some new content library functionality for ISOs, and even new support for certain features.

PowerCLI 6.5.3 comes packed with the following:

  • New module for NSX-T functionality
  • Addition of a ‘Create’ method for use with the ‘Get-*Service’ cmdlets
  • Several issues have been resolved

Let’s take a closer look at each of these.

New NSX-T Module

PowerCLI 6.5.3 introduces a brand-new module in order to manage VMware NSX-T environments. NSX-T was announced this year at VMworld US. In a nutshell, NSX-T is the newest iteration of VMware’s multi-hypervisor NSX platform. It is also the key to multi-cloud, and container infrastructures!

This module is being released as a low-level, API access only, module and will feature the following cmdlets:

  • Connect-NsxtServer
  • Disconnect-NsxtServer
  • Get-NsxtService

An example of connecting to an NSX-T server and listing the nodes included in the cluster:
NSX-T Module Example Usage

For more information on the NSX-T RESTful API, the API documentation can be viewed on the VMware Code API Explorer.

New Create Method Available

The other major update is around the addition of a ‘Create’ method to the Get-CisService and, newly released, Get-NsxtService cmdlets when used in conjunction with an object’s ‘Help’ property. This streamlines the creation of certain objects for a template-like experience. Those who have worked with specifications when using the ‘Get-View’ cmdlet will be quite familiar with how this ‘Create’ method will work and be interacted with. This method works against the following objects:

  • Parameter
  • Elements of a parameter (Limited to types: List, Set, Optional)
  • Key and value of parameters (Limited to types: Map)
  • Fields of a parameter (Limited to types: Structure)

Here’s an example on how the new ‘Create’ method can be used to create and apply settings to a specification in order to make a new VM while using the vSphere Automation SDK API:

Resolved Issues

This release of PowerCLI also contains some usage improvements to a handful of cmdlets.

  • New-TagAssignment: When connected to multiple vCenters and using string based inputs for the ‘Tag’ and ‘Entity’ parameters, the cmdlet has been updated to no longer throw an error of “The specified parameter ‘Tag’ expects a single value, but your name criteria ‘…’ corresponds to multiple values.”
  • Set-VMHostNetworkAdapter: When configuring an ESXi host’s virtual NIC to use an IPv6 address which is managed through a vCenter Server of version 6.5, the AutomaticIPv6 property has been corrected to no longer flip the switch to ‘True’.

Summary

We are continuing our commitment to getting the latest and greatest functionalities, performance improvements, and issue resolutions with this latest release of PowerCLI 6.5.3. After only 2 months, we have released a new module to manage NSX-T environments, added a new ‘Create’ method for use with the Get-CisService and Get-NsxtService cmdlets, and fixed a handful of issues with existing cmdlets.

Remember, updating your PowerCLI modules is now as easy as: Update-Module VMware.PowerCLI

For more information on changes made in VMware PowerCLI 6.5.3, including improvements, security enhancements, and deprecated features, see the VMware PowerCLI Change Log. For more information on specific product features, see the VMware PowerCLI 6.5.3 User’s Guide. For more information on specific cmdlets, see the VMware PowerCLI 6.5.3 Cmdlet Reference.

This entry was posted in General and tagged on by .
Kyle Ruddy

About Kyle Ruddy

Kyle Ruddy is a Senior Technical Marketing Engineer at VMware in the Cloud Platform Business Unit. Kyle currently focuses on vSphere with Operations Management as well as all things API, SDK, and CLI. Kyle can be found blogging on VMware blogs, http://blogs.vmware.com/vSphere and http://blogs.vmware.com/PowerCLI, and his personal blog, http://www.thatcouldbeaproblem.com. You can follow Kyle on twitter as @kmruddy.

17 thoughts on “New Release: PowerCLI 6.5.3

  1. Stephan

    Hi,

    I have a problem with one cmdlets: get-vsan-stat

    Get-VsanStat : 10/11/2017 6:54:33 AM Get-VsanStat Method not found:
    ‘VMware.VimAutomation.Cis.Core.Interop.V1.CisClient
    VMware.VimAutomation.Cis.Core.Interop.V1.CisClientManagerBase.GetClientByConnectionId(System.String)’.

    Reply
    1. Kyle RuddyKyle Ruddy Post author

      There’s been a new version of the PowerCLI 6.5.3 release that’s been updated on the PowerShell Gallery. Please run another Update-Module and let me know if you’re still experiencing that problem.

      Thanks.

      Reply
  2. Tom Otomanski

    Hi guys

    Getting the same error when trying to run the Get-Tag and Get-TagAssignment cmdlets.

    Regards
    Tom Otomanski

    Reply
    1. Kyle RuddyKyle Ruddy Post author

      There’s been a new version of the PowerCLI 6.5.3 release that’s been updated on the PowerShell Gallery. Please run another Update-Module and let me know if you’re still experiencing that problem.

      Thanks.

      Reply
  3. Pingback: Checking you are up to date with PowerCLI - Virtu-Al.Net

  4. Vijay Sai

    I hope I will find an answer here.
    I am new to power cli, and started using it from couple of months. I was very happy with PowerCLI 6.3 but I recently upgraded to PowerCLI 6.5 (Powershell 4.0 or 5.0) as our vcenter is upgraded to 6.5.
    The moment I upgraded, I started running into memory issues.

    Each end every command of powercli leaks memory and not freed for ever until I force garbage collect.
    Connect-VIserver, get-vm etc, all commands are leaking memory big time. Have you seen this kind of issue any time? is there anyway we can contain this leak.

    Here is my envivonment: Windows 2012 R2 server, .net 4.0, PowerShell 4.0/5.0, PowerCLI 6.5, Vcenter 6.5.

    Appreciate your help.

    Regards
    Vijay

    Reply
    1. Kyle RuddyKyle Ruddy Post author

      I’ve been following your VMTN thread regarding the issue: https://communities.vmware.com/thread/574071

      To this point, you’re the first to bring this up. I haven’t been able to reproduce it in multiple environments.

      I see from the thread that you’re running a script, if you can limit it down to one specific cmdlet that’s leaking memory I would urge you to open a Support Request. For more information on open an SR, see the following blog: http://blogs.vmware.com/PowerCLI/2017/08/powercli-support-breakdown.html

      Reply
      1. Vijay

        Thank you so much for replying. I will go through the support request channel and see what information I can provide. In my opinion, it is the combination of garbage collection happening slow and a memory leak.

        Also, I see that almost all commands like power-on VM, power-off VM, get-vm, get-vm <> etc are leaking. It is not just limited one command.

        Reply
        1. Vijay

          Also, do you think if you can revise your support Matrix? Because, in our environment, with PowerCLI 6.0 and Vcenter 6.5, it is working normally. We see issues with PowerCLI 6.5.x series.

          Reply
  5. NerdyBarry

    I believe in the past, there was guidance not to use the “Update-Module” cmdlet as it didn’t remove the old modules properly. Is that no longer the case?

    https://code.vmware.com/doc/preview?id=5731#/doc/GUID-36B57546-7378-4ED8-8780-43B6CE9914AF.html

    “If you use Update-Module, the existing version of the module is not removed. To update a module, you should first uninstall the existing version of the module and then install the new version.”

    Reply
    1. Kyle RuddyKyle Ruddy Post author

      I would consider that to be a personal preference.

      Personally, I don’t uninstall modules prior to an update. That allows the Update-Module command to complete a little faster since it only needs to download the new modules instead of downloading all of the modules.

      There’s no risk of issues when having PowerCLI 6.5.1 or newer versions all being on the same system, one of the huge benefits or switching over to modules!

      Reply
  6. Peter

    Only a small question…
    Do you know at what date VMRC is supported on Windows Server 2016?
    We want to offer our customers the VMware Remote Console via Remote Desktop Services (on Windows Server 2016), but we cant, because it does not work…
    VMware Support just said it is not supported, but didnt said when it will be!

    Maybe I find some help here?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*