Although the vCenter Converter installs SSL certificates by default, for better security you can replace these certificates with your own ones. If you want to improve the security of the Converter client – server communication, you need to install the SSL certificates on the Converter server. If you want to improve the security of the Converter server – agent communication, you need to install the SSL certificates on the Converter agent. You can create, sign, and install your own certificates, or you can use certificates issued by commercial CA (Certificate Authorities), such as Thawte or VeriSign.
If you have no certificates issued by a trusted CA, you need to create a new SSL certificate signed by a local CA and then install the CA for Converter server and agent services on the corresponding machines.
For more information about using openssl for generating a local CA and to find a sample openssl.cnf configuration, read the Replacing vCenter Server Certificates guide.
NOTE: When you install SSL certificate on a Converter server, the certificate's “Common name” attribute must match the DNS or the IP (depends which you use for connection) of the host, on which the Converter server is installed. If you want to install the SSL certificate on a Converter agent, the certificate’s “Common name” attribute must match the DNS or the IP of the host, on which the Converter agent is installed.
NOTE: For post Vista operating systems, the VMware folder is located directly under %ALLUSERSPROFILE%.
If you have installed certificates for vCenter Converter Standalone agent, you must be able to perform remote hot-clone of that machine without seeing a warning for a SSL certificate error in the Source Machine page of the Convert Machine wizard.