Well, today the support request came back. Seems one of the originally linked VMTN dicussions really is the only way:
- Export the customization specification
- Edit the XML file
- Import it again
The related part inside the customization specification should then look like this:
|
1 2 3 4 |
<type>vim.vm.customization.Password</type> <plainText>true</plainText> <value>Password01</value> </password> |
So if you ever think about switching the default VirtualCenter certificate (for whatever reason), make sure you use the above workaround. Otherwise VirtualCenter is gonna fail miserably during the customization phase of the cloning process.