Make sure you have XCode installed on your computer.If you are running OS X 10.6, you should download and run XCode 3.2.
In v Sphere 6.0 the VMCA (VMware Certificate Authority) was introduced.But everything should work fine if the steps above have been followed exactly. All you have to do next is paste this command: Note: When I first started to write this article, I was going to use Fink, however, it appears they dropped the package.So I opted for Mac Ports which is the most recently updated and compatible. What this means: Eventually, everyone who is accustomed to Putty will need to change directions indefinitely, so please take a look at Daniel’s post on Terminal in OS X.Select ‘Base 64 encoded‘ and then hit ‘Download certificate chain‘. Open a Command Prompt to the location you exported the above certificates.You will be prompted to download and save a certnew.p7b file. Open the certnew.p7b file in Windows and drill down to the Certificates container. Next we need to concatenate them into a single certificate chain, with the new VMCA on top, followed by the Intermediate CA, followed by the Root CA. If you have closed this, return to the certificate-manager by running /usr/lib/vmware-vmca/bin/certificate-manager Select Option 2, then Option 1 2.The Certificate-Manager will then replace the VMCA with your new Subordinate CA certificate and replace the certificates on the PSC (MACHINE_SSL_CERT, machine and vsphere-webclient solution user certificates) It will also update the relevant service endpoints with the new MACHINE_SSL_CERT.
Lastly it will restart all the services on the PSC.
When utilizing Mac Ports, you can find that there are thousands of programs you can run on your Mac that normally wouldn’t be available.
The interfaces may feel or act a bit differently, but it’s better than not having them at all.
Same as the Machine_SSL_CERT in the previous step, provide the FQDN for the ‘Hostname‘ field.
For the ‘Name‘ field use the format that the subject information of all solution user certificates in this environment are kept unique. If this was a v Center Server with Embedded PSC there would be two more solution user configuration files to configure in the same manner; vpxd and vpxd-extension.
If your v Center Server is External then proceed to the next section. Provide the [email protected] credentials 6. Since this is a v Center Server with an external PSC you will be asked to provide the IP Address of the PSC. Similar to before, we will be asked to configure the configuration file for MACHINE_SSL_CERT.