Deployment of Windows VMs using customization or using customization specifications fails with the error "Cannot complete customization"

Products

• VMware vSphere ESXi

Issue/Introduction

• Deployment of VMs with customization or using a customization specification fails with below:

Cannot complete customization

• Similar entries can be found in the vpxd.log -

error vpxd[7F36C9B#####] [Originator@6876 sub=VmCustomizer opID=CustomizeGuestOsDialog-apply-1027####-ngc:70310###-1e] Creating deploy pkg: oobeSystem.Microsoft-Windows-Shell-Setup.UserAccounts.AdministratorPassword.EncryptedValue
info vpxd[7F36C9B#####] [Originator@6876 sub=Default opID=CustomizeGuestOsDialog-apply-1027####-ngc:70310###-1e] [VmCustomizer] Successfully deleted file/directory /tmp/imcf-v1E###
info vpxd[7F36C9B#####] [Originator@6876 sub=vpxLro opID=CustomizeGuestOsDialog-apply-1027####-ngc:70310###-1e] [VpxLRO] -- FINISH task-28###
info vpxd[7F36C9B#####] [Originator@6876 sub=Default opID=CustomizeGuestOsDialog-apply-1027####-ngc:70310###-1e] [VpxLRO] -- ERROR task-28### -- vm-8### -- vim.VirtualMachine.customize: vim.fault.CustomizationFault:
--> Result:
...
...
-->    identity = (vim.vm.customization.Sysprep) {
-->       guiUnattended = (vim.vm.customization.GuiUnattended) {
-->          password = (vim.vm.customization.Password) null,
-->          timeZone = ##,
-->          autoLogon = true,
-->          autoLogonCount = 2
-->       },
...
...
... 

 

Please Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

• This issue arises when the Password parameter within the Customization Specification is left empty.

Resolution

• Ensure the Windows Administrator password field in the customization specification is not empty.