Temporarily allow vCenter VMware Update Manager (VUM) to enable the transition of heterogeneous hardware to vLCM Image Management. VMware Update Manager will remain enabled until the service or the vCenter appliance is restarted.
To complete your upgrade to VCF 9, you must transition your clusters from vLCM baseline management to vLCM image management.
The ESX upgrade portion of VMware Cloud Foundation 9.x upgrade process has a prerequisite of vLCM image-managed clusters.
However, vLCM images for heterogeneous hardware-based clusters are only supported in ESX 9, which means the transition must occur after the ESX 9 upgrade. In order to upgrade heterogeneous-hardware clusters to ESX 9 using VUM, a special process is required to temporarily allow the service.
The vCenter Update Manager service can be unrestricted via a Broadcom-provided PowerShell script or vCenter APIs, but only if one or more heterogeneous-hardware clusters are present.
Once vCenter Update Manager has been unrestricted, please upgrade the heterogeneous cluster to ESX 9 using vCenter Update Manager and then transition the cluster to vLCM images.
This script can work in VCF Mode (through SDDC Manager) and vCenter mode (no SDDC Manager). The former detects and connects all vCenters registered to SDDC manager, while the latter connects to individual vCenters.
- This process is only supported for true heterogeneous clusters.
- The service becomes restricted after a service restart or appliance reboot.
- Following VUM-based ESX 9 upgrades, users should prioritize transitioning the cluster(s) from vLCM baselines to vLCM images.
- VCF.PowerCLI 9.0+
- PowerShell 7.2+
- Compatible OS: MacOS / Linux / Windows
Note: Before installing VCF.PowerCLI uninstall VMware.PowerCLI to avoid conflicts between the two modules.
- (for VCF Mode) SDDC Manager: ADMIN user
- (for vCenter Mode) vCenter : ADMIN access
- HTTPS access to SDDC Manager
- HTTPS access to vCenter
- SDDC Manager 9.0+ (for VCF mode)
- vCenter 9.0+ (for the heterogeneous clusters)
Link to latest release.
Log any issues here:
https://github.com/vmware/powershell-script-for-vmware-cloud-foundation-vum-unrestrict/issues
- Run
VumUnrestrict.ps1. If you have a VCF deployment with SDDC Manager, enter "Y" to the promptIs this a VCF Deployment?otherwise enter "N". - When prompted, enter the credentials for SDDC Manager or vCenter, depending on the mode.
-Run VumUnrestrict.ps1 -Mode VCF for VCF mode (with SDDC Manager) or VumUnrestrict.ps1 -Mode vCenter (for non-VCF mode without SDDC Manager)
- When prompted, enter the credentials for SDDC Manager or vCenter, depending on the mode.
The script will return one of four statuses:
| Status | Meaning | Action Required / Next Steps |
|---|---|---|
| N/A | vCenter version not supported | Upgrade to vCenter 9.0 or later |
| Unrestricted | Success - VUM Services Unrestricted | Ready to proceed to ESX 9.0 upgrade |
| Restricted | No heterogeneous hardware-clusters located | Any VUM based clusters can be transitioned to vLCM images |
| Failed | Underlying vCenter Task failed, was blocked, or entered an unknown state | Please open a support case |
PS> .\VumUnrestrict.ps1
Is this a VCF Deployment?
[Y] Yes [N] No [?] Help (default is "Y"):
[INFO] Please enter your connection details at the prompt.
Enter your SDDC Manager FQDN: vcf01.example.com
Enter your SDDC Manager SSO username: administrator@vsphere.local
Enter your SDDC Manager SSO password: ********
[INFO] Successfully connected to SDDC Manager "vcf01.example.com" as "administrator@vsphere.local".
[INFO] Successfully connected to vCenter "vcenter01.example.com".
[WARNING] vCenter "vcenter02.example.com" detected running version 8.0. vCenter 9.0 or later required.
[INFO] Disconnecting from incompatible vCenter "vcenter02.example.com".
[INFO] Successfully disconnected from vCenter "vcenter02.example.com".
[INFO] Looking for heterogeneous-hardware clusters in the connected vCenter(s)...
[INFO] vCenter "vcenter01.example.com" VUM unrestrict task completed in 29 seconds.
Summary:
vCenter VUM Services Message
------- ------------ -------
vcenter01.example.com Unrestricted Heterogeneous-hardware clusters(s) located.
vcenter02.example.com N/A vCenter release unsupported (version 8.0).
[INFO] Successfully disconnected from SDDC Manager "vcenter01.example.com".
[INFO] Successfully disconnected from vCenter "vcenter01.example.com".PS> .\VumUnrestrict.ps1
Is this a VCF Deployment?
[Y] Yes [N] No [?] Help (default is "Y"): N
[INFO] Please enter your vCenter connection details at the prompt.
Enter your vCenter FQDN: vcenter01.example.com
Enter your vCenter SSO username: administrator@vsphere.local
Enter your vCenter SSO password: ********
[INFO] Successfully connected to vCenter "vcenter01.example.com" as "administrator@vsphere.local".
[INFO] Looking for heterogeneous-hardware clusters in the connected vCenter(s)...
[INFO] vCenter "vcenter01.example.com" VUM unrestrict task completed in 25 seconds.
Summary:
vCenter VUM Services Message
------- ------------ -------
vcenter01.example.com Unrestricted Heterogeneous-hardware clusters(s) located.
[INFO] Successfully disconnected from vCenter "vcenter01.example.com".PS> .\VumUnrestrict.ps1
Is this a VCF Deployment?
[Y] Yes [N] No [?] Help (default is "Y"): N
[INFO] Please enter your vCenter connection details at the prompt.
Enter your vCenter FQDN: vcenter02.example.com
Enter your vCenter SSO username: administrator@vsphere.local
Enter your vCenter SSO password: ********
[INFO] Disconnecting from incompatible vCenter "vcenter02.example.com".
[ERROR] vCenter version 8.0 detected. Version 9.0 or later is required.- vCenter: Administrative rights
- HTTPS access to vCenter
- vCenter 9.0+ (for the heterogeneous clusters)
- Login to vCenter as an administrative user.
- Click on the Menu icon.
- Click on Developer Center.
- Click on API explorer.
- Select API endpoint "esx".
- Select the correct vCenter 9.0 or later endpoint.
- Expand "settings/inventory".
- Execute
/api/esx/settings/inventory?action=update-vum-capability&vmw-task=true. - You receive a task ID back, copy this down (for example
"52b3cef6-00df-033a-9778-f243a1e96e97:com.vmware.esx.settings.inventory"). If you do not get a task ID, please verify the vCenter in question was indeed running vCenter 9.0 or later. - Change your API endpoint to "cis".
- Expand "tasks".
- Expand
/api/cis/tasks/{tasks}/{task}. - Enter your task ID from step 9 into the task field and click "Execute".
- Look at
vum_operations_enabledunder results. If this key is equal totrue, VUM has been unrestricted. If the value isfalse, please examine the payload for answers as to why not.
- For product issues, please open a standard Broadcom support case.
- For bugs or enhancement requests with this script, please open a github issue.