VMware vCenter Server 5.5.0a update released

VMware

VMware has released an update to vCenter 5.5 Server. The new updated, numbered 5.5.0a doesn’t appear to add any new features but instead focus on squishing a number of bugs in the 5.5 version – mostly around vCenter Single-Sign-On and the vSphere web client.

Issues resolved with this release are as follows:

  1. Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
  2. Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
  3. Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
  4. VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables

  1. Attempts to search the inventory in vCenter Server using vSphere Web Client with proper permissions might fail to return any results
  2. vCenter Server 5.5 might fail to start after a vCenter Single Sign-On Server reboot
  3. Unable to log in to vCenter Server Appliance 5.5 using domain credentials in vSphere Web Client with proper permission when the authenticated user is associated with a group name containing parentheses
  4. Active Directory group users unable to log in to the vCenter Inventory Service 5.5 with vCenter Single Sign-On
  5. Attempts to log in to vCenter Single Sign-On and vCenter Server might fail when there are multiple users with the same common name in the OpenLDAP directory service
  6. Attempts to log in to vCenter Single Sign-On and vCenter Server might fail for OpenLDAP 2.4 directory service users who have attributes with multiple values attached to their account
  7. Attempts to Log in to vCenter Server might fail for an OpenLDAP user whose account is not configured with a universally unique identifier (UUID)
  8. Unable to add an Open LDAP provider as an identity source if the Base DN does not contain an “dc=” attribute
  9. Active Directory authentication fails when vCenter Single Sign-On 5.5 runs on Windows Server 2012 and the AD Domain Controller is also on Windows Server 2012

The full release notes can be found here and the download is available now from VMware.

Similar Posts

  • Backup and Restore VMware VCSA 6.5

    VMware
    0 Comments

    With the release of vSphere 6.5, the VCSA has had a built-in and convenient way easily backup the configuration, inventory and even historical data right from the VAMI and directly into a TAR bundle. VMware has also made restoring the VCSA from a backup just as easy as well.

    Below are quick and dirty steps to backing up and restoring your VMware VCSA!

    Read More “Backup and Restore VMware VCSA 6.5”

  • VMware ESXi 5 home lab upgrade

    Home Lab, VMware
    54 Comments

    In the past I’ve been using a single server to run my VMware ESXi home lab. it was slow, old, big and loud. I’ve been meaning to upgrade my home lab for a while and just never got around to it, until now! When looking for new hardware I wanted the servers to be as compact as possible, quiet, and low energy usage as possible while still having some horsepower.

    I debated on going the whitebox solution as I build all my own desktops anyway, I also looked at several other solutions such as the HP ML310e server, Shuttle XH61V barebones machine, but ultimately decided to go with two Intel NUC i5’s.

    Intel NUC i5 and 16GB ram

    Intel NUC i5 DC53427HYE Features:

    • Uses very little energy
    • Completely quiet
    • Supports up to 16GB RAM
    • A dual core CPU that scores nearly 3,600 in PassMark benchmarking
    • Includes vPro which allows me to easily run both NUC’s headless
    • Extremely small, nearly 4 1/2″ inch square footprint

    Read More “VMware ESXi 5 home lab upgrade”

  • Thank you VMware Community!

    VMware
    0 Comments

    VMware vExpert 2014

    So far, 2014 has been a very rewarding year for a number of reasons, two of which has happened in just a week or two span. First, Eric Siebert (@ericsiebert) announced on March 27th, this years results of the 2014 Top VMware & Virtualization Blog voting. My first year entered into voting and made it to 71st place! A huge thanks goes out to not only Eric but just as much so to everyone who voted for me!

    To top it off, yesterday VMware announced 2014’s first quarter VMware vExpert list. While vExpert isn’t a technical certification or even a general measure of VMware expertise. The VMware judges selected people who were engaged with their community and who had developed a substantial personal platform of influence in those communities. There were a lot of very smart, very accomplished people, even VCDXs, that weren’t named as vExpert this year. VMware awarded this title to 754 people this year and on that list of many impressive names you’ll find yours truly, Michael Tabor!

    I’m both honored and humbled by both lists. It’s a great feeling to be recognized by not only my peers through the voting in the Top vBlog but also by VMware themselves through the vExpert title.

    So again THANK YOU very much to the entire VMware community, a spectacular community indeed, and congratulations to everyone else that made the Top vBlog and vExpert lists!

  • VMware Update Manager U3e upgrade failing? Un-install it!

    VMware
    0 Comments

    VMware Update Manager U3e error

    I was recently upgrading a VMware environment from vCenter Server Update 3b to Update 3e and during the scheduled change I had also planned on upgrading VMware Update Manager to Update 3e and ran into the following error:

    VMware Workstation unrecoverable error: (vthread-3)
    GetProcAddress: Failed to resolve ENGINE)load_aesni: 127
    You can request support.

    Looking for a possible solution at the VMware Knowledge Base came back with no results and to error message wasn’t overly useful either with “VMware Workstation unrecoverable error: (vthread-3)” as Workstation wasn’t installed on this server.

    Read More “VMware Update Manager U3e upgrade failing? Un-install it!”

  • Shrink a thin provisioned VMDK disk

    VMware
    8 Comments

    When maintaining a Horizon View environment I like to keep my parent images as small as possible and over time a thin provision disk can start to grow on you if you don’t watch it – be it from downloading installers, updates, or even running disk defrag. While there isn’t a simple, one click button in the View Administrator Console there is a fairly easy manual method using vmfkstools.

    Before we can use “vmkfstools” to shrink the VMDK file we must zero out any unused space on the thin provisioned disk. A simple way of doing this is by using a free utility called SDelete from Sysinternals.

    Read More “Shrink a thin provisioned VMDK disk”

Leave a Reply

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