After an upgrade from 6.5 to 6.7U3 we're unable to create any customizations, they all fail in the HTML5 UI with the following error:
vim.fault.NotFound
Looking in /var/log/vmware/vpxd/vpxd.log there's the following error:
Method vim.CustomizationSpecManager.GetEncryptionKey threw undeclared fault of type vim.fault.NotFound
Comparing the MOB entries for CustomizationSpecManager with another linked vSphere server I can see that the working server has an entry for encryptionKey, but the broken server just has "unset" against it.
Does anybody known if having encryptionKey under CustomizationSpecManager unset is normal or not?
If it's not normal, any idea how to fix it? (I've tried multiple reboots of VCSA and cert regeneration via UI and certificate-manager).
If it is normal, any ideas how I can fix the issue of creating Windows Customizations?
I'm assuming that the reason this only affects Windows customizations is that there's no stored password for a Linux customization so no need to access the missing public key.