ForwardOrReverse

The scripted install fails and the installer reports that it can not find some package files. The files were extracted from an ISO that was verified using md5sum.
When I extracted the files from the ISO image using MagicISO or DaemonTools on Windows a few of the files have invalid names. It looks just fine when I mount the ISO in my Ubuntu Linux VM though. I burnt the ISO to a disk and the same files have incorrect names.

Here are the files I had problems with, both wrong names and correct names:

VMware\RPMS\
VMware-esx-drivers-scsi-aacraid_esx30-350.1.1.5.2vmw-82663.i386
VMware-esx-drivers-scsi-aacraid_esx30-350.1.1.5.2vmw-82663.i386.rpm
VMware-esx-drivers-scsi-lpfc_elx_v740-350.7.4.0.13.1-82663.i386
VMware-esx-drivers-scsi-lpfc_elx_v740-350.7.4.0.13.1-82663.i386.rpm
VMware-esx-drivers-scsi-qla2300-v707_vmw-350.7.8.32-82663.i386.r
VMware-esx-drivers-scsi-qla2300-v707_vmw-350.7.8.32-82663.i386.rpm
VMware-esx-drivers-scsi-mptscsi_2xx-350.2.6.48.13vmw-82663.i386
VMware-esx-drivers-scsi-mptscsi_2xx-350.2.6.48.13vmw-82663.i386.rpm

Looks like this is a known VMware issue. The message towards the end of this forum post provides more information.http://communities.vmware.com/thread/139118

We upgraded to Virtual Center 2.5 and our XP deployments failed to join the domain. When I logged onto the VM I received a popup about an unsigned driver issue for the network card. Turns out a patch to the network driver in ESX 3.0.1 updated the driver to version 2.0.0.9 and there was a version of it in C:\WINDOWS\system32\ReinstallBackups. ESX 3.0.2 has a version of 2.0.0.8 so it looks like the problem was resolved within ESX itself.

I am not sure what changed in the deployment process for this issue to show itself after a VC upgrade, but here is what I did to resolve the issue in the template.

1. Convert to virtual machine
2. Power on
3. Uninstall VMware tools and reboot
4. Dismiss hardware dialogs
5. Delete the VMware driver folders in C:\WINDOWS\system32\ReinstallBackups
6. Delete lgotsync, vmmouse, vmx_svga, and vmxnet from windows\system32\drivers
7. Search for driver files in other locations and delete them
8. Reboot
9. Install the current VMware tools
10. Reboot
11. Configure display settings
12. Shutdown
13. Convert to template