Despite VMware’s stride to push for the adoption of vCenter Server Appliance (vCSA) instead of its Windows-based twin, the latter is still an integral part of vSphere 6.5. In this short how-to post, I’ll guide you through the steps required to install the latest incarnation of vCenter. To keep matters simple, I went for an embedded Platform Services Controller and PostgreSQL database solution. This setup will suffice for most SMBs out there. Broadly speaking, most SMB VMware based environment will fall under the Tiny or Small categories as per VMware’s literature.
VSphere Web Client has always been intended to be the replacement for the Desktop client, and many of our users have tried to embrace this during the vSphere 5.5 and vSphere 6.0 periods, spending their time working within the Web Client even with the Desktop client available.
The table shows the different types of environments, their respective capacity in terms of the number of ESXi hosts and deployed VMs and the compute resources that need to be allocated to vCenter Server.
Type | ESXi Hosts | VMs | VC RAM (GB) | VC CPUs |
Tiny | 10 | 100 | 10 | 2 |
Small | 100 | 1000 | 16 | 4 |
Medium | 400 | 4000 | 24 | 8 |
Large | 1000 | 10000 | 32 | 16 |
X-Large | 2000 | 35,0000 | 48 | 24 |
Note: vCenter Server for Windows 6.5 runs on Windows Server 2008 SP2 or better. As per earlier versions, installing vCenter on an Active Directory Domain Controller IS NOT supported.
A complete list of requirements is available on the VMware vSphere 6.5 documentation site.
Download Altaro VM Backup Ea koetting wiki.
Start your free 30-day trial of Altaro VM Backup today and see why it's trusted by 40 000+ organizations worldwide. Get started now and run your first backup in under 15 mins!
Getting on with the installation
Step 1: Prepare a VM or physical server. The specifications should reflect the environment you expect to be managing. Remember to allocate at least 10GB of RAM, 2 CPUs and 17GB of disk space over and above what’s required for the Windows OS and other installed software. Also keep in mind that in time, the vCenter database will grow in size, so factor in this as well when allocating disk capacity.
Step 2: Decide on a hostname for vCenter (ex. vcw65). Create the corresponding A and PTR records on a DNS server and make sure that the records resolve correctly.
Figure 1 – Creating the DNS records for the vCenter Server for Windows instance
Step 3: Install Windows Server as you would normally do. After the install, apply all pending updates and patches.
Step 4: Make sure the Windows computer name matches the vCenter hostname i.e. vcw65. Reboot the server.
Figure 2 – Setting the vCenter Server Windows computer name
Step 5:Download the latest vCenter Server 6.5 ISO from my.vmware.com.
Step 6: When deploying vCenter to a VM, you can mount the ISO image as a DVD drive directly from a datastore or from local disk. If a physical machine is used instead, you can copy the ISO image to a folder on the Windows server and then mount it as a drive from the OS itself; right-click on the file and mount!
Figure 3 – Mount the ISO image on a VM from a local disk
Step 7: Login as administrator on the Windows box.
Step 8: Double-click on the DVD drive just mounted. This launches the VMware vCenter Installer.
Figure 4 – The mounted ISO image in Windows Explorer
Vsphere Client 6.5 Windows 7 64 Bit Download
Step 9: From here on, the installer takes you through a series of screens and options, most of which are self-explanatory. Regardless, I listed the whole lot in a sequential order each accompanied by a brief note as follows.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The process is 100% identical to installing vCenter Server 6.0 for Windows as described in my somewhat old post How to set up a nested vSphere 6 nested environment. So really, very little has changed from an installation perspective. Under the hood, however, there have been some changes as explained here.
Conclusion
Installing vCenter Server 6.5 for Windows is pretty straightforward provided you prepare the groundwork first. Compared to earlier versions, very little has changed except that vCenter is now a little bit more resource hungry. The thick (C#) vSphere client is, officially, no longer supported. This means that getting used to the vSphere Web client (or HTML5 client) is no longer optional.
I would also have loved to see the Web client laid to rest once and for all but since its new HTML5 alternative is still not up to par, I guess we will all have to wait until vSphere 7 is released!
UPDATE: vSphere 6.5 U1 has recently been released. It brings the HMTL5 client almost up to par with the vSphere Web client in terms of functionality. Read about it here.
The vSphere Web Client lets you connect to a vCenter Server system to manage an ESXi host through a browser.
If an earlier version of the vSphere Web Client is installed, this procedure upgrades the vSphere Web Client.
vCenter Server 5.1 supports connection between vCenter Server and vCenter Server components by IP address only if the IP address is IPV4-compliant. To connect to a vCenter Server system in an IPv6 environment, you must use the fully qualified domain name (FQDN) or host name of the vCenter Server. The best practice is to use the FQDN, which works in all cases, instead of the IP address, which can change if assigned by DHCP.
Prerequisites
■ | Verify that the system has an Internet connection. |
Verify that the system meets the software requirements for the vSphere Web Client. See vSphere Client and vSphere Web Client Software Requirements. | |
■ | Before you install or upgrade any vSphere product, synchronize the clocks of all machines on the vSphere network. See Synchronizing Clocks on the vSphere Network. |
Install vCenter Single Sign On, or upgrade to the current version. | |
■ | Verify that the vSphere Web Client and vCenter Server are registered to the same vCenter Single Sign On server, to ensure that the vSphere Web Client can access the vCenter Server inventory. |
Close all browsers before installing or uninstalling the vSphere Web Client. | |
■ | Log in as a member of the Administrators group on the host machine, with a user name that does not contain any non-ASCII characters. |
If you are upgrading the vSphere Web Client, and you plan to use it with any version 5.0.x vCenter Server instance that was registered to a version 5.0 vSphere Web Client without accepting the SSL thumbprint, see Version 5.1 vSphere Web Client Fails to Connect to Version 5.0.x vCenter Server. |
Procedure
Vmware Vsphere 6.5 Client Windows
2 | Select VMware vSphere®Web Client and click Install. |
Follow the prompts in the installation wizard to choose the installer language, and agree to the end user patent and license agreements. | |
4 | Accept or change the default port settings. |
Enter the information to register the vSphere Web Client with vCenter Single Sign On. The vCenter Single Sign On administrator user name is admin@System-Domain, and the password must match the password you entered for the administrator user when you installed vCenter Single Sign On. The Lookup Service URL takes the form https://SSO_host_FQDN_or_IP:7444/lookupservice/sdk, where 7444 is the default vCenter Single Sign On HTTPS port number. Your entry should match the entry you made when you installed vCenter Single Sign On. If you entered a different port number when you installed vCenter Single Sign On, use that port number. | |
6 | Click Install. |
Start the vSphere Web Client by doing one of the following actions. | In a browser, go to https://vSphere_Web_Client_host_name_or_IP:9443/vsphere-client. |
From the Windows Start menu, select Programs > VMWare > VMware vSphere Web Client > vSphere Web Client. |