I found the answer to my own question. Here it is If anyone else needs to know.
1. Change directories to /etc/vmware/ssl
2. Create backups of any existing certificates by executing the
mv rui.crt orig.rui.crt
mv rui.key orig.rui.key
3. Enter the following command to restart the vmware-hostd
service mgmt-vmware restart
4. Confirm that the ESX Server host generated new certificates by
executing the following command comparing the time stamps of
the new certificate files with orig.rui.crt and orig.rui.key:
This seems to work for me.
it should be noted that (at least on my 3.5 server) restarting the mgmt-vmware service also restarts all the running VMs.
I am running VC 2.5.0 update 1 and stille get error in my logs when performing p2v import:
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs prd-vc.xx.xx.coma
I notice the certificate on VC 3.5.x is issued to vmware by vmware and this is not the VC server name?
I am still looking for answer.