You’ve moved workloads to the new “Azure Local” clusters (rebranded Azure Stack HCI). Now, MCS-provisioned VMs power on but never register. They are stuck waiting for an IP that never arrives.
Symptom Matrix:
ProvisioningState: Failed, Network: DHCP Timeout, ClusterVersion: 2503+.
Architectural Root Cause:
A conflict between the Citrix VDA’s network initialization and the Azure Local “Logical Network” driver which fails to process MAC address assignments for cloned VMs.
Surgical Fix:
A PowerShell script to reset the “VNET-Adapter” on the host node and force a MAC address refresh in the MCS Machine Catalog.
Cloud-hybrid collisions are the new normal. A network reset is a band-aid; a unified architecture is the cure. [Validate your Azure Local deployment]
Ready to Make Things Happen
Contact us today for impartial, expert advice from our lead Digital Workspace subject matter expert.
We’ll help you build a fast, secure, and future-ready digital workspace—perfectly aligned with your business goals.