Jump Host: PowerShell 7 and VCF PowerCLI — Build Guide
The jump host (prerequisites.md → Jump host)
needs PowerShell 7 and VCF PowerCLI for custom ESX images, day-2
scripts and most community tools. Windows ships only Windows PowerShell 5.1,
and VCF PowerCLI 9.x doesn’t work properly on 5.1, so this is the step that
most often goes wrong on a fresh jump host. It goes wrong even more often on a
jump host without internet access, where everything has to be carried in
by hand.
This page covers both cases: a jump host with internet access (§2) and one without (§3). It ends with how to check the result (§4), the problems seen on real jump hosts (§6), and how to clean up old PowerCLI for a clean start (§7).
Evidence level: Broadcom’s PowerCLI Installation Guide, the VCF PowerCLI download page, KB 409981 and KB 428547, the PowerShell Gallery page for
VCF.PowerCLI, and Microsoft Learn (Install PowerShell 7 on Windows, PowerShell Support Lifecycle, about_PSModulePath,Install-Module,Save-Module), all read verbatim on 2026-11-16. The offline-zip problems in §6 are field-verified 2026-11-13 on an air-gapped jump host. The manifest and module-path checks are lab-verified 2026-11-16 (PowerShell 7.6.10, VCF.PowerCLI 9.1.1.25718932, Windows 11).
1. What to install
| Component | Pick | Why |
|---|---|---|
| PowerShell | 7.6 (LTS), latest patch | Broadcom: “PowerShell 7.4 or later is officially supported and is our minimum recomended version for use”. Microsoft ended support for 7.4 and 7.5 on 10-Nov-2026; 7.6 LTS is supported until 14-Nov-2028 (support lifecycle). |
| PowerCLI | VCF.PowerCLI 9.1.1 (9.1.1.25718932) | “Make sure that you are installing VCF.PowerCLI and not VMware.PowerCLI.” VMware.PowerCLI “is compatible with vCenter Server 8.0 or earlier”; for vCenter 9 check the VCF PowerCLI matrix (KB 428547). |
| Windows PowerShell 5.1 | Leave it installed, don’t use it for PowerCLI | PowerShell 7 “installs to a new directory and runs side-by-side with Windows PowerShell 5.1”. VCF PowerCLI 9.x needs “PowerShell 7.0.13 +”; on 5.1 it fails at run time with “Could not load file or assembly ‘Newtonsoft.Json…’” (KB 409981). |
Two things to know before you start:
- The PowerShell Gallery lists
5.1as the minimum PowerShell version for VCF.PowerCLI, soInstall-Modulehappily installs it from Windows PowerShell 5.1. The install succeeds; the cmdlets fail later (KB 409981). Always install and run it frompwsh, notpowershell. - One PowerCLI version per jump host. VCF.PowerCLI pins every submodule to an exact version, and a second PowerCLI anywhere in the module path breaks the import (§6.1). Remove old VMware.PowerCLI 11.x/12.x/13.x copies before you install, unless something still needs them (§7).
2. With internet access
2.1 PowerShell 7
Microsoft’s options, from Install PowerShell 7 on Windows:
| Method | Use on a jump host? |
|---|---|
| MSI package | Yes. “Best choice for Windows Servers and enterprise deployment scenarios.” Installs to $Env:ProgramFiles\PowerShell\7. |
| WinGet | On Windows 11 / Server 2025 (Desktop Experience) only: “winget isn’t available on Windows Server 2022 or earlier versions.” From 7.6.0 it installs the MSIX by default; add --installer-type wix for the MSI. |
| MSIX / Microsoft Store | No. “Store-based installations are installed for a single user” and “don’t support PowerShell remoting.” |
| ZIP package | Only for a second, side-by-side version or Server Core. “Doesn’t check for prerequisites.” |
With WinGet (Windows 11 / Server 2025):
winget install --id Microsoft.PowerShell --source winget --installer-type wix
Or download PowerShell-7.6.x-win-x64.msi from the
PowerShell releases on GitHub
and install it silently:
$msiParams = @(
'/package', 'PowerShell-7.6.6-win-x64.msi', '/quiet',
'ADD_PATH=1', 'USE_MU=1', 'ENABLE_MU=1'
)
msiexec.exe @msiParams
USE_MU=1 / ENABLE_MU=1 (the defaults) let Microsoft Update, WSUS or
Configuration Manager patch PowerShell 7 later.
Plan ahead: “Beginning with the PowerShell 7.7.0 release, there is no MSI package available. WinGet only installs the MSIX package.” That affects the next upgrade, not 7.6.
2.2 VCF PowerCLI
Open PowerShell 7 (pwsh), not Windows PowerShell, and install from the
PowerShell Gallery:
Install-Module -Name VCF.PowerCLI -Scope CurrentUser
- Scope.
CurrentUserinstalls to$HOME\Documents\PowerShell\Modulesand needs no elevation.AllUsersinstalls to$Env:ProgramFiles\PowerShell\Modulesand needs an elevated session. On a shared jump host,AllUserssaves every engineer a separate install. Without-Scope, PowerShellGet 2.x in PowerShell 7 defaults toCurrentUser, orAllUsers“if you are running in an elevated session”. - Confirmation prompt. “Dependent upon your repository settings, you
might need to answer a prompt for the module installation to continue.”
Answer
Y. - Proxy. If the jump host reaches the internet through a proxy, add
-Proxy http://proxy.rainpole.io:3128(and-ProxyCredentialif needed). - Coming from VMware.PowerCLI 13.3 or earlier. Broadcom recommends a clean
install: uninstall VMware.PowerCLI first (§7). If you install over it anyway, you
may hit “The following commands are already available on this system”
(add
-AllowClobber) and certificate errors because “PowerCLI is now signed with a Broadcom certificate and not a VMware one” (add-SkipPublisherCheck).
Update later with Update-Module -Name VCF.PowerCLI.
2.3 First run
PowerCLI asks once about the Customer Experience Improvement Program, and refuses connections to servers whose certificate it doesn’t trust. Set both deliberately:
Set-PowerCLIConfiguration -Scope User -ParticipateInCeip $false
For certificates, the cleaner answer is to import the fleet CA on the jump
host (Windows certificate store, Trusted Root Certification Authorities)
and test Connect-VIServer with the default setting (Unset, the default, which
acts as Fail). InvalidCertificateAction on
PowerShell 7 knows only two values: “On PowerShell Core, only the Fail and
Ignore options are supported.” If you must use Ignore (a lab, or before the
certificate pass), keep it to the session:
Set-PowerCLIConfiguration -Scope Session -InvalidCertificateAction Ignore -Confirm:$false
3. Without internet access
Everything is fetched on a connected machine, checked, carried across, and installed on the jump host. Bring three things:
| What | Where from | Check |
|---|---|---|
PowerShell-7.6.x-win-x64.msi | PowerShell releases on GitHub (Assets of the release tag) | As your transfer policy requires |
VCF-PowerCLI-9.1.1-25718932.zip (168.33 MB) | developer.broadcom.com → VCF PowerCLI | MD5 on the download page: 11f33c4065214aebfb91dbd80b540bab |
| The fleet CA certificate | Your PKI team | Thumbprint against the CA |
Check the zip before you carry it:
(Get-FileHash .\VCF-PowerCLI-9.1.1-25718932.zip -Algorithm MD5).Hash
# 11F33C4065214AEBFB91DBD80B540BAB
Alternative to the zip: Save-Module. On a connected machine with
PowerShell 7, Save-Module “saves a module and its dependencies on the local
computer but doesn’t install the module”, in versioned folders, ready to be
“copied into the appropriate $env:PSModulePath location of the offline
machine”:
Save-Module -Name VCF.PowerCLI -RequiredVersion 9.1.1.25718932 -Path C:\Transfer\Modules -Repository PSGallery
Then carry C:\Transfer\Modules\* instead of the zip, and skip step 3.2.
3.1 Install PowerShell 7
On the jump host, as administrator:
msiexec.exe /package PowerShell-7.6.6-win-x64.msi /quiet ADD_PATH=1 USE_MU=0 ENABLE_MU=0
USE_MU=0 / ENABLE_MU=0 because the host can’t reach Microsoft Update; if
WSUS or Configuration Manager serves the isolated network, leave them at 1.
Open a new window and check pwsh -v.
3.2 Unblock the zip, then extract
Files downloaded with a browser carry a Mark of the Web, and everything extracted from a marked zip inherits it. Blocked module files fail to load.
Unblock the zip itself before you extract it. Then nothing extracted from it is blocked, and you don’t need admin rights to unblock files afterwards:
Unblock-File .\VCF-PowerCLI-9.1.1-25718932.zip
Broadcom’s guide unblocks after extracting instead
(Get-ChildItem * -Recurse | Unblock-File in the modules folder). That works
too, but in Program Files it needs an elevated session.
3.3 Extract to the PowerShell 7 module path
Broadcom: “Extract the downloaded .zip file to one of the listed folders”
of $env:PSModulePath. Pick the PowerShell 7 path:
| Scope | Path | Admin? |
|---|---|---|
| One user | $HOME\Documents\PowerShell\Modules | No |
| All users | $Env:ProgramFiles\PowerShell\Modules | Yes |
| Not this | $Env:ProgramFiles\WindowsPowerShell\Modules | — |
The last one is the Windows PowerShell 5.1 path. PowerShell 7 reads it too (see §6.2), so a copy there is found, but it’s also the path where old PowerCLI versions tend to live, and mixing is what breaks the import.
On a jump host where Documents is redirected or synced by OneDrive, check
the real location first: [Environment]::GetFolderPath('MyDocuments').
$dest = "$Env:ProgramFiles\PowerShell\Modules" # or "$HOME\Documents\PowerShell\Modules"
Expand-Archive .\VCF-PowerCLI-9.1.1-25718932.zip -DestinationPath $dest
Get-ChildItem $dest | Select-Object Name
The module folders (VCF.PowerCLI, VMware.VimAutomation.Sdk,
VMware.VimAutomation.Core, …) must land directly in that path, not in an
extra subfolder named after the zip. Move them up a level if they did.
3.4 Updating later
“You cannot update the PowerCLI module online if you have installed it by the offline method. In this case, perform an offline installation of the latest PowerCLI version.” Remove the old module folders first, so the new version doesn’t end up next to the old one (§6.1, how: §7).
4. Check the result
Run these in a clean session, pwsh -NoProfile, so nothing from a profile
interferes.
$PSVersionTable.PSVersion # 7.6.x
Get-Module -Name VCF.PowerCLI -ListAvailable | Select-Object Version, ModuleBase
Is every required submodule present at the exact version? VCF.PowerCLI
9.1.1 lists 36 submodules in its manifest, each with a RequiredVersion. This
shows only what’s missing; no output means complete:
$psd = (Get-Module -ListAvailable VCF.PowerCLI | Sort-Object Version -Descending | Select-Object -First 1).Path
(Import-PowerShellDataFile $psd).RequiredModules | ForEach-Object {
$req = $_; $all = Get-Module -ListAvailable $req.ModuleName -All
[pscustomobject]@{ Module = $req.ModuleName; Required = $req.RequiredVersion
Present = [bool]($all | Where-Object { $_.Version -eq $req.RequiredVersion })
Found = (($all.Version | Sort-Object -Unique) -join ', ') }
} | Where-Object { -not $_.Present } | Format-Table -AutoSize
Is anything still blocked? Should print 0:
$dest = "$Env:ProgramFiles\PowerShell\Modules" # where you extracted
(Get-ChildItem $dest -Recurse -File |
Where-Object { Get-Item $_.FullName -Stream Zone.Identifier -ErrorAction SilentlyContinue }).Count
Does it load, and from where?
Import-Module VCF.PowerCLI
Get-Module VCF.PowerCLI, VMware.VimAutomation.Sdk, VMware.VimAutomation.Core |
Select-Object Name, Version, ModuleBase
All versions should match the release (9.1.1.… for VCF.PowerCLI,
13.5.1.… for the VMware.* submodules) and come from the path you chose.
Can it connect?
Connect-VIServer -Server sfo-m01-vc01.rainpole.io
Get-VMHost | Select-Object Name, ConnectionState, Version
Disconnect-VIServer -Confirm:$false
5. Linux jump host
The same order applies on Linux:
- PowerShell 7 from Microsoft’s repository for your distribution
(Install PowerShell on Linux).
Without internet, carry the
.rpmor.deb: “Install package files (.rpm) are also available from https://packages.microsoft.com/”. - VCF PowerCLI with
Install-Module -Name VCF.PowerCLI, or offline with Broadcom’s same five steps (download the zip, list$env:PSModulePath, extract, unblock, check). - Module paths:
$HOME/.local/share/powershell/Modulesfor one user,/usr/local/share/powershell/Modulesfor all users.
6. Pitfalls
6.1 Several PowerCLI versions on one host
Field-verified 2026-11-13 on an air-gapped jump host that had PowerCLI
11.5 (in $PSHOME\Modules), 13.3 (unversioned folders in
C:\Program Files\WindowsPowerShell\Modules) and an incomplete offline
VCF.PowerCLI 9.1.1. The import failed with:
The required module 'VMware.VimAutomation.Sdk' with version '13.5.1.25718932' is not loaded.
and, after a partial fix:
Exception calling "OnImportModule" ... Value cannot be null. (Parameter 'type')
Why (manifests lab-verified 2026-11-16 on VCF.PowerCLI 9.1.1; module behaviour from about_PSModulePath):
- VCF.PowerCLI pins exact versions. All 36 entries in
RequiredModulescarry aRequiredVersion. One missing or shadowed submodule fails the whole import. - The submodules ask each other only for a minimum.
VMware.VimAutomation.Vds13.5.1 requiresVMware.VimAutomation.Storagewith only aModuleVersion. “By default, PowerShell loads the highest version number of a module when multiple versions are found”, so with several versions installed a session can end up with a mix. - One version of a module per session. Once a PowerCLI assembly is loaded it stays until the session ends, so an old version loaded by a profile or an earlier command blocks the new one.
- Unversioned folders (
…\Modules\VMware.VimAutomation.Sdk\with the files directly in it, typical after a manual copy) hold one version only, and a copy in an earlierPSModulePathfolder shadows a later one.
What to do:
- Keep one PowerCLI version on the jump host (how to remove the rest:
§7). Check every module path, not only the
one you installed to:
Get-Module -ListAvailable VMware.VimAutomation.Sdk, VMware.VimAutomation.Core -All | Select-Object Name, Version, ModuleBase - Run tools from a clean session:
pwsh -NoProfile. Don’t import PowerCLI from the profile on a shared jump host. - If two versions must stay, keep them in versioned folders
(
<Module>\<version>\) and narrow the search path for one session to the folder that holds one complete set:$env:PSModulePath = "$Env:ProgramFiles\PowerShell\Modules;$PSHOME\Modules"
Scripts shouldn’t work around a mixed host: a script that picks its own
PowerCLI set still leaves every other tool, and plain PowerCLI, failing.
The better guard is to detect it and point here. From v1.3.0,
VDSPortGroupManager
imports VMware.VimAutomation.Vds normally, stops when PowerCLI modules of
different versions are already loaded, and on a load failure lists what is
loaded with a link to this page. (v1.2.1 loaded a build from the module
manifests itself; that was dropped because it hid the problem.)
6.2 pwsh also reads the Windows PowerShell paths
PowerShell 7 builds $env:PSModulePath from its own user, system and
$PSHOME paths and then appends the machine-wide value, which includes the
Windows PowerShell paths (about_PSModulePath, PowerShell 7 startup). On
the lab workstation the result was:
C:\Users\<user>\Documents\PowerShell\Modules
C:\Program Files\PowerShell\Modules
C:\Program Files\PowerShell\7\Modules
C:\Program Files\WindowsPowerShell\Modules
C:\Windows\system32\WindowsPowerShell\v1.0\Modules
So a PowerCLI installed for Windows PowerShell years ago is still in play
under pwsh. Remove it (§7), or it takes
part in the version mix of
§6.1.
6.3 Blocked files after an offline install
Field-verified 2026-11-13: extracting the offline zip straight into
C:\Program Files\WindowsPowerShell\Modules left every .psd1, .psm1 and
DLL blocked, and Unblock-File there needed admin rights. Unblock the zip
before extracting (§3.2) and check with
the Zone.Identifier count in §4.
6.4 SsoAdmin on PowerShell 7
Lab-verified: Connect-SsoAdminServer from the VMware.vSphere.SsoAdmin
module fails on PowerShell 7.6 with VCF.PowerCLI 9.1.1 (a missing
System.ServiceModel type). Create or change SSO users and groups in the
vSphere Client instead.
7. Cleaning up old PowerCLI
Use this before a fresh install on a jump host that has had PowerCLI before, when §6.1 applies, before an offline update (§3.4), and when you come from VMware.PowerCLI 13.3 or earlier (§2.2).
Broadcom’s procedure is short. The prerequisite: “Close all PowerShell
sessions that are running VCF PowerCLI.” Then: “locate your VMware Cloud
Foundation PowerCLI modules and delete them”, using
Get-Module -ListAvailable VMware* | Select-Object -Property Name, Version, Path,
and “delete all modules that start with VMware” (TechDocs, Uninstall VCF
PowerCLI). Two things to add to that:
- That filter leaves out the
VCF.PowerCLImodule itself. Include it. VMware.vSphere.SsoAdminalso starts with VMware but isn’t part of PowerCLI. Leave it if you use it.
Evidence level: the TechDocs procedure and Microsoft’s
Uninstall-Modulepage, read verbatim on 2026-11-17. Route B withUninstall-Module, and the inventory and folder-list commands, are lab-verified 2026-11-17 (PowerShell 7.6.10, Windows 11): an old VMware.PowerCLI 13.3.0 set (83 modules, including 49VMware.Sdk.vSphere.*8.0.2099) next to VCF.PowerCLI 9.1.1, all from the PowerShell Gallery. Route A was not run end to end, and the lab had no unversioned folders.
7.1 Before you start
- Close every session that has PowerCLI loaded:
pwshandpowershellwindows, the ISE, VS Code terminals, and tools started from them. A loaded module keeps its DLLs open.Get-Process pwsh, powershellshows what is still running. - Rights. Your own folder (
Documents\PowerShell\Modules) needs no admin rights.Program Files\PowerShell\Modules,Program Files\WindowsPowerShell\Modulesand$PSHOME\Modulesneed an elevated session. - Delete PowerCLI only. The Windows PowerShell 5.1 folder
$PSHOME\Modulesholds modules that come with Windows. Remove the VMware ones from it and nothing else.
7.2 What is there, and how was it installed?
Run this in pwsh -NoProfile and in powershell -NoProfile. pwsh also
reads the Windows PowerShell paths
(§6.2), but a copy in
Documents\WindowsPowerShell\Modules only shows up in 5.1:
Get-Module -ListAvailable VMware.*, VCF.PowerCLI |
Sort-Object Name, Version | Select-Object Name, Version, ModuleBase
Which of these did PowerShellGet install (Install-Module)? Only those can
go with Uninstall-Module. Microsoft: “You can’t uninstall a module if
other modules depend on it or the module wasn’t installed with the
Install-Module cmdlet.” Copies from the offline zip, or from a manual
copy, aren’t in this list:
Get-InstalledModule | Where-Object { $_.Name -like 'VMware.*' -or $_.Name -eq 'VCF.PowerCLI' } |
ForEach-Object { Get-InstalledModule -Name $_.Name -AllVersions } |
Select-Object Name, Version, InstalledLocation
(Get-InstalledModule -Name VMware.* -AllVersions doesn’t work: with
-AllVersions it refuses a wildcard, “allowed only when you specify a
single name”.)
7.3 Route A: remove everything, then install once
Broadcom’s route. Use it when you don’t trust what is there, for example a mix of installs from different years.
- What PowerShellGet installed, from
pwsh(and again frompowershellfor 5.1 installs):
If a module refuses because another one depends on it, run the line again.Get-InstalledModule | Where-Object { ($_.Name -like 'VMware.*' -or $_.Name -eq 'VCF.PowerCLI') -and $_.Name -ne 'VMware.vSphere.SsoAdmin' } | ForEach-Object { Uninstall-Module -Name $_.Name -AllVersions -Force } - What is left is a manual or offline copy: delete the folders. This
lists the module folders (
<Modules>\VMware.Xxx). Check the list before you remove anything:
The$dirs = Get-Module -ListAvailable VMware.*, VCF.PowerCLI | Where-Object Name -ne 'VMware.vSphere.SsoAdmin' | ForEach-Object { if ((Split-Path $_.ModuleBase -Leaf) -eq "$($_.Version)") { Split-Path $_.ModuleBase -Parent } else { $_.ModuleBase } } | Sort-Object -Unique $dirs # check this list first $dirs | Remove-Item -Recurse -Forceifhandles versioned folders (VMware.Vim\9.1.0.…\) and unversioned ones (the files directly inVMware.Vim\). In both cases the module folder goes, never theModulesfolder above it. Microsoft notes that deleting by hand “may break any modules that depend on the deleted module”. Here that is the intent, because the whole set goes. - Check that
Get-Module -ListAvailable VMware.*, VCF.PowerCLIshows nothing (or only SsoAdmin), in both editions. - Install once, online (§2.2) or offline (§3), then run §4.
7.4 Route B: keep the current VCF.PowerCLI, remove the rest
Use it when the newest VCF.PowerCLI is complete (check with §4) and only older sets are in the way. This follows the dependencies of the newest VCF.PowerCLI and lists every PowerCLI module outside them:
$vcf = Get-Module -ListAvailable VCF.PowerCLI | Sort-Object Version -Descending | Select-Object -First 1
$keep = @{}; $todo = [System.Collections.Generic.Queue[object]]::new(); $todo.Enqueue($vcf)
while ($todo.Count) {
$m = $todo.Dequeue(); if ($keep["$($m.Name)|$($m.Version)"]) { continue }
$keep["$($m.Name)|$($m.Version)"] = $true
foreach ($r in $m.RequiredModules) {
$c = Get-Module -ListAvailable $r.Name | Sort-Object Version -Descending
$c = if ($r.RequiredVersion) { $c | Where-Object Version -eq $r.RequiredVersion } else { $c | Where-Object Version -ge $r.Version }
if ($c) { $todo.Enqueue(@($c)[0]) }
}
}
$old = Get-Module -ListAvailable VMware.*, VCF.PowerCLI |
Where-Object { $_.Name -ne 'VMware.vSphere.SsoAdmin' -and -not $keep["$($_.Name)|$($_.Version)"] }
$old | Select-Object Name, Version, ModuleBase # check this list first
VCF.PowerCLI 9.1.1 comes to 37 modules (itself plus 36). Then remove $old:
# installed with Install-Module
$old | ForEach-Object { Uninstall-Module -Name $_.Name -RequiredVersion $_.Version -Force }
# manual or offline copies in versioned folders: remove just that version folder
# $old | ForEach-Object { Remove-Item $_.ModuleBase -Recurse -Force }
In the lab, all 83 old modules went in one run of the Uninstall-Module line
and left no empty folders. Afterwards, Import-Module VCF.PowerCLI loaded
with one VMware.VimAutomation version (13.5.1). An old set in an
unversioned folder holds one version only and shares the folder name with
the current one. Remove it by hand after checking that the current version
lives elsewhere.
7.5 Afterwards
Run §4 in a clean pwsh -NoProfile. If a script
still reports “PowerCLI modules of different versions are already loaded”,
look for a profile or an open session that loads PowerCLI
(§6.1).
Sources
Read verbatim on 2026-11-16:
- Broadcom, PowerCLI Installation Guide:
PowerShell 7.4+ minimum, online and offline install, update, migrating from
VMware.PowerCLI (
-AllowClobber,-SkipPublisherCheck) - Broadcom, VCF PowerCLI downloads:
VCF-PowerCLI-9.1.1-25718932.zip, size and MD5 - KB 409981: VCF PowerCLI 9.x needs PowerShell 7.0.13+
- KB 428547: VCF PowerCLI, not VMware PowerCLI, for vCenter 9
- PowerShell Gallery, VCF.PowerCLI: current version 9.1.1.25718932 (2026-09-10), minimum PowerShell 5.1 as listed
- Microsoft Learn, Install PowerShell 7 on Windows, PowerShell Support Lifecycle, about_PSModulePath, Install-Module, Save-Module, Install PowerShell on Linux
- Broadcom, Set-PowerCLIConfiguration:
InvalidCertificateActionon PowerShell Core,ParticipateInCeip, scopes
Read verbatim on 2026-11-17 (§7):
- Broadcom TechDocs, Uninstall VCF PowerCLI
(VCF 9.1, last updated 16 November 2026): close all sessions, locate the
modules with
Get-Module -ListAvailable VMware*, delete the VMware folders - Microsoft Learn, Uninstall-Module:
only modules installed with
Install-Module, not while other modules depend on them; deleting by hand can break dependent modules