After you install vCenter Server, consider these postinstallation options before adding inventory for the vCenter Server to manage.

Install the vSphere Client and make sure that you can access the vCenter Server instance.

Check the license server configuration. A license server is required if this vCenter Server is managing ESX 3.5/ESXi 3.5 hosts. See Using a License Server to Manage Version 3.5 ESX or ESXi Hosts.

When vCenter Server and the database are installed on the same machine, after you reboot the machine, you might need to restart the VMware VirtualCenter Management Webservices service. See VMware vCenter Management Webservices Service Fails to Start.

For the Oracle Instant client, copy ojdbc14.jar to the vCenter Server tomcat directory vCenter install location\Infrastructure\tomcat\lib.

The Oracle 10g client and Oracle 11g client include ojdbc14.jar at: Install location\oracle\product\10.2.0\instance_name\jdbc\lib or Install location\app\Administrator\product\11.1.0\instance_name\sqldeveloper\jdbc\lib. The vCenter Server installer copies the file from the Oracle client installation location to the vCenter Server tomcat directory vCenter install location\Infrastructure\tomcat\lib.

If the ojdbc14.jar file is not found in the Oracle 10g or Oracle 11g client location, the vCenter Server installer prompts you to copy the file manually. You can download the file from the Oracle.com Web site. At the time of this topic's publication, the file was available at http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc101040.html.

For environments that require strong security, VMware recommends that you replace the default certificates on your vCenter Server system with certificates signed by a commercial Certificate Authority (CA). See the information on increasing security for session information in the vSphere Examples and Scenarios documentation.