This past week we dropped the latest versions of the VMware Aria Suite: VMware Aria Operations 8.18.7 VMware Aria Operations for Logs 8.18.7 VMware Aria Suite Lifecycle 8.18.0 Patch 8 VMware Aria Automation Orchestrator 8.18.1 U6 (Patch 6) VMware Aria Automation 8.18.1 U5 (Patch 5) I'm running the following in my lab: VMware Aria Operations 8.18.6 VMware Aria Operations for Logs 8.18.6 VMware Aria Suite Lifecycle 8.18.0 Patch 7 VMware Aria Automation 8.18.1 U4 (Patch 4) Let's

When downloading the Aria Suite Lifecycle Easy Installer for Aria Automation recently I noticed Aria Automation has an OVA. I've only ever installed Aria Automation via the ASLCM Easy Installer, but this OVA implies I could do it stand alone, so I started looking around. And sure enough, as part of the ASLCM Easy Installer, you can actually skip the Automation deployment and just install ASLCM and vIDM. For that matter, you can also skip the vIDM deployment from the ASLCM E

To go along with my fresh deployments of Operations and Operations for Logs, I wanted a fresh deployment of Automation, here goes. I downloaded the VMware Aria Suite Lifecycle 8.18 Easy Installer for Aria Automation 8.18.1, you can get it here. Once downloaded, I double clicked the .iso to mount it. The documentation can be found here. After clicking Open I was presented with the contents. Drill down to find the installer which is located here if you're installing from a Win

For customers running several instances of the various Aria products, it can be helpful to tell users what instance they are actually logging in to. With Aria Operations and Operations for Logs this can be done with a login message. In Operations this can be found in Administration - Global Settings - User Access - Login Message. Now, when users log into Operations they will be presented with that message, it looks like this. If you have a Development instance, a Staging ins

Now that we've upgraded Aria Suite Lifecycle Manager (ASLCM) to 8.18 and loaded the Aria Operations, Operations for Logs, and Automation 8.18 binaries into ASLCM, we can proceed with our product upgrades. Let's start with Aria Automation. Log into ASLCM, go to Lifecycle Manager - Environments - select your environment - then the Automation tab. As you'll notice, the UPGRADE button is available now that the 8.18 binaries have been loaded, click UPGRADE Once complete, you can

We just upgraded our Aria Suite Lifecycle Manager (ASLCM) to 8.18, which we can still do online, next we'll upgrade Operations, Logs, and Automation, but first we'll need those binaries. We can no longer download binaries directly from VMware Customer Connect, so we have to load them into ASLCM manually, here's how. Log into the Broadcom Support Portal and go to My Downloads, these are the three tiles you'll want. We're upgrading from previous releases, so we'll download the

Aria Automation 8.16.2 dropped last night, let's upgrade! You can find the Release Notes here if you're interested. Log into your Aria Suite Lifecycle Manager and check for new Product Support Packs (PSP) via Lifecycle Operations - Settings - Product Support Pack - CHECK SUPPORT PACKS ONLINE. Once selected you can watch the progress in Requests. Once a new PSP is discovered it will show back on the Product Support Pack page. Which you can apply by clicking APPLY VERSION, the

On February 20th the original Aria 8.16 and 8.16.1 updates were released, but we quickly pulled them due to a missing feature. They've been updated and republished, here they are! Aria Suite Lifecycle Manager 8.16 Release Notes Aria Operations 8.16.1 Release Notes Aria Operations for Logs 8.16 Release Notes Aria Automation 8.16.1 Release Notes KB with upgrade details Let's apply them. Aria Operations for Logs 8.16 needs to be done locally, let's do that one first. First do

Aria updates are here, they were released originally on 2.20.2024. Aria Operations, Aria Operations for Logs, Aria Suite Lifecycle Manager 8.16 and Aria Automation 8.16.1 dropped last week, let's upgrade! Important links here: Aria Operations 8.16 Announcement Blog Aria Operations 8.16 Release Notes Aria Operations for Logs 8.16 Release Notes Aria Automation 8.16 Release Notes Aria Suite Lifecycle 8.16 Manager Release Notes Let's get started by upgrading our Aria Suite Life

