The exact error I get when I attempt to deploy a template is "The virtualcenter server is unable to decrypt passwords stored in the customization specification."
I have found previous mention that when you uninstall VC and then reinstall it you can no longer use old customization specifications. I have done this, but I have since DELETED all old specs.
I cannot even deploy a template with brand new customization settings (although I am assuming it saves those settings to a temp file for sysprep to use). Have I fubarred myself completely by previously uninstalling VC server?
Any help is appreciated. Thanks!
I opened a support call for the client where I am working at about this problem. VMware couldn't understand why I am having this problem until today. They had to export the customization template, which exports to an XML file. Then they had me edit line 719 which read this:
They had me switch the false to true and then re-import the xml file back into VirtualCenter. About 15 minutes later I was able to deploy a template into a virtual machine. They also told me that they are continuing to research the problem for more a clearly picture in why this is happenning. I also told them that also when I choose the second option during the deployment of the template virtual machine that I get the same result error with the decrypt passwords. The engineer said that he hopes to get back to me by the end of the week. With keep you posted. But give the replacement of the false to true a shot and hopefully it will fix your problem too.
In my case, this issue was caused by a SQL problem.
One of the sample databases (tempdb on SQL2005) grew to all the available space on OS volume (the default installed databases were installed on C). This caused SQL to partially stop functioning.
After shrinking the tempdb database and rebooting, template deployment started working again. After that, I moved tempdb to a larger volume and set up a maintenance plan to make sure it doesn't happen again. If you get this error, you might verify that everything is ok with the database that your VC uses.
I didn't update my post.
The workaround i use is to export the customization template:
where you can change Password01 to your needs.
This error comes up random. On some sites it works oke and some it don't.
And how do you go about doing an export/import?
Go to Edit | Customization Specifications
Right-click the template desired and select export.
Save-As whatever you want.
To Import, click the Import button at the top of the Customization Spec. Mgr.
I ran into this issue with saved customizations and templates also.
I tried a few things including:
1. Delete the customization having the issue
2. Recreated the customization from scratch (did not resolve the problem)
3. Delete the customization again
4. Deploy the template using the customization wizard only (not using a stored customization). The issue still happened.
5. Create another customization
6. Follow the export/import procedure. Resolved the problem.
This will need to be resolved. Saving Windows infrastructure passwords via the export/import procedure in clear text isn't good.
This appears to be permanently broken in VirtualCenter 2.5 Update 1. None of the methods above allows me to deploy a template with a stored customization. I even tried to deploy a template creating a new customization on the fly, and that does not work either. At this point I cannot deploy a template with any customization. This one is bad news.
I jsut started getting this error after updating the default VC certificate last night to use one produced by our CA.
ONe workaround would be to sysprep the image manually, power off and then convert to a template. Then the password is stored in the sysprep.inf file on the image. Just make sure the runonce command deleted the sysprep.inf file to delete the trace.
Is there any permanent solution to this error:
virtualcenter server is unable to decrypt passwords stored in the customization specification
Or I did not notice it here?
Manual change password in the cust xml file to plain text works, but it is a bodge IMHO