Home > Blogs > VMware PowerCLI Blog > Monthly Archives: June 2016

Monthly Archives: June 2016

Which Version of PowerCLI is Right For Me?

“I have PowerCLI 5.5 installed because I manage a vSphere 5.5 environment. I’ll update to PowerCLI 6.0 when I upgrade my vSphere environment to 6.0.”

Sound familiar? This is one of the most common things we hear during VMUGs, customer meetings, and around the community in general. This also happens to be a HUGE misconception. The current version is PowerCLI 6.3 Release 1 and it is compatible with all the supported vSphere versions!

Don’t take my word for it, check out the compatibility matrix:
PowerCLI Compatibility

As displayed in the compatibility matrix above, significant effort has been made to ensure backward compatibility while still being able to offer all of the latest and greatest updates and feature enhancements.

At this point you’re probably wondering what version of PowerCLI you’re using? Open up your PowerCLI window and have a look at the “Get-PowerCLIVersion” cmdlet:
Get-PowerCLIVersion

Conclusion

PowerCLI is extremely backward compatible and we highly recommend upgrading to the latest version: PowerCLI 6.3 Release 1.

Take advantage of the following benefits:

  • Get-VM cmdlet optimizations
    Saying Get-VM is faster is just an understatement, some of the numbers we’ve received from the community are amazing!
  • Get-View cmdlet improvements
    Get-View now allows for tab completion of the -ViewType parameter
  • Added Content Library functionality
    The new Get-ContentLibraryItem cmdlet retrieves Content Library items as well as the ability to specify a Content Library item while using the New-VM cmdlet.
  • Get-ESXCLI improvements
    Major upgrade to the Get-ESXCLI cmdlet to now allow the passing of arguments by name instead of position simply by adding the -V2 parameter
  • Added PowerShell v5 and Windows 10 support
  • Added support for the following VMware products: vCloud Director 8.0 and vRealize Operations Manager 6.2

A couple notable resolved issues:

  • Get-VM
    If you try to run Get-VM without specifying any parameters, you might receive an error message of type Value cannot be null.
  • Export-EsxImageProfile
    If you try to export an image profile, you receive an error message of type Cannot instantiate ‘certified’ policy: VibSign module missing.
  • New-DeployRule
    If you try to create a new deploy rule by passing absolute values of host profle, cluster, datacenter, or folder instead of passing the objects, you receive an error message of type Cannot process argument transformation on parameter ‘Item’. Unsupported version URI urn:rbd1/3.0.

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

Upgrade by heading over to the vSphere PowerCLI page and downloading it today!

Welcome a new face to the team

 

3TSeV8RqYou are about to see new and exciting blog posts arrive from a fresh face on the team.  Please do join me in welcoming the new Technical Marketing expert on all things PowerCLI – Kyle Ruddy.

Kyle works as part of our Technical Marketing team, being responsible for vSphere Operations Management and will also cover APIs / SDKs and CLIs.

Kyle has been a big fan of PowerCLI, and automation in general, having technically reviewed PowerCLI books, presented PowerCLI based VMUG sessions, and been a strong community contributor. Kyle’s focus will be to continue evangelizing PowerCLI and its use to help VMware customers increase their productivity and consistency and to bring you the latest and greatest in news and new ways to use PowerCLI.

During his spare time, Kyle enjoys golfing, SCUBA diving, and most motorsports activities.

 

You can find Kyle’s personal blog at http://thatcouldbeaproblem.com and can contact him on twitter via @kmruddy