Converge vSphere 8 to VMware vSphere Foundation 9.1.x

.

ATTENTION!!

This is a document that was created from a Home Lab.

My Home Lab:

vSphere 8u3i

One vCenter

Two ESXi hosts (Nested)

One NFS datastore (TrueNAS)

Official Documentation

Source Converge a vCenter Instance and ESX Hosts to vSphere Foundation

Verify upgrade path from Product Interoperability Matrix

Requirements

Prepare a temporary IP for vCenter

Prepare five FQDNs and register on DNS (with reverse) for:

1 VCF Operation

3 VCF Management Services

1 VCF License server

And ten IP addresses (minimum) for Management Services

.

UPGRADE STEP

• vCenter Upgrade
• Install VCF Installer
◦ Install VCF Operations
◦ Install VCF Management Services
• Upgrade ESXi
◦ Upgrade ESXi Hosts
◦ Upgrade vDS
◦ Upgrade VMware Tools
◦ Upgrade Virtual HW

.

vCenter Upgrade

You must deploy the new vCenter in the vSphere Cluster that you need to upgrade at VVF. In my test, I deployed the new vCenter in another vSphere infrastructure, and the VCF Installer reports an error.

The vCenter upgrade process is a classic vCenter upgrade.

.

Download vCenter 9.1 from the Broadcom Support Portal

Dedicate a temp IP address and FQDN name (need to register in DNS) for deployment

Mount the downloaded ISO on a bridge PC or Virtual Machine

Start the UI installer

 .

Select upgrade

 .

Start the deployment

.

Deploy the VCF Installer appliance.

I covered this installation in another Post; read this post:

Start a New vSphere Foundation Deployment by Using the VCF Installer Deployment Wizard – BIOLNX

Deploy VCF Operations

Log in to VCF Installer

Download bundles for the VCF Installer appliance (Read this post: Start a New vSphere Foundation Deployment by Using the VCF Installer Deployment Wizard – BIOLNX)

Use VCF Installer to deploy your vSphere Foundation platform.

.

.

Select I have an existing vCenter

Select the network infrastructure for the Management Services and Operations component in my Home Lab. I choose the network where the VM is deployed (otherwise, create a dedicated network; check the firewall configuration in the official documentation)

.

.

Dedicate IP address and FQDN (with reverse)

VVFOPUP.pollaio.lan 192.168.80.110

VVFMNGSUP01.pollaio.lan 192.168.80.111

VVFMNGSUP02.pollaio.lan 192.168.80.112

VVFMNGSUP03.pollaio.lan 192.168.80.113

VVFLICUP01 192.168.80.114

.

.

We enter the FQDN names of the objects; if entered correctly in the DNS (with the reverse), they have a green tick

.

In my case, if the new vCenter is not deployed in the cluster that we want upgrade, we see an error.

.

After vCenter migrating to the vSphere cluster object for the upgrade

.

Save the Password!!!!

Start the VCF Operation appliance installation

.

At the end of VCF operation Installation, we can log in to the VCF Operations UI

Now we can configure the License (See this post)

Register VCF Operations and Your License Server in Connected Mode – BIOLNX

.

Upgrade ESXi

Log in to vCenter and select the Lifecycle Manager

After some time, under Software Depot, the new ESXi version appears

Now we create a new Image; go to Image Library and select Create Image

 

Validate and save

.

Go to Inventory

Select the cluster and after updates

.

Now the upgrade will start if the cluster is correctly configured

Upgrade Virtual Distributed Switch

.

.

Next step

Upgrade VMware Tools

Upgrade Virtual Hardware

.

Converge vSphere 8 to VMware vSphere Foundation 9.1.x

Register VCF Operations and Your License Server in Connected Mode

