Windows Server 2025 VM Template Clones Inherit Template IP Address During Deployment

Products

• VMware vCenter Server

Issue/Introduction

When creating a VM from a Windows Server 2025 template using the "Customize the OS" option during deployment, the newly deployed VM inherits the same IP address as the template VM, causing IP conflicts or APIPA addressing.

Environment

VMware vSphere

 

Cause

The VM template was not fully generalized or properly prepared for cloning and customization. Specifically:

• Sysprep (generalization) on the template VM either failed or was incomplete.
• The template retained static IP or network profile settings.
• VMware Guest Customization failed to apply unique network settings during deployment.
• DHCP configuration was not effectively applied, resulting in APIPA addresses on deployed VMs.

Resolution

• Run Sysprep with the generalize option on the Windows Server 2025 VM to remove unique system identifiers (IP, SID).
• Ensure the VM is not joined to Active Directory and uses DHCP with no static IP before converting to a template.
• Create or update a Guest Customization Specification in vCenter to assign DHCP or unique static IPs, and apply it during deployment.
• Confirm VMware Tools is installed and running on the template VM.
• Convert this VM to template and try deploying the VM from the updated template and verify it obtains a unique IP without conflicts.

Additional Information

Sysprep generalization is the Microsoft-supported method to prepare Windows images for cloning and deployment, preventing IP and SID duplication.

Create a Customization Specification for Windows

Sysprep (Generalize) a Windows installation