We experienced this issue with the template deployment with the custom specification wizard. The important thing here is we experienced this issue soon after the vSphere 6.5 upgrade. Our Virtual Machine deployment team reached us to find a solution after the upgrade.
Previously, they were using the old C# client to deploy the Virtual Machines and with the change of the vCenter this issue came in to the action. I thought to write this post to share and explain the findings and the steps to resolve the issue.
First thing first what are the permission levels required?
Below permission levels should be fulfilled to use the custom specifications for a Role.
Virtual Machine -> Provisioning -> Read Customization Specifications
Virtual Machine -> Provisioning -> Modify Customization Specifications
Also, the created or role that these provisioning users are sitting at should be applied to the vCenter level, it was added to the Datacenter level and I had to change it to the vCenter level as shown in the below screen capture
After that our provisioning engineers were able to see the custom spec scripts
Still not finished…..
“The public key in the specification does not match the vCenter public key. You have to reenter the password in order to proceed”
This error appeared after fixing the above issue
So we had to update the passwords of the templates, follow below steps to update the template passwords
Click on the “Home” icon and select the “Policies and Profiles”
Select the “Customization Specification Manager” and select the template and click on “Edit” icon
Select the “Administrator Password” and update it in the wizard
Click “OK” to complete the change
After that we were able to use the Customization Specification scripts without any issues
If you found this post as useful please rate the post and share it!