In my previous post, I walked through the process of deploying VMware vSphere Foundation (VVF) in my Home Lab using the VCF Installer, from infrastructure preparation to the initial bring-up of the environment. [If you missed it, you can find it here:

Start a New vSphere Foundation Deployment by Using the VCF Installer Deployment Wizard – BIOLNX

With the deployment up and running, the next step is licensing the environment. In this post, I cover how I activated the VVF licenses, the options available, and a few gotchas I ran into along the way — useful if you’re following the same path in your own lab and want to move from a freshly deployed environment to a fully licensed one.

 

Log in to VCF Operations

From the navigation bar at the top, click Manage and in the left navigation pane, click Licensing -> Licenses & Registration

 

In the Register & License VCF Operations pane, click Continue

 

 

The Register and License VCF Operations workflow appears.
The first step of the procedure is complete because a license server is automatically deployed during a new VCF Operations 9.1 deployment and an upgrade to VCF Operations 9.1.

In the Select Connection Mode card, select
Start, and click Continue.

 

 

Navigate to the Registration section.

Get an activation code for your registration. In the Get Activation Code from VCF Business Services console card, click Start

 


The VCF Business Services console opens in a new tab.

 

 

Log in to the VCF Business Services console by using your Broadcom Support Portal credentials.

Select the Site ID to which you want to register this VCF Operations instance, and click
Next. If you have only one site, it is selected by default.

In the VCF Business Services console, оn the Register & License VCF Operations page, navigate to the Registration part of the registration workflow.

In the Name VCF Operations pane, click Start, enter a unique display name for your
VCF Operations instance, and click Save

The FQDN is only saved if you do not enter another display name. If you change the FQDN with another display name, the connectivity between
VCF Operations
and the VCF Business Services console is not impacted. You can change the display name at any time after the registration.

In the Generate Activation Code card, click Start

 

.

A dialog box with the activation code appears.

 

 

Click Copy (and save the info into a notepad file) Verify that you copied the code, and click Finish

Navigate to the VCF Operations instance, and upload the activation code. In VCF Operations, in the Enter Activation Code card, click Start

 


A dialogue box appears.

In the text field, paste the activation code, and click Activate

 

 

 

In the Add Licenses from VCF Business Services console card, click Start

 

 

The VCF Business Services console opens in a new tab.

In the VCF Business Services console, add licenses to your license servers.

 

To complete the registration process, you must first add licenses to each license server.

In the Add Licenses section of the registration workflow, in the card for the respective license server, click Start
On the Allocate Licenses page, enter a display name for the license server.

If you want to split the default license or change a license’s capacity before assigning it, click the vertical ellipsis next to the license. To split the default license, select it from the list and click Create. Enter a name and license capacity for the split license. To change the capacity of a split license, enter the capacity for the license in the New Capacity column. Click Save.

Select licenses from the table to add to the license server, and click Confirm.
To license your environment, you must add at least one primary license to the license servers. You can add licenses during the registration process, or at any time after that.

 

   

 

Download the license file in the VCF Operations instance.

Navigate to the Licenses page.

In the Add Licenses to License Servers section, in the Download card, click
Download.

 

 

On the Register and License VCF Operations page, click Finish

 

 

 

Now we can assign the license to vCenter. Select Assign Primary License after checking the vCenter instance to assign the license.

 

 

 

Select the license to assign and click Assign

 

 

 

Now the assigned license Core Count and Host Count are Green (if you have sufficient licenses to assign)

 

 

 

From vCenter, by accessing from the vSphere client, we can show the license status under Administration -> License -> Version 9+ License

 

 

 

.

Register VCF Operations and Your License Server in Connected Mode

Horizon 2603 is here!

A new version of Omnissa Horizon has just been released, and 2603 is not just another update — it’s an ESB (Extended Service Branch) release and marks an important transition point for many environments.

🔗 Release Notes:
https://docs.omnissa.com/bundle/horizon8-rnV2603/page/Horizon8-ReleaseNotes.html


First things first: end of support for vSphere 7

Let’s start with something critical:

Horizon 2603 ESB no longer supports vSphere 7.x

  • Horizon 2512 was the last release supporting vSphere 7
  • Starting from 2603, vSphere 8 is the required platform

This means one thing:
If you’re planning to move to this ESB, your vSphere upgrade is no longer optional — it’s mandatory

This is a key architectural checkpoint, especially for environments that have been delaying the jump to vSphere 8. (vSphere 7 is end of support)


Event Database + Integrated Authentication (finally!)

Now, let’s talk about one of my favorite new features.

Horizon 2603 introduces the ability to configure the Event Database on Microsoft SQL Server using Active Directory identities (Domain User with Integrated Authentication).

No more SQL authentication.

Why this matters:

  • Eliminates stored SQL credentials
  • Aligns with enterprise security best practices
  • Simplifies credential lifecycle management
  • Improves compliance and auditability

From a design perspective, this is a very welcome step toward a more secure-by-default architecture.

 Final thoughts

This release is not just about new features — it’s about setting a new baseline:

  • ✔️ ESB = long-term stability
  • ✔️ vSphere 8 as the standard
  • ✔️ Stronger security integration

If you were waiting for the “right moment” to modernize your Horizon platform… this is probably it.


 In the next posts, I’ll dive deeper into the other new features and changes introduced in Horizon 2603 — stay tuned 👀


Need help testing or upgrading?

If you’re planning to:

  • Test Horizon 2603
  • Upgrade your existing environment
  • Move from vSphere 7 to vSphere 8 or 9

Feel free to reach out — happy to help with assessments, design, and upgrade strategies.


Have you already started testing Horizon 2603?
Or are you still planning your vSphere 8 migration?

Let’s discuss 

Horizon 2603 is here!

vSAN ESA and vSAN File Service

Requirements

Enable vSAN File Service

Limitations and Considerations

Limitations and Considerations of vSAN File Service

Networking Considerations for vSAN File Service

After deploying and configuring the vSAN ESA we are ready to enable and configure the vSAN file services.

Enable File Service

A screenshot of a computer

Description automatically generated

A screenshot of a computer service

Description automatically generated

After Enabling the service we will see on the vCenter a new Resource Pool to allocate the File Service Node VM. (One for Each host ESXi)

A screenshot of a computer

Description automatically generated

Configure vSAN File service

Go to vSAN, Services and under File Service click CONFIGURE DOMAIN

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

We need to configure the Directory Service to enable SMB share and NFS Kerberos Authentication.

The user identity for configuring the directory service must have the correct permission to do a join AD.

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

After completing the domain configuration we see the computer accounts in the OU select.

A screenshot of a computer

Description automatically generated

Create File Share

Now we can create the file share

A screenshot of a computer

Description automatically generated

Will can create a NFS share with AUTH_SYS or Kerberos Authentication

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

Will can create an SMB share

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

Configure ACL permission

SMB SHARE can configure ACL for access use the FSM MMC from a windows OS.

A screenshot of a computer

Description automatically generated

A black background with white text

Description automatically generated

A screenshot of a computer

Description automatically generated

From best practices Microsoft it suggest to user Everyone on Share permission

A screenshot of a computer screen

Description automatically generated

And set the permission on File Level (Security TAB)

A screenshot of a computer screen

Description automatically generated

Mount Share

On every share proprieties, we can find the path to use for mounting the share (The SMB Export Path)

A screenshot of a computer

Description automatically generated

Share quota

The quota control if a specified Share exceed the max space add for it.

A screenshot of a computer

Description automatically generated

We can control the state of all share quotas from the vSphere console.

A screenshot of a computer

Description automatically generated

A screenshot of a computer

Description automatically generated

SMB Export Path -> The path to use for mounting the share

MMC Command -> The command to use for configuring the ACL

A screenshot of a computer

Description automatically generated

vSAN ESA and vSAN File Service

App Volumes 2406

As anticipated in my previous posts, version 2406 of Omnissa’s EUC products (the company that took over VMware’s EUC products) has been released. New versions of the following are present:

  • App Volumes
  • Horizon
  • Unified Access Gateway
  • Dynamic Environment Manager

In the next posts I present some of the most interesting new features that are present in these new releases.

Let’s start with App Volumes and talk about:

  • Volumes App for Persistent Desktop
  • Extending the App Volumes solution to other platforms
  • Assign different versions of the same application to a user

Volumes App for Persistent Desktop

  • The solution until the version before 2406 was only available for non-persistent desktops (Instant Clone)
  • From the 2406 it is also possible to use it with persistent desktops

The main difference is present in the installation of the agent where it is asked on which type of desktop we are installing the App Volumes agent

A screenshot of a computer

Description automatically generated

In its nature of profile management, the use of App Volumes on a persistent machine is only possible with App Stacks and not with Writable Volumes

Extending the App Volumes solution to other platforms

The ability to use App Volumes with VDI is not only of Horizon infrastructure, from version 2406 it is possible to use with Windows 365 and with Amazon WorkSpaces

A group of logos on a white background

Description automatically generated

Assign different versions of the same application to a user

Leveraging Apps on Demand, end users can now select from multiple packages of an application at launch, providing flexibility to try out new versions or launch specific ones

Other assignment options: “Marker,” and “Package,”, now we are the “Multiple,” option enhancing application management and deployment flexibility.

App Volumes 2406

VMware vSphere Foundation for VDI (VVF for VDI)

A blue and white logo

Description automatically generated

A black text on a white background

Description automatically generated

The exit of EUC services from Broadcom (after the acquisition of VMware by the US giant) has brought a situation of uncertainty for all those who have been appreciating for years the features of the VDI/Applications published with Horizon and all the products of the EUC ecosystem that were from VMware.

The birth of Omnissa (effective from the beginning of July) bodes well for the future (more information in this post of mine from a few weeks ago).

Of the many synergies that were natural when vSphere and Horizon were children of the same mother, the first uncertainty was the licensing issue.

VMware gave the possibility, once a specific Horizon license was purchased, to have the vSphere virtualization infrastructure licenses, practically a solution ready to be only implemented. (I remind you that Horizon also goes on other Hypervisors… obviously exploits 10% of the potential… on this issue. I expect news from Omnissa since vSphere and Horizon are no longer brothers). The only limitation of the vSphere license included in Horizon was the need to run on the vSphere platform, licensed with Horizon, only VDI environments and the servers necessary for operation (Connection Server ,,, App Volumes Manager etc ..)

Now that vSphere and Horizon no longer have the same mother, what happens to these licenses? Will I still be able to buy a bundle with Horizon and vSphere together?

This link explains that the best of the matter:

Setting the record straight: EUC to continue to offer Horizon with vSphere and vSAN (omnissa.com)

Where it is indicated that there will be a collaboration between Omnissa and Broadcom to allow the presence of a bundle with Horizon and vSphere.

A green and white logo

Description automatically generated

So it is still possible to purchase one of the following licenses:

  • Horizon Enterprise term
  • Horizon Universal,
  • Horizon Enterprise Plus
  • Horizon Standard Plus
  • Horizon Apps Universal

What is the name of the vSphere package included in Horizon Solutions?

VMware vSphere Foundation for VDI (VVF for VDI)

What does it include?

• vSphere Enterprise Plus

• vCenter Standard

• vSAN Enterprise (100 GB) (licensed per Core)

So how much space have I included in vSAN?

Well, the game is quite simple: for each core of my vSphere cluster on which I host VDI and on which I have the VVF for VDI licenses, just multiply 100GB by the number of CORES. (there are no restrictions on the number of cores)

Let’s focus on the vSAN Enterprise license… what difference do we have from the previous Bundle?

  • vSAN Enterprise includes the same features as vSAN Advanced plus all those of vSAN Enterprise which are:
    • Data-at-rest and data-intransit encryption
    • File services
    • VMware HCI Mesh™2

In this link more information:

VVF_VDI_SPD_July2024.pdf (broadcom.com)

VMware vSphere Foundation for VDI (VVF for VDI)

Nested ESXi Virtual Appliances

A logo for a software company

Description automatically generated

In the field of home labs, nested virtualization is the must to be able to create vSphere environments in a short time to test or try new features even in the EUC environment.

To help those who want to use nested virtualization, William Lam has been providing Nested ESXi Virtual Appliances for some years now.

Until a few days ago nested ESXi virtual appliances were available to download from William’s website (https://williamlam.com/) and since yesterday they have been available on the VMware Flings Community (Accessible with a free Broadcom community account that can be created here)

The convenience of using these virtual appliances is the ability to also create automatic scripts to be able to create nested environments such as vSphere clusters, vSAN and VCF (VMware Cloud Foundation) environments in a short time, which can then be used to test Omnissa’s EUC solutions as well.

Here is William’s official post

A screenshot of a phone

Description automatically generated

Nested ESXi Virtual Appliances

Approach to updating a horizon infrastructure

When approaching the upgrade of an infrastructure in the EUC world (as with most technologies in the IT world) it is necessary to define a roadmap of activities and follow it carefully. In many cases, IT technology vendors already have update procedures in place that should be followed carefully. When I started working as a consultant, the documentation was very scarce (we are talking about the end of the 20th century and the beginning of the 21st…) and the procedures were poorly documented and only those who took courses or had experience could approach with a certain “tranquility” updates of production environments.

Going back to EUC infrastructures and focusing on the VMware by Broadcom world (still for a while….given the transfer of the technology in question) we have a precise update sequence, especially if we talk about + technologies that interact with each other, and the need to verify the interoperability between the various technologies.

For example, we have this KB that gives us the upgrade sequence of a Horizon 8 infrastructure:

Update sequence for Horizon 7, Horizon 8, and compatible VMware products (78445)

A diagram of software

Description automatically generated

And the ability to use the interoperability portal:

https://interopmatrix.vmware.com/Interoperability

A screenshot of a computer

Description automatically generated

In my ten-year experience in updates and maintenance of vSphere and Horizon infrastructures, it has often happened that I have had to intervene and manage post-upgrade problems, where in most cases the problems were generated by the fact that I did not perform the update in the correct order or even did not complete all the upgrade steps.

For example, I have experienced situations where, following upgrades, the copy and glue to and from VDI sessions no longer worked correctly in a Horizon infrastructure.

In the end, the problem was solved by also performing the update step of the Horizon ADMX templates in Active Directory, something that the customer or whoever had done the update for him had not done.

Approach to updating a horizon infrastructure

VMware Pre Broadcom vs VMware Broadcom – Primi dati reali

Attenzione è una mia valutazione….quindi non sparate sul sistemista

Broadcom ha acquisito VMware, ormai lo sappiamo tutti.
La situazione di incertezza aleggia ovunque soprattutto sul mondo vSphere e sui costi (con tanti competitor che provano a ritagliarsi la loro fetta di mercato togliendole al leader indiscusso di questi anni)


Finalmente in questi giorni incomincio ad avere i primi dati effettivi (Prezzi ecc…) su cui iniziare a fare i primi ragionamenti.
!!Attenzione non voglio dare giudizi ma voglio solo paragonare due offerte fatte allo stesso cliente che abbiamo dovuto rivedere a seguito del nuovo listino (E parliamo di prezzi di listino.. senza eventuali scontistiche)!!

Ragioniamo su un cluster vSphere con 3 nodi da 2 processori ciascuno da 16 core.

Con le precedenti licenze e il vecchio listino nello scenaro ipotizzato dovevamo considerare:

  • Licenza VMWARE VCENTER SERVER 8 STANDARD
  • Licenza VMWARE VSPHERE 8 STANDARD FOR 1 PROCESSOR
  • Support/Subscription
  • Support/Subscription

Con il nuovo listino e le nuove tipologie di licenze invece dobbiamo considerare:

  • VMWARE VSPHERE STANDARD per core (Che comprende la licenza di vCenter)

Entrambe le soluzioni con 5 anni.

Da una prima analisi le prime valutazioni sono:
Con il nuovo listino si viene a pagare circa 30-35% in meno.
Ho una semplificazione nella quotazione (una sola voce rispetto alle 4 precedenti)

Ovviamente:

  • Non abbiamo le licenze perpetue (comunque chi non vuole il supporto sul proprio ambiente di produzione o la possibilità di effettuare aggiornamenti?)
  • é una prima offerta e la quotazione può dipendere da vari fattori e i prezzi potrebbero nuovamente cambiare
  • Le funzionalità all’interno dei bundle possono essere leggermente differenti (il link per vedere le funzionalità presenti nei nuovi bundle VMware vSphere® Product Line Comparison)
  • Posso aver sbagliato i calcoli 🙂
  • Possono avermi dato dei prezzi sbagliati 🙂 spero di no per il cliente 🙂

ma aspettavo di avere due informazioni reali per fare le mie prime considerazioni.

L’unica cosa che posso dire è di valutare con attenzione il cambio …. (io sono il primo che accetta nuove sfide..) ma attenzione a tutti i prezzi nascosti e valutate bene!

P.S. se qualcuno ha delle esperienze in merito … condividiamole.

VMware Pre Broadcom vs VMware Broadcom – Primi dati reali