Our website use cookies to improve and personalize your experience and to display advertisements(if any). Our website may also include cookies from third parties like Google Adsense, Google Analytics, Youtube. By using the website, you consent to the use of cookies. .

vCenter Server 5.5 – Update 2d

VMware have just released an update to its vCenter Server.

vCenter Server 5.5 Update 2d – Build 2442329
vCenter Server 5.5 Update 2d Installation Package – Build 2442328
vCenter Server Appliance 5.5 Update 2d – Build 2442330

Please make sure to review the release notes and download from vmware.com

While this is a minor release it does resolve many issues previously experienced as summarized here:

vCenter Single Sign-On

  • VMware Directory Service consumes excessive memory
  • Backup and restore of vCenter Single Sign-On database might not replicate the data between primary and secondary nodes correctly
  • Attempts to logout through the vCloud Automation Center UI might fail

Networking

  • Network Interface Cards of virtual machines in disconnected state might get ejected during vMotion
  • vCenter Server, vSphere Client, and vSphere Web Access
  • Virtual machines on ESXi hosts containing NSX Endpoint virtual machines might not power on
  • Update to SUSE Linux Enterprise Edition Server in vCenter Server Appliance to address time zone changes
  • vpxd reports massive logging
  • Accessing the Storage View tab fails with the error
  • Scheduled tasks cannot be created for a different time on the same day in vSphere Web Client
  • The VMware VirtualCenter Server service fails intermittently
  • HTML console cannot be launched with custom port
  • Datastore browser in vSphere Web Client does not overwrite existing files
  • VMware VirtualCenter Server service fails

Virtual Machine Management

  • Cloning or deploying deploying virtual machines over the network causes performance degradation
  • Alert event is not triggered when one VM has multiple vNICs with same MAC address

vMotion and Storage vMotion

  • The default behavior of DRS has been changed to make the feature less aggressive during cluster upgrade

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Related Posts