Join our VMware Hands-on Labs Online Workshop on Tuesday, March 25th 10:00 AM PDT.
In our vSphere with Operations Management 101 online workshop, you will learn first-hand how vCenter Operations Manager can help you manage your vSphere environments. We will walk you through the steps to access the live vCenter Operations labs. Using the Hands-on Labs online portal you will be able try vCenter Operations Manager and chat with our VMware experts who use this product to monitor the Hands-on Labs infrastructure. Attend this online workshop to see how vCenter Operations Manager provides comprehensive visibility into the health and performance of your vSphere environments, helps you improve the efficiency of your virtual infrastructure, increase your consolidation ratios, and how it provides capacity management with “what if” planning capabilities.
This online workshop is targeted at customers who are running vSphere and who are new to vSphere with Operations Management.
Date: March 25th
Time: 10:00 AM PDT
Length: 1 Hour Register
I’ve had a number of requests for recommendations on the “best way” to restrict access to the ESXi host console. While this is easily done using the ESXi Lockdown Mode feature I’m finding there are some admins who are still under the impression that lockdown mode doesn’t work, and in order to prevent access to the host console you need to disable the console service. While there were some challenges with lockdown mode in the past, things changed in ESXi 5.1.
I’m often asked if you can use vCenter Server Heartbeat to protect the Auto Deploy Server. The answer is yes and I’m happy to announce that we now have some videos and product walkthroughs that show how this is done.
To view the product walkthrough visit http://vmwarewalkthroughs.com and select the recently added vCenter Server Heartbeat section. Here you will see the walkthrough showing how to use vCenter Server Heartbeat to protect your Auto Deploy server.
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”.