We have an issue with Windows (2008 R2 SP1) o/s customization on our ESXi 5.1 update 3 (build 1743533) hosts
since we have upgraded the vCenter Server from 5.1.0 to the last 5.5 update 1 version.
The sysprep works normally and customization seems to be good in the end,
but we don't get the "Customization Succeeded" anymore in the VM Events.
Here is the end of the "C:\Windows\TEMP\vmware-imc\guestcust.log" file:
[2014-06-09T12:43:50 INFO] GuestCustUtil invoked.
[2014-06-09T12:43:50 INFO] Params: flagComplete
[2014-06-09T12:43:50 DEBUG] Customization in progress set to 0 at 2014-Jun-09 12:43:50
[2014-06-09T12:43:50 DEBUG] Rpci: Sending request='deployPkg.update.state 5 0 C:\Windows\TEMP\vmware-imc\guestcust.log'
[2014-06-09T12:43:50 DEBUG] Rpci: Sent request='deployPkg.update.state 5 0 C:\Windows\TEMP\vmware-imc\guestcust.log', reply='Unknown command', len=15, status=0
[2014-06-09T12:43:50 ERROR] Unable to set customization status in vmx.
[2014-06-09T12:43:50 DEBUG] SysprepDecrypter has unobfuscated the password successfully
That's the only error we have in all logs (C:\Windows\System32\sysprep\Panther\setupact.log is 100% successfull)
and it seems it's just the ending "GuestCustUtil flagComplete" that is not working.
Might it be a compatibility issue with the vCenter 5.5 GuestCustUtil command (dated 04/16/2014) with our ESXi 5.1 update 3 hosts?
Thanks in advance for any clue.
Hi, I'm having similar issue, but I'm using vCenter Server 5.1.0, 1473063 and same ESXi build as yours ESXi 5.1 build 1743533. My VMs are in customization loop and I can see imcXXX.tmp file in each VM datastore even after the customization. Which is technically wrong as imcXXX.tmp file should only be there for customization to run and after customization finished, it should be removed.
Please let me know if you've fixed your issue.
Now that's what called a great fix! Attached new patch through Update Manager and deployed VM again from the template. No more annoying customization message! Cheers guys.