2020/02


Custom Hostname Generation in vRealize Automation 8

Reading time: 12 minutes
If you’re like most large IT environments, a device naming standard is common to maintain order on your network when deploying new devices. Some IT environments utilize simple naming standards, while others are complex and might vary depending on location, device type, device usage, or some other abstract reason. vRealize Automation 8 introduced significant improvements over vRealize Automation 7 when it comes to machine naming including support for naming templates based on:

vRealize Automation 7.x Data Collection Stuck "In Progress" for Compute Resource

Reading time: 3 minutes
Over the past several years of operating multiple vRealize Automation 7.x deployments, I’ve come across a situation where the data collection status for the Inventory or State data stays stuck at “In Progress” for a particular vSphere cluster. Usually, this occurs because a vSphere Agent executing the job was stopped mid-process. I initially searched online for a solution and could not find anything that helped. This left me to digging through the vRealize Automation 7.

VMware Updates Per-CPU Licensing Model to 32-Cores Per CPU

Reading time: 3 minutes
With the new 64-core AMD EPYC processors available and the 56-core Intel Xeon on the horizon, it was bound to happen… On February 3, 2020, VMware announced that effective April 2, 2020, all per-CPU licensed products will be limited to 32 physical cores per CPU license. This change means that those shiny new 64-core processors will require the purchase of 2 CPU licenses for each processor going forward. This change affects all per-CPU licensed products, including vSphere, vSAN, NSX, and Enterprise PKS, to name a few.


Search

Get Notified of Future Posts

Follow Me

Twitter Icon
LinkedIn Icon
RSS Icon

Recent Posts