After deploying a new VCSA 6.0u1 I was seeing some weird errors while trying to retrieve AD- users/groups (or anything from the esod.local domain):
VMUG Denmark is arranging the Nordic VMUG UserCon in Copenhagen December 1st 2015, and the agenda went live earlier today. I’m definitely going to be there, and as it turns out I even have my own session lined up:
This is a guest post from Kristian Wæraas
Senior Consultant Datacenter at Datametrix AS
VMware VCP3/5, MCTS Hyper-V, Horizon View and Trend Micro Security Expert.
I am a curious by nature, and when my colleagues start talking frantic about some system that has crashed, I get curious and have to ask questions. Usually this ends up in me doing a lot of work.
- This, however, was not one of those times.
During an upgrade from vSphere 5.1 to 5.5, I ran into a rather strange issue when trying to utilize VMware Update Manager to perform the ESXi upgrade.
During scanning, VUM reported the ESXi host as «Incompatible», without offering any other explanation. I spent ages looking through VUM logs, trying to find the culprit, suspecting it was an incompatible VIB. Without finding anything that gave me any indication on what the problem might be, I moved on to looking at the ESXi image I had imported into VUM.
The ESXi Embedded Host Client Fling got an upgrade today, and in addition to new features it now works properly on ESXi 5.5. In addition to this, it’s also available as an offline bundle so you can distribute it with Update Manager.
Since I’ve spent most of my day in esxcli, here is a quick post on how to perform the upgrade from a local http repository hosting the .vib file.
I was recently involved with consulting for a Norwegian shipping company who has quite a few remote vSphere installations, most of them with a couple of ESXi hosts, but no vCenter and hence no Update Manager. While looking at methods for managing these installations, in particular how to facilitate patching and upgrading scenarios, I remembered that way back in 2013, I posted Quick and Dirty HTTP-based Deployment which shows how to use the Python to run a simple http daemon, and serve files from it.
This is a guest post from Shane Williford
Sr. Systems Engineer, VCAP-DCA/EMCCAe/Pizza Connoisseur and vExpert.
Problem History
I work at a school district in the US (Kansas City area). After the school year ended, my Director decided he wanted to upgrade to vSphere6 from vSphere55U2 on a few Hosts we were using with XenApp. We are using XenApp to deliver apps to student labs that utilize an Autocad program. As such, our Hosts also have a graphics card in them – nVIDIA GRID K1. To give the students a bit more graphics power this upcoming school year, we added a 2nd nVIDIA card to each Host. The Hosts are HP Proliant DL380p Gen8 with Intel Xeon X5650 2.67GHz processors and about 296GB RAM. Since we added a 2nd nVIDIA card, we also needed to upgrade the Host power supplies to support the 2 cards’ power consumption (1200W support).
I almost choked on my coffee this morning when I saw William Lam announcing a new VMware Fling called ESXi Embedded Host Client. Finally the day when we can get a local vSphere Web Client on a standalone host is here, and it’s not a moment too soon. This feature has been missing since ESX 3 and it’s VMware Infrastructure Web Access. For now, this is a Fling (which means unsupported and so on), but I really hope that this ends up being built-in to ESXi very soon – even on the free vSphere Hypervisor.
Veeam has been «silently» working on their own global influencer program, and the inaugural list of Veeam Vanguards was published today. I am thrilled to be selected amongst the first 31 people awarded this title, it’s quite an exclusive list!
Sponsors
