Powershell script run to long after migration from Powercli 6.5.4 to Powercli 11

[Touffi]

Hi Community

My script run to long after changing PowerCLI 6.5.4 to Powercli 11.

I applied some recommandations found in internet but I'm not really satisfied.

My system is Windows 2016, 4 CPU's , 8GB

I changed scheduled Task Priority from 7 to 4

I control the PowerCLIConfiguration:

Scope    ProxyPolicy     DefaultVIServerMode InvalidCertificateAction  DisplayDeprecationWarnings WebOperationTimeout

                                                                                                  Seconds           

-----    -----------     ------------------- ------------------------  -------------------------- -------------------

Session  NoProxy         Multiple            Ignore                    True                       300               

User     NoProxy         Multiple            Ignore                                                                 

AllUsers NoProxy

An exemple of running time:

	Priority 7	Priority 4
PowerCLI_654	7mn	7mn
Powercli_11	36mn	17mn

With PowerCLI_11 raise now in Windows an Event 10016

Can someone help to correct this issue?

Thanks for suggestions.

Regards

Denis

[Touffi]

No, is not gone...

[LucD]

It might be time to open a SR for this I think.

And yes, PowerCLI is supported, as long at it is not an obvious scripting error.

When GSS makes the remark that you need to have a Developer SDK Support contract, you can refer to PowerCLI Support Breakdown

[Touffi]

I have allready tryed  with no chance.

Yesterday I start an another one SR with our Cloud Contract.

We will see!

[Touffi]

Hi Luc,

Greetings!

It toke a long time to get a support from VMware...

Now I'm in contact with the support for my case.

From Support: "We appreciate your patience, kindly bear with us. Our concerned engineering team and SDK team is working on the service request."

As soon I'll get the solution, I'll write it down here

Best Regards

Denis

[Touffi]

Hi Luc,

I'm always on this VMware Support Case, I was pushed from SDK team to Vcenter Team...
We will turn in a circle!
The vCenters where we have our problem are behind more firewall.
I Install on one of them PowerCLI and did the test between these vCenters and our local connection.
Connection is 3s or 2s.

We make a demande to our Firewall Team to open the Port 7444. Port was today opened.
Here the result of the today connection: 3s

**********************
Windows PowerShell Transcript Start
Start time: 20190222084640
**********************
Windows PowerShell Transcript End
End time: 20190222084643
**********************

I ask VMware for a exactly Port Matrix for PowerCLI 10x and greater, they always say port 443 and 902.

Our test show that port 7444 is a requirement when working with firewall!
Have you more information?

Regards
Denis

[LucD]

Port 7444 is used for the SSO service over HTTPS.

See Port Requirements (from vCloud 6.0)

Are you using vCloud?

[LucD · Accepted solution]

I just discovered that the use of port 7444 is not limited to vCloud.

It seems that vCenter 6.0.x and higher, also uses this port.

See for example KB2131310 and KB2106283

[Touffi]

I got yet the answer below from VMware Support:

-----------------------------------------------------------------------------------------------------------------------------------------------------

I have confirmed from the SDK team and as per them 7444 port is used by the lookupservice/sdk  and the main port
which is required are 443 and 80.
Please also go through this blog:

https://blogs.vmware.com/PowerCLI/2014/09/poweractions.html

There is no such port matrix doc available.

-----------------------------------------------------------------------------------------------------------------------------------------------------

[LucD]

That is also what the 2nd KB I mentioned earlier says

The PowerActions Fling in fact is quite old and doesn't work anymore with the latest vSphere and PowerCLI versions.
No clue why they send you to that 5-year old blog post.

[Touffi]

OK Thanks Luc

I mark this event as resolved

Best Regards

Denis

[Touffi]

Hi Luc,

Oppening the port 7444 was not enough.

But installing the new PowerCLI version 12.2 resolved the problem.

Something change in this new version...

Regards

Denis

[LucD]

Thanks for sharing that.

Could be something related to SSL and/or the Lookup Service, and how it is handled in the latest PowerCLI version.

A network trace might shed some light :smileygrin: