Today VMware released Update 2 of its vSphere management solution, vCenter Server. In this release there are updates to the supported database versions and many resolved known issues.
vCenter Server database support: vCenter Server now supports the following external databases:
Oracle 12c. Important: For pre-requisite requirements, see KB 2079443.
Microsoft SQL Server 2012 Service Pack 1
Microsoft SQL Server 2014
vCloud Hybrid Service: The vCloud Hybrid Service (vCHS) introduces a new container, Hybrid Cloud Service, on the vSphere Web Client home page. The Hybrid Cloud Service container contains the vCHS installer and the new vCloud Connector installer.
Customer Experience Improvement Program: The vSphere customer experience improvement program is introduced to collect configuration data for vSphere and transmit weekly to VMware for analysis in understanding the usage and improving the product. For more details, see the vSphere Documentation Center.
If you are like me, VMworld 2014 in San Francisco left my brain on overload. With so many new product and services announcements, plus breakout sessions filled with technical information and demos in the expo floor booths, it’s hard not to feel like you are drinking from the proverbial fire hose. Throw in a party or three, plus the pile of work waiting when you get home and all that great info you gathered starts to turn up with some CRC errors in your memory.
Fortunately, VMware has a tool that you can use to refresh your memory on the VMware solutions and services that you explored at VMworld. The VMware Feature Walkthrough site (http://featurewalkthrough.vmware.com) provides technical overviews and step-by-step guidance for installing, configuring and managing our solutions. Each walkthrough includes screen shots with relevant steps highlighted and text explaining the process.
The Feature Walkthrough site is a great for stepping through a self-paced demo of a particular VMware product or feature. We’ve made the site mobile friendly, so go ahead and open it on your tablet and take it into the data center to guide your proof-of-concept install of the products you saw or heard about during VMworld, or to simply refresh your memory on just where exactly that checkbox to enable a product feature is. Use it to show your boss that cool feature you saw at VMworld, or to familiarize yourself with the basics of a product before you jump into a live Hands-on Lab environment.
One of the most repetitive questions that I get asked is which version of vCenter Server should I be using. This obviously is based on the decision between using the vCenter Server appliance (VCSA) introduced with vSphere 5.0 or the trusted and proven vCenter Server on Windows.
It has been general knowledge that the vCenter Server appliance, since its introduction has lacked features to that of its Windows counterpart. With vSphere 5.5 the vCenter Server appliance has come a long way, it supports all solutions that integrate with vCenter Server (vCD, vCOPs, SRM, VUM etc) but is it production ready? I can confidently say yes but will it meet your requirements? Continue reading →
Over the last few months, many customers have been testing and familiarizing themselves with vSphere 5.5 however deployment into a production environment is usually stalled until the availability of the first update or service pack. As we are nearing the typical time frame of when such an update or service pack may become available, I wanted to share some findings that may affect your deployment selection of vCenter Single Sign-On when deploying or upgrading to vCenter Server 5.5
During the installation of vCenter Single Sign-On server you are asked on the deployment option of the vCenter Single Sign-On instance. Below is the intended use case for each deployment option.
Many of you have now kicked the tires with vSphere 5.5 either in your home lab or on some servers at work and you're anxious to get all the new goodies running in your production environment. Perhaps some of you early adopters are already running in full production, but we're guessing many of you are just contemplating your major upgrade now.
VMware's Tech Support staff tend to see a surge during the month of March in number of calls to support. But guess what? Many of the issues we're anticipating are already resolved, and we've been busy compiling and documenting solutions to common problems that you can handle yourself.
Those of you installing or upgrading your vSphere hosts, and vCenter Server instances to version 5.5 will find the following KB articles and Support Insider posts of great interest.
You have probably heard the terms “Big Data” and “Hadoop” mentioned somewhere in the industry lately – they are both very popular subjects of discussion at the moment. This blog gives you an introduction to the core technology and explains some of the contributions that VMware continues to make to the Hadoop world.
While VMware highly recommends the deployment of all vCenter Server components into a single virtual machine (excluding the vCenter Server database), large enterprise customers running multiple vCenter Server instances within a single physical location can simplify the vCenter Single Sign-On architecture and management by reducing the footprint and required resources and specify a dedicated vCenter Single Sign-On environment for all local resources in each physical location.
For vSphere 5.5 the VMware recommendation is to centralize vCenter Single Sign-On when you have 8 or more vCenter Server instances in a given location (this is a soft recommendation).
Centralized vCenter Single Sign-On Architecture
Figure 1: A Centralized vCenter Single Sign-On Server environment
There can be increased risk when centralizing a vCenter Single Sign-On server (to why it is not recommended for smaller environments) due to the increased number of components affected if the vCenter Single-Sign-On server was to become unavailable, in short all vCenter Server components of all vCenter Servers registered will incur authentication loss (when compared to just the single vCenter Server instance when installed locally) and so availability of the vCenter Single Sign-On centralized server(s) is highly recommended. Continue reading →