Browsing: Guides & Tutorials

Introduction VCF Automation 9.x is easy to misunderstand if your mental model was built around vRealize Automation or Aria Automation. The familiar product lineage is still present, but the platform now exposes two materially different consumption paths. One path preserves the established VM-centric automation model. The other places organizations, projects, vSphere Namespaces, and Supervisor-backed services at the center of private cloud consumption. That distinction is more important than the product rename. It changes how architects define tenancy, allocate capacity, structure networks, delegate administration, publish services, and decide where policy is enforced. It also changes what a virtual machine represents operationally.…

TL;DR August 2, 2026 is not the date when every high-risk AI obligation suddenly becomes enforceable. It is the point when the EU AI Act becomes a much more immediate evidence problem for enterprise technology leaders. Article 50 transparency duties begin to apply. The European Commission gains enforceable authority over general-purpose AI model providers, including the ability to request documentation, evaluate models, require corrective measures, and impose fines. National authorities begin operating in a broader enforcement environment for obligations already in effect. The core Chapter III requirements for Annex III high-risk AI systems are now scheduled for December 2, 2027.…

TL;DR A newer VMware Kubernetes Service version may be missing from the vCenter upgrade interface even when the environment is functioning correctly. VKS versions bundled with the installed vCenter build appear automatically. Newer asynchronous VKS releases must first be downloaded from the Broadcom Support Portal and registered by uploading the release’s package.yaml file. Registration does not upgrade a Supervisor. It only makes the VKS version known to vCenter. The version must then be activated on the appropriate Supervisor after its compatibility, workload-cluster impact, content-library readiness, and upgrade path have been validated. The correct workflow is: Inventory the current vCenter, Supervisor,…

TL;DR AI ROI is stalling because many organizations are managing experiments, not investments. A pilot can prove that a model works, users are interested, or a workflow can be partially automated. It does not prove that the organization can produce repeatable business value after integration, data, security, change management, support, and operating costs are included. CEOs and CIOs should replace disconnected AI pilots with a governed investment portfolio. Every initiative should have an accountable business owner, a measured baseline, a defined unit of value, fully loaded unit economics, evidence-based scale gates, and termination criteria agreed before enthusiasm turns into sunk…

TL;DR No network fabric is universally superior for enterprise AI. A well-designed Ethernet network is normally the right foundation for out-of-band management, in-band platform services, north-south inference, registry access, and many storage flows. It is also sufficient for single-node training and inference workloads that do not exchange latency-sensitive data across GPU nodes. A specialized RDMA fabric becomes important when inter-node communication sits on the critical path of useful GPU work. Frequent all-reduce operations, tensor or expert parallelism across nodes, large synchronous jobs, direct storage-to-GPU paths, and expensive GPU idle time all strengthen the case for RoCEv2 or InfiniBand. RoCEv2 preserves…

TL;DR Enterprise AI is not one market. It is a connected ecosystem of business applications, model providers, data platforms, private AI operating models, accelerated infrastructure, networking, and physical facilities. The vendors that create the most technical capability do not always capture the most enterprise value. Value tends to accumulate around control points: user distribution, proprietary data, workflow authority, model access, platform governance, infrastructure bottlenecks, and energized data-center capacity. NVIDIA currently occupies the broadest strategic position because its influence extends from accelerators and networking into inference software, enterprise AI tooling, scheduling, and validated architectures. However, Microsoft, OpenAI, Salesforce, ServiceNow, Dell, HPE,…

During a VMware Cloud Foundation 9 deployment, the VCF Installer becomes one of the most important control points in the environment. It is not just a temporary wizard screen. It is the place where deployment state, validation, bring-up workflows, and local administrative access intersect. That becomes a problem when the admin@local password is missing, mistyped, expired from operational handling, or simply not recorded in the right vault entry. The confusion usually comes from the way the installer handles local credentials. Operators may remember setting the root password or using the vcf account for SSH, but the web login depends on…

TL;DR Azure Local 2607 is an architecture-significant release, but it should not receive blanket production approval. The release baseline changed quickly. Microsoft first published Azure Local 12.2607.1003.69 on July 22, 2026, then published 12.2607.1003.71 on July 29, 2026. The newer build supersedes .69 while retaining OS build 26100.33158. Microsoft also changed the Trusted Launch position: the startup failure affecting Trusted Launch VMs created on earlier releases is now listed as fixed in .71. That changes the upgrade decision. The appropriate posture is no longer to block every 2607 upgrade involving existing Trusted Launch VMs. Instead: Reject the superseded 12.2607.1003.69 package.…

Introduction Azure Local is frequently described with one of two incomplete labels. One camp calls it cloud-managed infrastructure, implying that an Azure outage should stop the platform. The other calls it on-premises infrastructure, implying that Azure connectivity is optional once deployment is complete. Neither description is precise enough for architecture, operations, or incident response. Azure Local has a local workload and infrastructure data plane, but it also has cloud-connected management, reconciliation, governance, lifecycle, billing, and identity dependencies. A running virtual machine does not ask Azure Resource Manager for permission to execute every CPU instruction. However, creating a new Azure Local…

TL;DR Shadow AI is not merely unapproved software. An unsanctioned agent, copilot, script, or autonomous workflow can authenticate as a machine identity, call a model provider, read enterprise data, invoke tools, modify systems, and create spend without appearing in a centralized AI inventory. The practical discovery method is evidence correlation. Start with model-provider traffic, provider usage and audit records, non-human identities, CI/CD and Kubernetes inventory, runtime execution, package installation, secrets access, data access, and billing. No single signal proves that an agent exists. Multiple signals tied to the same workload, identity, time window, and owner create the defensible finding. This…