vSphere 5.5 QuickTip: Upgrading vCenter 5.1 to vCenter 5.5

Last modified date

Comments: 0

it-crowd-unexpectedSo I did my upgrade of my new environment and began using Chrome (native Mac Browser) to access vCenter. As I was doing was I was being innodated with “Unable to create the managed object for ” kinds of errors. I thought at first it was a browser issue so I tried Safari and Firefox.

Still didn’t work.

So I tried it on the native system and noticed that the error propagates there as well. A quick search internally I found a similar, yet different issue that suggested a restart of services might solve that issue. That got me thinking. Sometimes a reboot (or “forcing an unexpected reboot”) can solve some issues (e.g., clears out the cache, restarts services properly, etc.).

Eh. What could it hurt? At worse, I’d do a fresh install. At best, it’d solve stuff.

Turns out, it was the “at best” situation. Horizon View 5.2, although no official sanction is out yet for support (assume that Horizon View 5.2 and vSphere 5.5 are “unsupported”; that means best effort — usually — from GSS for tickets) Horizon View seems ok with the upgrade. I’ve yet to test whether Composer will like it (that’s next). And I still need to upgrade my MacMinis themselves.

Oh. Joy.

Oh, where to begin? Let's see.. I lived in the US for 13 years (3 years in NYC and 10 years in Los Angeles area). I'm a huge MMORPG fan (I've been a die-hard World of Warcraft player since mid-2007 -- For the Horde!). And have numerous tattoos, including one about VMware and one about Warcraft. I enjoy the occasional cigar with a single malt (for a while, I even had a cigar aficionado blog). I used to enjoy long distance solo cycling and am hoping to restart it here in Nova Scotia. I live just outside of Halifax, Nova Scotia with my wife, our 3 cats and our Golden Retriever.

I'd love to hear from y'all. Leave me a message or comment!

%d bloggers like this: