Came across this article in the EMC KB-- and was very helpful in getting a vCenter server added in to the RecoverPoint Management Application. I was receiving errors that it was using the "wrong port"-- despite the fact I knew it was using 443.

I even went so far as to verify it on the server via netstat, and with Wireshark. Then I found this (step 4 is the key):

<!--more-->
<ol>
	<li>Validate RPA can ping VC IP</li>
	<li>Validate VC can ping RPA Cluster IP</li>
	<li>Validate VC is listening on port 443 ( netstat -an | find "443")

Note  : Use 'boxmgmt' user to run commands from following menu options :

**  Main Menu **
[2] Setup
[8] Advanced options
[6] System internal  operations
[2] Run internal command
This is the list of commands you are  allowed to use: switch_utils <strong>netstat</strong> ethtool date telnet  <strong>ping</strong> ssh top
Enter internal command:</li>
	<li>Using this secure connection you must use the Virtual Center (VC)  certificate which can be found in the following directory on the Virtual Center  server:

<strong>C:Documents and SettingsAll UsersApplication  DataVMwareVMware VirtualCenterSSLrui.crt
</strong>
Copy this to a  location on the PC that you are running the RecoverPoint GUI and vCenter Server  install from.

NOTE: This location maybe different on Windows 2008 server  and you will need to search accordingly for the certificate file.</li>
	<li>Using the RecoverPoint Console, right-click <strong>vCenter  Servers</strong>, select <strong>Add vCenter Server  credentials</strong>.

Under Credentials :
Server IP :  &lt;  Note : this is the Virtual Center IP address and not an ESX  IP &gt;
Port number : 443
Username : &lt;User must be  able to login to VC&gt;
Password :
Certificate files:  &lt;rui.crt from step 4&gt;</li>
</ol>
In my case the path was not as listed in Step 4, but I was able to track the cert down regardless.