VMware Cloud Community
swinster
Enthusiast
Enthusiast
Jump to solution

PowerCLI v6.5.4 with PowerShell Core v6 (rc2)

Hi All,

There are some major changes to PowerShell in v6 that I would like to leverage as for use these lead to incredible operating improvements. Whilst I can Install the PowerCLI module, when I attempt to run something like

Connect-VIserver

PowerCLI throws an exception

pastedImage_0.png#

Importing also doesn't work:

pastedImage_3.png

Anyone any thought around this?

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

Which PowerCLI version are you using?

The PowerCLi 6.5.x version will not work with PowerShell v6 I'm afraid.

See the compatibility matrix.

When you are trying with the PowerCLI Core Fling, that has some requirements as well, and will only work with PowerShell Core alpha 18.

This Fling will not work with the PowerShell Core beta versions.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

5 Replies
LucD
Leadership
Leadership
Jump to solution

Which PowerCLI version are you using?

The PowerCLi 6.5.x version will not work with PowerShell v6 I'm afraid.

See the compatibility matrix.

When you are trying with the PowerCLI Core Fling, that has some requirements as well, and will only work with PowerShell Core alpha 18.

This Fling will not work with the PowerShell Core beta versions.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

swinster
Enthusiast
Enthusiast
Jump to solution

@Lucd thanks, but at the same time, "OH NO!".

MS/OpenSource community have fixed some of the implementations of `Invoke-WebRequest` and `Invoke-RestMethod` that makes PS v6 highly desirable going forward (indeed we have seen a 200x speed improvement in file downloads). Given that PS v6 is about to be a fully released product, I can only hope that VMware will build support for this ASAP.

0 Kudos
LucD
Leadership
Leadership
Jump to solution

I'm not working for VMware, so any comment I make is purely personal :smileygrin:

When PowerShell Core went from Alpha to Beta, there was a breaking change in .Net Core.

Due to other priorities the Team that created the Fling didn't have the resources to catch up.

But I'm pretty sure that PowerCLI Core will be a thing in the future, and not a Fling anymore.

That might be after PowerShell RTM, but I'm pretty sure that it will come.

I don't think they can ignore the success of the Fling, and the added value of multi-platform support.

I for sure am waiting for that event :smileylaugh:


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
swinster
Enthusiast
Enthusiast
Jump to solution

@Lucd - I see your request a feature here - Minimise the time between PowerShell v6 RTM and | VMware PowerCLI

All you can do is vote Smiley Happy

Now I have to figure out how to write a script that can work out if PS v6 is installed, and use it for specific functions, and v5.1 for others.

0 Kudos
LucD
Leadership
Leadership
Jump to solution

And it is "planned" :smileygrin:


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos