Dec 15, 2013 Is the vSphere 5.5 client I can download from an ESXi 5.5 host compatible with Windows 8 and Windows 8.1? There is just one vsphere client. It is not not released per OS. This Post is purely to easy of vSphere Admins who want to download the VMware vSphere Client. I have athered the Download link of all versions of vSphere Client starting from vSphere Client v4.1 Update 1 to the latest release vSphere Client 6.0 Update 3.
![]()
What's in the Release NotesThe release notes cover the following topics:What's New
vCenter Server 5.5 Update 3g addresses issues that have been documented in the Resolved Issues section.
The update from vCenter Server 5.5 Update 3f to vCenter Server 5.5 Update 3g affects only vCenter Server and VMware vCenter Inventory Service.
Earlier Releases of vCenter Server 5.5
Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 5.5 are:
Internationalization
VMware vSphere 5.5 is available in the following languages:
Compatibility and InstallationESXi, vCenter Server, and vSphere Web Client Version Compatibility
The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.
The vSphere Client and the vSphere Web Client are packaged on the vCenter Server ISO. You can install one or both clients by using the VMware vCenter™ Installer wizard.
vSphere Client Connections to Linked Mode Environments with vCenter Server 5.x
vCenter Server 5.5 can exist in Linked Mode only with other instances of vCenter Server 5.5.
Guest Operating System Customization Support
The Guest OS Customization Support Matrix provides details about the guest operating systems supported for customization.
Installation Notes for This ReleaseRead the vSphere Installation and Setup documentation for guidance about installing and configuring vCenter Server.![]()
Although the installations are straightforward, several subsequent configuration steps are essential. Read the following documentation:
Upgrades for This Release
For instructions about upgrading vCenter Server, see the vSphere Upgrade documentation.
For more information about the sequence in which vSphere environments need to be updated, see KB 2057795.
Open Source Components for VMware vSphere 5.5
The copyright statements and licenses applicable to the open source software components distributed in vSphere 5.5 are available at http://www.vmware.com/download/vsphere/open_source.html, on the Open Source tab. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of vSphere.
Product Support Notices
Resolved Issues
The resolved issues are grouped as follows.
Security Issues
Known Issues from Earlier Releases
To view a list of previous known issues, click here.
The earlier known issues are grouped as follows.
Installation and Upgrade
After upgrading to vCenter Server 5.5 Update 2d from earlier versions of vCenter Server 5.5, attempts to log in to the vSphere Web Client on vCenter Virtual Appliance fail with an error
After you upgrade to vCenter Server 5.5 Update 2d from earlier versions of vCenter Server 5.5, attempts to log in to the vSphere Web Client on the vCenter Virtual Appliance fail with the following error message: Failed to connect to VMware Lookup Service <address> - SSL certificate verification failed. Automatic regeneration of the SSL certificate does not resolve the problem. Workaround: To resolve this issue, open a Secure Shell (SSH) connection to the vCenter Virtual Appliance and run the following commands to forcibly regenerate the vCenter Server and the vCenter Single Sign-On certificates:
Workaround: If you install the new versions of vCenter Server and vCenter Heartbeat instead of performing an upgrade, the second node starts up as expected.
If Single Sign-On must be upgraded rather that a fresh install on a different virtual machine, follow the procedures listed in KB 2059820.
If Active Directory services and vCenter services are in different locations, a login by a user who belongs to over 500 groups might take a long time
Your environment uses an Active Directory setup. This setup is in a different location from vCenter Server and its services. As a result, when a user who belongs to over 500 Active Directory groups logs in with the vSphere Web Client, login might take 10-20 minutes. With the vSphere Client, login for that user might time out.
Workaround: Change your setup so the Active Directory services and the vCenter Server system are in the same location, or log in as a user who does not belong to so many Active Directory groups.
Auto-discovery of Active Directory settings no longer supported with vCenter Single Sign-On 5.5
The vSphere 5.1 vCenter Single Sign-On version included an autodiscovery feature. That feature was removed from the vSphere 5.5 vCenter Single Sign-On service.
Workaround: Log in to vCenter Single Sign-On from the vSphere Web Client as a user with vCenter Single Sign-On administrator privileges and add the identity source manually. By default, [email protected] has vCenter Single Sign-On administrator privileges.
After upgrade, domain administrators, who are part of the local administrators group, cannot log in to vCenter Server
In your vSphere 5.1 environment, you gave permissions to the local administrators group, which implicitly includes the domain administrator group. You can log in to vCenter Server 5.1 as a member of the domain administrator group. However, when you upgrade to vSphere 5.5, the domain administrator users no longer have the permissions to log in to vCenter Server. Permissions for local users are maintained after the upgrade.
Workaround: The simplest solution is to log in to vCenter Server as [email protected] and to assign permissions directly to the domain administrators group. If other local users who were not inside a subdomain had permissions to manage to vCenter Server users before the upgrade, those users can also log in to vCenter Server and assign permissions to the domain administrators group or any other group.
vCenter Single Sign-On installation fails on Windows Server 2008 SP1
When you attempt to install vCenter Single Sign-On on Windows 2008 SP1 (64 bit), the following warning appears: This application is only supported on windows server 2008 64bit, or higher. Make sure windows is not running as domain controller. Installation does not complete.
Workaround: None. Install vCenter Single Sign-On on a Windows 2008 SP2 (64 bit) or higher system.
No error occurs when you replace the certificate for a service with a certificate already in use by a different service
If you are using the Certificate Automation Tool to replace certificates, and you respond to the prompts by replacing an existing certificate with a certificate that is already in use by a different service, the tool does not display an error message. The tool proceeds with the replacement. Because each service must have a unique certificate in the vCenter installation on Windows, authentication does not work properly.
Workaround: None. Keep track of the certificates that you are using for the different services.
Login with vCenter Single Sign-On might require inclusion of domain name
In vSphere 5.5, vCenter Single Sign-On no longer supports multiple default domains. This might cause problems for users who attempt to log in to a vCenter Server system that is installed on Windows, or for users who log in to the vCenter Server Appliance.
Workaround: Include the domain prefix with the user name when you log in to a nondefault domain. For example, the user root on the local operating system can log in as localosroot. The user user1 in the domain DOMAIN1 can log in as DOMAIN1user1.
This behavior is not considered a bug, but included in the release notes for completeness.
vCenter Single Sign-On installation fails if the destination folder includes non-ASCII or high ASCII characters
If you change the destination folder for vCenter Single Sign-On during installation, and if the new destination folder that you select includes non-ASCII or high ASCII characters, no warning appears but installation fails.
Workaround: Select destination folders that contain ASCII characters. Special characters are not allowed and generate the error listed in the next known issue.
vCenter Single Sign-On fails if the installation folder includes special characters
If you attempt to install vCenter Single Sign-On in a custom location, and the destination folder name includes characters such as percent (%) or ampersand (&), the installation fails. An error message similar to the following appears: Error 20020. Failed to update values in server.xml file
Workaround: None. See the vSphere Installation and Setup documentation for a complete list of disallowed characters.
To collapse the list of previous known issues, click here.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |