Notice that the interoperability matrix shows support based on the ESX/ESXi version that is providing the tools. This is different from how the virtual machines report their VMware Tools versions. The virtual machines lists their tools version as a four-digit number which has no correlation with the corresponding ESX/ESXi host version:
Updated based on feedback. Thanks for the comments!
I’d like to revisit the question “are ESXi patches cumulative”? This time I hope to hammer home the point with an example.
In short, the answer is yes, the ESXi patch bundles are cumulative. However, when applying patches from the command line using the ESXCLI command you do need to be careful to ensure you update the complete image profile and not just select VIBs.
There are two ways to update VIBs using the ESCLI command. You can use either the “esxcli software vib update …“ command or the “esxcli software profile update …” command. The “vib” namespace is typically used with the optional “-n <vib name>” parameter in order to update individual VIBs, where the “profile” namespace is typically used to update the host’s image profile, which may include multiple VIB updates. The key is when applying patches use the “profile” namespace to update the complete image profile opposed to using the “vib” namespace to update selected VIBs.
vCenter Server Appliance 5.5.0a | 31 OCT 2013 | Build 1398493
Last week, along with the rest of you, I learned about an authentication issue with vSphere Single Sign-On version 5.5 when running both the Active Directory (AD) domain control and the vCenter Single Sign-On Server on Windows Server 2012 (http://kb.vmware.com/kb/2060901).
In a nutshell, when your AD domain controller and your vCenter Single Sign-On are both running on Windows Server 2012, the single sign-on is unable to authenticate AD users. You get a “Cannot parse group information” error:
I was testing vSphere 5.5 upgrades in my lab and came across an interesting situation that you need to be aware of. In a nutshell, pay attention to how your Active Directory groups are configured on your vCenter Server and avoid nesting any domain level user or group accounts inside of local groups.
Here’s the situation I ran into. My lab was running a vanilla vCenter 5.1 install. In vCenter I only had one permission assigned, which is for the local “Administrators” group.
I recently posted a summary of the new features and capabilities available in vSphere 5.5 and I want to follow that with a summary of the new features and capabilities available in vCloud Director 5.5.
However, before we talk about what’s new in vCloud Director 5.5 I recommend you first read Mike Adams recent post discussing the new vCD product strategy that was announced at VMworld 2013. This post has some important information that everyone working with vCloud Director should be aware of.
With that, I’m excited to announce these new vCloud Director features as there are some very cool new capabilities being introduced with the 5.5 release. I want to stress that this list is just a summary. For additional information be sure to check out the new VMware Mobile Knowledge Portal iPad app where you will find several recorded demos that show most of these features in action. In addition there are also some nice click-through demos available online. Both the Mobile Knowledge Portal app and click-through demos were created by VMware’s Technical Marketing Group and provide a wealth of information not just on vCloud Director but the entire vCloud Suite. We’re actively working to add more content so even if you’ve played with it in the past, be sure to revisit and check out the recent additions.
On August 26th at VMworld 2013 VMware announced vSphere 5.5, the latest release of VMware’s industry-leading virtualization platform. This latest release includes a lot of improvements and many new features and capabilities. In an effort to try and get my head around all this exciting new “stuff” I decided to go through the what’s new paper and compile a brief summary (well, relatively brief anyway).
Here’s the list I came up with. I’m sure I missed some things, but this list should help you get started with learning about what’s new in vSphere 5.5.
After upgrading a vSphere host from ESXi 5.0 to ESXi 5.1u1 I attempted to create an new host profile and was surprised when it failed with the error: “Firewall rule activeDirectoryAll must be enabled for the service lwiod”.
If you are an experienced vSphere admin then this post may not be for you. However, if you are new or just getting started on your journey to virtualization and vSphere with Operations Management (VSOM) then please keep reading…
I was once asked: “Explain how a brand new admin who wanted to install vSphere with Operations Management (VSOM) for the first time would go about doing that?”. While my initial thought was “Ah, that’s easy!”, in trying to answer this question it occurred to me that it’s actually quite involved, especially when you are new. You would need to do some research to understand the components, in the course of this research you would come across many new terms and acronyms and several different installation guides. Bottom line, a lot of time would be spent trying to figure out what the pieces are and how they fit together, and this is all before you install the first component.
This got me thinking about the challenges new IT professionals face and how it can be difficult having to sift through the vast amount of data trying to get answers to even the simple questions.
It’s in this spirit that we have created a new video series entitled “Getting Started – vSphere with Operations Management”. These videos are aimed specifically at helping new IT professionals get started with VSOM. The series starts by introducing you to the principals of virtualization and then guide you through the process of installing and configuring each VSOM component. The aim is to to help you spend less time researching and more time doing. These videos are basic, the goal was simple – to provide a series of introductory videos targeted at people who are new to vSphere in order to help get them through the initial learning curve. Continue reading →
I’ve been asked several times if there is a way to get a host profile to stop prompting for MAC addresses. This is actually pretty easy, although arguably not very intuitive. Lets start with a quick example showing a host profile prompting for MAC addresses: