however what I found is that it never uses the customization when it deploys from the template. does it work for y'all? if you delpoy from the template, then customize.. when the VM fires up does it go through the customization process? it doesn't for me. it did before my upgrade to VC 2.5

thank you

I had to convert my template to a VM, upgrade the VMTOOLS, then convert it back to a template. then when I powered it on it sat at the login screen for about 2 min. then rebooted and did the sysprep wizard.

For example:

You have a native language installation. Win2003 SP1 GERMAN

and you are using the standard Virtual Center installation. This is the english Version.

THEN your PATH NEED to look like this:

<ALL USERS>\Application Data\VMware\VMware VirtualCenter\sysprep\<os>

means for this GERMAN case

C:\Dokumente und Einstellungen\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\svr2003

be carefull the Folder Application Data remains english. IT IS NOT "Anwendungsdaten".

Hope this helps.

Regards,

Using this path "C:\Dokumente und Einstellungen\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\svr2003"the VC did NOT offer me the customisation options.

Using the path "C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\VMware\VMware VirtualCenter\sysprep\svr2003" i can initiate the guest-customisation.

First test is running and i'll report the result.

regards