Search the VMware Knowledge Base (KB)
View by Article ID

Installing vCenter Server 5.5 on a Microsoft Windows platform (2058274)

  • 3 Ratings

Purpose

This article provides a step-by-step guidance for installing vCenter Server using the Custom Install method.
 
This article assumes that:

Important: Having the services located on multiple Microsoft Windows servers increases the complexity of maintaining the environment. Additional complexity comes in the form of administration overhead and licensing costs. In addition, this configuration introduces points of failure, such as network connectivity and name resolution related issues which may involve engaging additional vendors during outages and maintenance windows. Please make sure that your infrastructure is configured in a redundant manner and you allocate appropriate resources considering these factors.

Resolution

Installation steps for vCenter Server 5.5

  1. Mount the vSphere 5.5 installation media. The installation wizard appears.
  2. In the left pane, under Custom Install, click vCenter Server and then click Install.

    Note: If any of the prerequisites are not met, they are listed in the right pane under Prerequisites.

  3. Select the appropriate language from the dropdown and click OK.
  4. In the welcome screen, click Next.
  5. Review the End User License Agreement. If you agree, select the I accept the terms in the license agreement option, and click Next.
  6. In the license key screen, enter your license key and then click Next
  7. Click Yes to proceed.

    Note: You can view your license keys in My VMware. For more information, see Viewing license keys in My VMware (2006831). If you do not enter a license key, you can proceed with a 60 Day Evaluation license and you see a popup, which prompts you to acknowledge that you are proceeding without a license. 

  8. Select the database solution for vCenter Server and then click Next.

    You can use one of these options for the database:
     
    • Install a Microsoft SQL Server 2008 Express instance.
    • Use an existing supported database.

      To use an existing supported database, select the Data Source Name (DSN) from the dropdown.

      Note: For information about specific database versions and service pack configurations supported with vCenter Server 5.5, see the VMware Product Interoperability Matrixes.

  9. Select the user type that the vCenter Server should run with and click Next. You can use one of these options:
     
    • Use Windows Local System Account
    • Use an alternate account

  10. Choose how you want to use vCenter Server. You can use one of these options:
    • Create a standalone VMware vCenter Server Instance.
    • Join a VMware vCenter Server group using Linked Mode to share information. You may receive a warning indicating that the alternate vCenter Server must be version vCenter Server 5.1 or later.

      Enter the Fully Qualified Domain Name (FQDN) for the alternative vCenter Server, with which you are attempting to use Linked Mode, along with the LDAP port.

      Note:
      By default, the LDAP port is 389.

  11. Optionally, provide an alternative TCP port number for the VMware VirtualCenter Server service and click Next.

    Note:
    • To check for available port numbers, run the netstat -a command in an elevated command line. 
    • Changing the default ports is recommended only if you have an unchangeable port conflict on the same system.

  12. Optionally, select the Increase the number of available ephemeral ports option and click Next.
  13. Select one of these inventory sizes, depending on environmental requirements:

    • Small (less than 100 hosts or 1000 virtual machines)
    • Medium (100-400 hosts or 1000-4000 virtual machines)
    • Large (more than 400 hosts or 4000 virtual machines)

  14. Click Next.
  15. Enter the SSO Lookup Service URL and SSO administrator username and password. You may be prompted to install the Lookup Service Certificate.

    Notes:
    • This dialog shows information related to a domain by the name vsphere.local. This is not a domain that is auto-detected within the existing environment, but a net new domain used internally by vSphere. The administrator@vsphere.local account performs the same function as the admin@System-Domain account in previous versions of vSphere.

      For more information about the administrator@vsphere.local account, see the vSphere Software Components section of the vCenter Server and Host Management Guide.

    • You must use the Fully Qualified Domain Name (FQDN) and not the IP address.  Providing the IP address may allow you to proceed with the upgrade, but may result in certificate related errors when starting vCenter Server. 

    • If you are configuring a HA SSO configuration, you must provide the FQDN of the load balancer. Providing the FQDN of a single node may allow you to proceed with the upgrade, but may result in certificate related errors when starting vCenter Server. 

  16. Click Next.
  17. Enter the SSO administrator user or group and click Next.

    Note: By default, this value is the administrator@vsphere.local user. The only time this value may be changed is when you have made modifications to the SSO service before installing vCenter Server.

  18. In the dialog that appears, check if the Fully Qualified Domain Name (FQDN) of the vCenter Inventory Service URL and port number are displayed. These fields are auto-populated.

    Notes:
    • If the FQDN is not auto-populated, enter the FQDN manually.
    • The default port is 10443.

  19. Click Next.
  20. Optionally, provide an alternative installation location and then click Next.

    Notes:
    • The installation path of vCenter Server must be compatible with the installation requirements for Microsoft Active Directory Application Mode (ADAM/AD LDS). The installation path cannot contain non-ASCII characters, commas (,), periods (.), exclamation marks (!), pound signs (#), at signs (@), or percentage signs (%).

    • The path must conform to NTFS naming restrictions.  For more information, see the Microsoft TechNet article Naming Files, Paths, and Namespaces.

    • The installation requires 4 GB of disk space to be available. For more information, see the Hardware Requirement for vCenter Server, the vSphere Web Client, vCenter Inventory Service, and vCenter Single Sign-On section in the vSphere Installation and Setup Guide.

  21. In the Ready to Install screen, click Install to start the installation.
  22. When the installation completes, click Finish.

Post installation of vCenter Server 5.5

After installing vCenter Server 5.5:

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 3 Ratings
Actions
KB: