Hi,
> Key CUSTOMIZATIONINFO was not found in the config map
Is not an error, it's a warning which indicates that you run without pre-/post-customization script.
> I have been using the SetpComplete.cmd trick to get this working.
In VCD 5.1 (and previous ones) there is a number of unpleasant limitations with regards to joining domain. In 5.1 GA (and previous ones) networking configuration is always performed after sysprep tries to join the domain. The implication is that template NICs must be configured in such way that it's possible to join the domain without running VCD networking customization. This means:
1) for DHCP suggested DNS servers must be able to resolve domain name
2) for static provided manually DNS servers must be able to resolve domain name and static addresses must be valid for the connected VCD/VC network (network is already connected at the time VM is powered on)
To complicate things even more sysprep is known to reset NICs to DHCP automatically in some cases. This means that the only recommended approach for VCD 5.1 and before is 1), although 2) may randomly work for some templates.
Also I believe in VCD 5.1.1 there was a patch which additionally configures networking before running sysprep on Vista+ in order to allow for KMS activation to workaround "rearms" issue. That might help in some cases, but again approach 2) may not work.
I'm working on lifting these limitations, but I wouldn't expect that to be fixed in in 5.1.xxx releases since required changes are way too intrusive and require rewrites of some big parts of the current code.
/Andrii
