Select the Run this program in compatibility mode for option. Note: Usually, the installer is named as VMware-viclient.exe. Note - I know that these spec's are not recommended by Microsoft to run a production Exchange server. Right-click the vSphere Client installer and click the Compatibility tab. Now with that out of the way, lets get started:
It will bypass the operating system check and the thing will just install and work perfectly. You may use the flag /VSKIPOSCHECKS'1' to bypass this check. Well, okay, but I want to do that anyway. vSphere Client cannot be installed on a Domain Controller. the moral of the story here is to make sure that you are mindful of what you are working on and do not touch what is not yours. vsphere Client requires Windows XP SP2 or later. Now what we are working on here should not be disruptive to the rest of the ecosystem but you never know.
Things to consider before proceeding is that this is a preexisting lab environment that has a lot of things going on. I will be doing this in a series with the end goal of having Microsoft Exchange 2013 SP1 installed and running in my Lab environment. In this post I will go over the process of creating a new Virtual Machine (VM) in with VMware vSphere 5.5 in my lab environment. You can find the complete list of operating system supported by vSphere Web Client in the VMware Compatibility Guide.
On Windows XP or Windows Server 2003, the vSphere Client and vSphere PowerCLI do not use strong cipher suites to connect with vCenter Server. vSphere Web Client: Starting with vSphere 5.5 Update 2, Windows XP and Windows Vista are not supported as vSphere Client Operating System. When I open a console window via the C Windows based client, and then I minimize either of the VMs, I cannot activate them or bring them back up from the taskbar. In VMware vCenter Server 5.1 and 5.5, virtual machines can only be created with hardware version 9 and 10 from the vSphere Web Client. Ive created a Windows 7 and XP VM for testing. For example, you cannot manage, modify or create VMs with Virtual hardware 13 (vSphere 6.5) with vSphere Client 6.0 or you cannot manage virtual hardware 10 (vSphere 5.5) with vSphere client 5.1.
I am pretty new to the game but I figured that starting with a how to guide may be beneficial to others as well as a great way to track all of the things I have worked on. In the release notes of vSphere 5.5 this is a known issue: vSphere 5.5 uses the Open SSL library, which, for security, is configured by default to accept only connections that use strong cipher suites. This is for Windows XP and 7 that Ive noticed so far.
Greetings all, this will be my very first technical blog post.