May be because you have different passwords?
I've never done it but I think you must deal with this links:
Thanx.. for the tips..
in fact i have a clustered VC2 installation .. and i also changed my SSL certificates on the virtual center 2 server.. maybe this is causing my strange error message.. didn't think about that until now..
i will investigate and post the results..
I found the solution..
The customization specification uses the original SSL certificates of Virtual Center 2.
When you change them to trust your Microsoft CA, you cannot use your customization specifications anymore. probably to get this working, you should also replace the ESX host SSL certificates..
Is there somebody who also replaced the SSL certificates and get template deployment working with customization specification?
How can i get template deployment working with customization specification without changing back the original SSL certificates
I'm just installed new environment of VirtualCenter 2.5 with 2 ESX's 3.5 for testing this new product and i have been meet this issue too
I'm never change the SSL so its look like the SSL on this issue is not relevant (anyway for this test)
This is really big problem for me cause i working with this feature a lot on are production environment and i can't upgrate until VMware will fix this issue
So if the customization specification working for anybady on 2.5 please tell us here and please describe how
Thanks in advance
Well after delete and recreate the customization specification template its working so thanks anyway
But i have not test it with new SSL yet
I had this same error and fixed it by editing the template in VC and
supplying the administrator password. I edited the template in the Customization Manager. I was then able to deploy using
this template. I did the same for another and that also worked