Windows Virtual Machine retains original SID after cloning with Guest Customization

Products

• VMware vCenter Server

Issue/Introduction

When you clone a Windows Virtual Machine using a Guest Customization Specification, the Security Identifier (SID) is not updated and remains identical to the source VM or Template.

Environment

VMware vCenter 8.0.x

Cause

You observe that the Guest Customization process fails to initiate. Reviewing the VM Events in vCenter reveals the following error:

"The number of network adapter settings in the customization specification: [X] does not match the number of network adapters present in the Virtual Machine: [Y]"

When this mismatch occurs, the customization workflow terminates before the Sysprep phase, resulting in the SID not being reset.

Resolution

You must ensure the number of network adapters defined in the Customization Specification matches the hardware configuration of the Virtual Machine or Template.

1. Log in to the vSphere Client.
2. Navigate to Policies and Profiles > VM Customization Specifications.
3. Select your specification and click Edit.
4. Navigate to the Network section.
5. Add or remove network adapters until the count matches the target VM/Template hardware.
6. Save the specification and attempt the clone operation again.