Cannot deploy template: cannot complete customization

[Francisco317]

I have ESX 4.1 with VC 4.1 using a 4.1 client. I setup a template, windows 2008 x64 sp2, installed VMtools on it and then tried to deploy a new VM from the template. At about 99%, it fails with Cannot deploy template: cannot complete customization. that is the only error I get. Any ideas?

[Francisco317]

I also forgot to add that the VM is automatically deleted after, so I can't even access the VMWare logs! When I don't use customization, I can deploy the template.

[WaffleSniffer]

Hi

You mention that the VM is deleted after the deploy task fails so you can't view the logs, however, you should be able to find the info you are after in the vpxd logs (C:\ProgramData\VMware\VMware VirtualCenter\Logs) on the vCenter server.

Can you have a look at them and see if you can find any errors relating to the clone task, and post back anything that you find.

Hope this helps

Adam

[Francisco317]

Thanks Adam.

I attached the logs, but there is nothing that really stands out other than:

error 'App' opID=EA9A638D-0000007F] Error occured while creating deploy package. Msg: oobeSystem.Microsoft-Windows-Shell-Setup.UserAccounts.AdministratorPassword.EncryptedValue

(Template) Unexpected exception (vim.fault.CustomizationFault) during clone. Aborting.

I've tried with a blank password and with a password, but it fails either way.

[WaffleSniffer]

Hi

Thanks for uploading the log, and yeah, I agree the only really interresting lines are the one you mentioned, and it does seem to be related to the password, or at least the the way sysprep uses it...

I did notice that you seem to have upped the logging level on your vCenter to verbose. Is there any chance you could crank up the logging to trivia and repeat the process, to see if it gives us a little more insight... naturally, turn the logging down again afterwards

Sorry i've not been much help, but from the research i've done, you certainly are not alone!

Cheers

Adam

[Francisco317]

Thanks again for looking. I attached the logs with trivia enabled, but I don't see anything.

[Rimtuuk]

Have you tried to sysprep the server and then clone it? I have not used the new sysprep yet but in the older version you always had the option of shutting the machine down after you sysprep it and then you could clone the machine. If it works you could do it as a work around until you have a resolution for your problem.

[llueder]

I realize this is an old post but I ran into the same problem. This fix worked for me:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103206...

If the disk is full on your vCenter server, it will exhibit the same symptom. In my case, the disk was not full but filled during the deployment. Furthermore, our %TEMP% variable pointed to D:\, so it was not immediately obvious where the problem existed.