I have a vCloud Director 5.5 instance set up with one cell. I've created a catalog which holds several vApps, each containing a single Windows VM. The versions of Windows captured in these vApp Templates are Windows XP, Windows 7, Server 2008, and Server 2012. Everything appears to be working fine up until I begin to deploy new vApps from the ones in my catalog. The VM builds and launches with no problem and from what I can tell, the IP address and hostname are being changed to what I specified in the vCloud Director UI so some customization is taking place. However, the system SID isn't being changed and I'm not seeing Sysprep being fired off at all to customize my deployments making them unique. This problem is compounded by the fact that I've got a SetupComplete.cmd script in my %windir%\Setup\Scripts\ directory which has some post customization things that I'm expecting to run. With no Sysprep being run, I'm not getting my scripts to fire off either.
For further information, Guest Customization is selected, and Change SID is also selected for every vApp Template captured to the Catalog. Additionally, the necessary Sysprep files for my VX and 2003 deployments have been placed on by vCloud server under /opt/vmware/vcloud-director/guestcustomization/default/windows/sysprep
Does anyone have any idea why this might be happening or how I can ensure that my VMs are being customized properly when deployed?