You can monitor progress back in Software Update. Once complete, it will look like this. The Operations Cluster will come back online on its own, as shown in System Status. You can also confirm the upgrade back on the About page.

download the necessary binaries, in my case I'm grabbing the Upgrade Assessment Tool and the Upgrade Pak Back to INSTALL A SOFTWARE UPDATE and point it at the 8.18.2 binaries. Back on the main UI and the About page, it should look like this.

Checking my Inbox I see: Clicking the link takes you back into Service Broker - Inbox - Approvals. Back on the Deployment History tab. Back in Cloud Assembly - Deployments you can see your new VM, which was formally Approved and built.

Back in VCF Operations you'll notice the new Unified Cloud Proxy. Looking back at Infrastructure Operations - Analyze, we now have logs!

Exchange, which people use to share things like vROps dashboards and super metrics, vRA Blueprints, vRO Packages and Workflows, vRLI Content Packs, and more.

Allow the user to select an IP from an IP Block Back in Assembler - Design we can see the YAML Code, Back on the Service Broker Catalog we'll now see our Windows 2022 VM Template/Blueprint.

Back to our Operations Log Forwarding, once you've configured things, click APPLY CHANGES bottom right

Back at the Cluster Summary page, let's add these Custom VM Profiles to the Virtual Machine Remaining Give the vROps engine 10-15 minutes to make these calculations and check back.

The Operations cluster will come back up on its own.

This has been a common question since Workload Optimization was introduced back in vROps 6.7. Back to DRS, there are four automation levels available: Disabled - DRS is disabled.

Now back on the Home - Overview page you'll notice the map has been populated, the Inventory is starting Back in the Admin UI ( https://your_ops_fqdn_here ), you'll want to enable SSH in case you need to SSH

can't connect to your VMware Private Cloud vCenters, we can add a source by clicking IMPORT INVENTORY back the migration of just one Cluster, you must first take all of the Clusters out of scope, then bring back

This will assign your new Tag to the Cluster you selected, which will be reflected back on the Tags tile

Back in the Internal API we can now construct our call and run it using the Datacenter ID.

Once adjusted and published, back in Service Broker we can request our VM. Click REQUEST. Once done, let's confirm the VM was added to AD domain TVS back in vCenter.

Back in Policies, you can now see our new Alert. But you'll notice it's still not Active. Back in Policies you'll notice our new Policy (including our new Alert Definition) is now Active.

Back in Settings - Patch Binaries, you'll notice PATCH1 for VMware Aria Suite Lifecycle 8.12, let's download Back on Settings, select System Patches. Then select NEW PATCH top right. You can confirm it back in the Environments tab. And we're done!

We introduced a metric called Cluster Availability (%) back in Operations 8.16, here's how it works.

Go to Software Update - INSTALL A SOFTWARE UPDATE and point it at your APUAT pak file. Back on the System Status page you will show this, notice version 8.18.3 (24746341) And finally the About

Confirmation back on the Operations UI About page.