To be able to deploy the VMs.
Symptoms:
YYYY-MM-DDTHH:MM:SS info vpxd[08396] [Originator@6876 sub=VmProv opID=kdtz7aj8-520539-auto-b5ng-h5:70108018-13-02] Created VM vim.VirtualMachine:vm-3998 (ds:///vmfs/volumes/########-######ef/vmname/vmname.vmx) on host [vim.HostSystem:host-555,hostname] (hostname)
} to VM ds:///vmfs/volumes/########-######ef/vmname/vmname.vmx on host <IP>
YYYY-MM-DDTHH:MM:SS warning vpxd[42562] [Originator@6876 sub=InvtVmDb opID=HB-host-549@235344-3f385f7b] Skipping update of NIC settings for unknown device; key=-1, VM id=1545
YYYY-MM-DDTHH:MM:SS info vpxd[08396] [Originator@6876 sub=pbm opID=kdtz7aj8-520539-auto-b5ng-h5:70108018-13-02-01] Reconfigure profile association for vm vm-3998
YYYY-MM-DDTHH:MM:SS info vpxd[08396] [Originator@6876 sub=vmmoVm opID=kdtz7aj8-520539-auto-b5ng-h5:70108018-13-03] Powering on vm vmname (ds:///vmfs/volumes/########-######ef/vmname/vmname.vmx) in compute resource <name> on host <hostname>
YYYY-MM-DDTHH:MM:SS info hostd[2102433] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 8793 : vmname on hostname in ha-datacenter is powered on
YYYY-MM-DDTHH:MM:SS info hostd[2102433] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 8794 : Started customization of VM vmname. Customization log located at C:/Windows/TEMP/vmware-imc/guestcust.log in the guest OS.
YYYY-MM-DDTHH:MM:SS info hostd[2100370] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 8795 : An error occurred while customizing VM vmname. For details reference the log file C:/Windows/TEMP/vmware-imc/guestcust.log in the guest OS.
YYYY-MM-DDTHH:MM:SS| vmx| I125: DICT ethernet0.virtualDev = "vmxnet3"
YYYY-MM-DDTHH:MM:SS| vmx| I125: DICT ethernet0.dvs.switchId = "50 08 91 17 ## ## ## ##-## ## ## ## 50 c5 b2 e8"
YYYY-MM-DDTHH:MM:SS| vmx| I125: DICT ethernet0.startConnected = "FALSE"
YYYY-MM-DDTHH:MM:SS: : INFO] GuestCustUtil invoked.
YYYY-MM-DDTHH:MM:SS: : INFO] Checking for Windows Sysprep Respecialize operation.
YYYY-MM-DDTHH:MM:SS: : DEBUG] Sysprep process is not running.
YYYY-MM-DDTHH:MM:SS: : INFO] Windows Sysprep Respecialize operation was not detected.
YYYY-MM-DDTHH:MM:SS: GuestCustUtilLib: DEBUG] customizationState: 4, errCode: 0
YYYY-MM-DDTHH:MM:SS: GuestCustUtilLib: DEBUG] Got VMX response: ''
YYYY-MM-DDTHH:MM:SS: : DEBUG] Temporary sysprep dir path: C:\sysprep
YYYY-MM-DDTHH:MM:SS: : DEBUG] Copying file/directory from 'sysprep' to 'C:\sysprep'
YYYY-MM-DDTHH:MM:SS: : INFO] Sysprep File is C:\Windows\Panther\unattend.xml
YYYY-MM-DDTHH:MM:SS: : DEBUG] HandleCustomizationFailed
YYYY-MM-DDTHH:MM:SS: : DEBUG] Customization in progress set to 0 at 2020-Sep-03 10:29:14
YYYY-MM-DDTHH:MM:SS: GuestCustUtilLib: DEBUG] customizationState: 4, errCode: 100
YYYY-MM-DDTHH:MM:SS: : DEBUG] RpcChannel: Recved 0 bytes
YYYY-MM-DDTHH:MM:SS: : DEBUG] RpcChannel: Request OK: reqlen=95, replyLen=0
YYYY-MM-DDTHH:MM:SS: : INFO] GuestCustUtil exiting.
Guest customization exits with customizationState: 4, errCode: 100
Note: The preceding log excerpts are only examples. Date, time and environmental variables may vary depending on your environment.
VMware vCenter Server 6.x
VMware vCenter Server 7.0.x
This issue is resolved in VMware vCenter Server 6.5 U3n, 6.7 U3m and 7.0 U1c patches. To download go to the Broadcom Downloads page.
Workaround:
Use a shorter computer name in the Windows OS for the VM template.
Perform the below steps:
It fails with GetComputerEx() Win32API we are using to get current VM's name, For more information refer to Microsoft Document https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-getcomputernameexa
If the buffer is smaller than the returned value there will be "ERROR_MORE_DATA" error.
Impact/Risks:
Changing the VM templates computername to a shorter one.