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.
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 →
As many of you know, I work very closely with VMware Product Management and Engineering and we are always looking for data points to support concepts and aid the development of future generations with our products. We have created a 3 page survey that covers Performance and Availability within vCenter Server environments.
Help us make our products better by spending a few minutes to complete, your participation is much appreciated.
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.
VMware vSphere Mobile Watchlist allows you to monitor the virtual machines you care about in your vSphere infrastructure remotely on your phone. Discover diagnostic information about any alerts on your VMs using VMware Knowledge Base Articles and the web. Remediate problems from your phone by using power operations or delegate the problem to someone on your team back at the datacenter.
IMPORTANT NOTE: A VMware vSphere installation (5.0 and above) is required to use VMware vSphere Mobile Watchlist. Access to your vSphere infrastructure may need a secure access method like VPN. Contact your IT department for further assistance.
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 →