Month: April 2025

On April 23 2025, Broadcom deactivated the previous URLs to their public repositories from which the binaries for VCF, vCenter, ESX, and vSAN File Services can be downloaded. The new URLs now must contain customer-specific code. This particularly affects the automatic download of patches.

Broadcom announced two fundamental changes to the way VMware updates are available. First, they will now only be available at dl.broadcom.com, instead of depot.vmware.com, hostupdate.vmware.com, or vapp-updates.vmware.com as before.

Administrators must therefore ensure that the vSphere Lifecycle Manager (vLCM) or VMware Update Manager (VUM), for example, have access to the new address at broadcom.com and, if necessary, enable it in the firewall. Conversely, the previous URLs no longer have any function and can be blocked.

Second, each customer will receive a unique URL in the future – downloading from the public repositories via a general address will no longer be possible. Companies will receive the corresponding token from the Broadcom support portal.

The new URLs then follow this pattern:

https://dl.broadcom.com/<Your_Download_Token>/PROD/COMP/ESX_HOST/main/vmw-depot-index.xml

Read More

On April 10, 2025 an important change in the licensing model was introduced: the minimum number of cores ordered increased from 16 to 72, both for new licenses and for renewals.

Important: This only applies in Americas and APJ region, not in EMEA.

In EMEA, the new policy has been withdrawn and only the existing 16 core rule applies.

Rules:

• All core-based products are sold with a 16-core per CPU minimum.
• If you have an existing contract, you can add capacity in any quantity.
• For each core-based product you must place an new order or renew an existing order for at least 72 cores.

Example:

• Customer has 48 cores and wants a new contract, they need to buy 72 cores.
• Customer has already a contract with 16 cores, they need to buy 48 cores as capacity.