This morning we announced VMSA-2024-001 with the following Synopsis: VMware Aria Automation (formerly vRealize Automation) updates address a Missing Access Control vulnerability (CVE-2023-34063) The fix is addressed in Aria Automation 8.16, which requires Aria Suite Lifecycle Manager 8.14 PSPack 4, which is now GA. Go to Lifecycle Operations - Settings - Product Support Pack - CHECK SUPPORT PACKS ONLINE and get it. Once applied, download Aria Automation 8.16 via Lifecycle Op

The 8.14.1 updates to Aria Operations, Aria Operations for Logs, and Aria Automation were dropped in late November, just getting around to applying them, here's how you do it with Aria Lifecycle Manager. Log in to Aria Lifecycle Manager and check for the latest Product Support Packs via Settings - Product Support Packs - CHECK SUPPORT PACKS ONLINE. You'll find the latest available to be 8.14.0.3. Click APPLY VERSION, once done you'll have the latest. Next get the 8.14.1 binar

We've talked about Aria Automation Approval Policies and Lease Polices, but haven't touched on Resource Quota Policies, we'll do that here. Resource Quota Policies are a nice way to put limits on the amount of resources (vCPU, Memory, and Disk) consumers can use, let's have a look. You can always put limits on resources in your Cloud Templates themselves, but Resource Quota Policies give you a bit more power, with the ability to put limits on Organization, Projects, and User

When I first started building VMs with Aria Automation I would configure vCPU and Memory via Properties on the VM object itself, something like this. This prompts the user for input, giving them a default, minimum, and maximum available values for vCPU and Memory (among others). There are many properties you can set at build time, for a list of all available options, click the properties link in your Cloud Template. This is how I learned to size VMs, but there is another way,

This morning while debugging an Aria Automation Cloud Template I thought to myself, I should really be backing these up, so I configured the integration with GitHub and planned to export all Cloud Templates to one of my GitHub Repositories for safe keeping. Well, that's not how it works, you can only import from GitHub. I don't love that, but I explored the option nonetheless. I also spoke to the Product Manager and opened a feature request for the push/export functionalit

Last time we discussed renaming VMs deployed with VMware Aria Automation, this blog will detail how to add those same VMs being deployed with Aria Automation to Microsoft Active Directory (AD). We'll do it with vSphere Customization Specifications, here's how. Log into vCenter and go to Menu - Policies and Profiles - VM Customization Specifications. You can see that I have three VM Customization Specifications, all for Windows VMs, one of which we already used to rename our

If you deploy VMs with Aria Automation without adjusting their names, they'll look something like this. You can rename after the fact, but it's not ideal. In a previous blog, we discussed how to rename VMs by calling a vRO Workflow (based on a subscription) and Customization Specifications, but there is another way, Custom Names! Let's explore. Custom Names are a way for you to rename VMs (and other things) deployed from Aria Automation. You build Naming Templates to perfo

Last night VMware dropped several new releases, here they are! Aria Operations 8.14 and Aria Operations SaaS (October 2023) What's New Blog 8.14 Release Notes SaaS October 2023 Release Notes Aria Operations for Logs 8.14 and Aria Operations for Logs SaaS (October 2023) What's New Blog Release Notes Aria Automation 8.14 and Aria Automation SaaS (October 2023) What's New Blog Release Notes Aria Suite Lifecycle 8.14 What's New Blog Release Notes First, let's upgrade Aria Suite

As you know, VMware Aria Automation includes an embedded instantiation of Aria Automation Orchestrator, which includes hundreds of Workflows. I'd like to make some of these Workflows available to consumers via Service Broker, let's do it! The documentation can be found here, but let's walk through it. For the record, I'm running an on-prem deployment of Aria Automation 8.13. First, go to Assembler - Infrastructure - Connections - Integrations and configure your Orchestrator

We dropped VMware Aria Operations, Aria Operations for Logs, and Aria Automation 8.12 yesterday, let's update! First, a few helpful links: Aria Operations 8.12 Release Notes | Aria Operations 8.12 Blog Aria Operations for Logs 8.12 Release Notes | Aria Operations for Logs 8.12 Blog Aria Automation 8.12 Release Notes | Aria Automation 8.12 Blog Let's start by upgrading Aria Lifecycle Manager (formerly vRealize Suite Lifecycle Manager) to 8.12, which will give us the necessary