Afaik it is not mentioned explicitly in the PowerCLI documentation.
It was mentioned in some older PowerCLI threads on here, but since the VMTN migration to this new (Broadcom) platform, it is hard, if not impossible, to find old threads.
------------------------------
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
------------------------------
Original Message:
Sent: Oct 21, 2024 04:51 AM
From: Atsushi Kondo
Subject: "Import-Module VMware.PowerCLI" Takes 5 Minutes & Taking to Akamai
LucD - san
We asked the question (*1) and found that the following workarounds are effective:
- UNcheck "Check for publisher's certificate revocation"
- UNcheck "Check for server certificate revocation"
We would like to know if this workaround is described in VMware documentation. If so, can you tell me the VMware document where it is described?
(*1)
https://community.broadcom.com/vmware-cloud-foundation/question/when-we-run-the-powercli-connect-viserver-command-it-takes-about-1-minute-and-40-seconds-to-execute
Original Message:
Sent: Jan 27, 2020 05:09 PM
From: LucD
Subject: "Import-Module VMware.PowerCLI" Takes 5 Minutes & Taking to Akamai
PowerShell doesn't look automatically for module updates unless you have the Update-Module somewhere in a profile.
This might be a timeout while checking the certificates that secure the PowerCLI modules.
See for a similar (older) issue Re: PowerCLI very slow to load on a Windows 2012R2 Server