Default gateway not populating in Windows VM deployments via VMware Aria Automation

Products

• VCF Automation

Issue/Introduction

When deploying Windows virtual machines from a template in VMware Aria Automation, the virtual machine may fail to populate the default gateway, even when the network profile correctly specifies it. This issue occurs when the template itself retains a static IP configuration, which prevents Aria Automation or DHCP/IPAM from successfully reconfiguring the network adapter during deployment.

Environment

• VMware Aria Automation 8.x
• Windows Server Templates (2019/2022/2025)

Cause

The virtual machine template contains a hardcoded static IP address or gateway configuration in the Windows registry or network adapter settings. During deployment, the Guest OS customization process or Aria Automation cannot overwrite these settings because the existing static configuration conflicts with the expected dynamic assignment.

Resolution

1. Power on the template VM.
2. Open the Network Connections control panel.
3. Modify the network adapter settings to use DHCP instead of a static IP.
4. Remove any hardcoded default gateway addresses.
5. Run sysprep /generalize /oobe /shutdown to ensure the template is clean.
6. Convert the VM back to a template in vCenter.
7. Trigger a new deployment via VMware Aria Automation to verify the gateway is now populated correctly.

Additional Information

Ensure that your Aria Automation Network Profile does not conflict with the template settings. If the issue persists, review the C:\Windows\Panther\setupact.log for errors related to network re-assignment.