To prevent or resolve this issue, VM need to be generalized with one of the following methods:
Method 1: Generalize the source VM using Sysprep before it is cloned or converted into a template
- In the template VM, run sysprep.exe
C:\Windows\System32\Sysprep\sysprep.exe
- In the System Preparation Tool window:
- For System Cleanup Action, select Enter System Out-of-Box Experience (OOBE)
- Check the Generalize box.
- For Shutdown Options, select Shutdown from the dropdown menu.
- Click OK.
- Power-off the VM. (NOTE: Do not power on the VM again)
- Convert the VM to template.
Method 2: Use VM Customization Specification
- Create a Customization Specifications for Windows VMs
- In the vSphere Client, Select Menu > Policies and Profiles, and under Policies and Profiles, click VM Customization Specifications.
- Click the Create a new specification icon.
- Select the Generate a new security identity (SID) option.
- Complete the remaining fields with appropriate information. For more details, refer to Create and Manage Customization Specifications for Windows and Linux.
- Customize the new VM during cloning or deployment
- On the Select clone options page, select the Customize the operating system check box and click Next.
- On the Customize guest OS page, select the customization specification from the list and click Next.
- Apply the Customization Specifications to the new VM
- Right-click the VM in vSphere inventory, select Guest OS > Customize Guest OS.
- Select a customization specification from the list and click OK.
Method 3: Generalize the new VM using Sysprep
- In the VM, run sysprep.exe
C:\Windows\System32\Sysprep\sysprep.exe
- In the System Preparation Tool window:
- For System Cleanup Action, select Enter System Out-of-Box Experience (OOBE)
- Check the Generalize box.
- For Shutdown Options, select Shutdown or Reboot from the dropdown menu.
- Click OK.