vCloud guest customization does not work

[FAugust]

Hi

I#ve got the Problem that the settings (Guest Name, Domain, etc.) of a VM aren't changed during the Sysprep Stage. Also a forced customization has no effect.

The VM starts, is busy for a while and runs without any problems but with the same name like the template.

The last lines of the toolsDeployPkg.log file are:

Expanding C:\WINDOWS\TEMP\vmw2.tmp\sysprep\cloud-director\system\org\apache\httpcomponents\httpcore-osgi\4.0.1\httpcore-osgi-4.0.1.jar
Expanding C:\WINDOWS\TEMP\vmw2.tmp\sysprep\cloud-director\system\org\apache\httpcomponents\httpclient-osgi\4.0.1\httpclient-osgi-4.0.1.jar
Expanding C:\WINDOWS\TEMP\vmw2.tmp\sysprep\cloud-director\system\org\apache\servicemix\camel\apache-servicemix\${artifact.baseVersion}\apache-servicemix-${artifact.baseVersion}${dashClassifier?}.${artifact-features.extension}
FDICopy failed, error = 11
Caught runtime exception in DeployPkgDeployPackage: C:\WINDOWS\TEMP\vmw1.tmp
package deploy failed:
## Closing log

The guest VM is a WindowsXP x86.

Hope someone can give ma an advice of whats going wrong here.

[admin]

You might want to also check out customize-guest.log, ref http://kb.vmware.com/kb/1026317.

[FAugust]

Thanks for your advice but there is no such logfile. It will be created when sysprep runs but in this case it doesn't start.

Some files are copied to the C:\Windows\Temp subfolders but after a while the files and folders are deleted with no effect on the system.

I have tested the same with a Windows 2008R2 Server. This works fine.

Maybe ist a Problem with the deployment files that i took from the ISO. It's the same i used to install the Guest OS. Its Windows XP with integrated SP3.

Can someone send or post a complete toolsDeployPkg.log file  (WINXP sysprep) for research purposes? I want to see which files are extracted when the error occurs.

[FAugust]

Problem solved.

We run into the same problem like this case http://communities.vmware.com/thread/299527

We used CentOS 5.5 for evaluation purposes and it seems that this is no good idea to do this because CentOS doesn't create the sysprep package in the right way.

So we installed an evaluation version of Redhad Enterprise Linux 5 and build the sysprep files there. The file size here (3MB) differs from CentOS (aprox. 750MB).

The Sysprep of the XP templates worked like a charm. Then we copied the sysprep file from RHEL to CentOS and voila: all was fine.

So we will stick to RHEL for testing since it is the only supported OS.