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.
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.
A minor update to the vCenter Server 5.5 has been released
VMware vCenter Server™ 5.5.0a | 31 OCT 2013 | Build 1378901
vCenter Server Appliance 5.5.0a | 31 OCT 2013 | Build 1398493
Issues resolved with this release are as follows
Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables
Attempts to search the inventory in vCenter Server using vSphere Web Client with proper permissions might fail to return any results
vCenter Server 5.5 might fail to start after a vCenter Single Sign-On Server reboot
Unable to log in to vCenter Server Appliance 5.5 using domain credentials in vSphere Web Client with proper permission when the authenticated user is associated with a group name containing parentheses
Active Directory group users unable to log in to the vCenter Inventory Service 5.5 with vCenter Single Sign-On
Attempts to log in to vCenter Single Sign-On and vCenter Server might fail when there are multiple users with the same common name in the OpenLDAP directory service
Attempts to log in to vCenter Single Sign-On and vCenter Server might fail for OpenLDAP 2.4 directory service users who have attributes with multiple values attached to their account
Attempts to Log in to vCenter Server might fail for an OpenLDAP user whose account is not configured with a universally unique identifier (UUID)
Unable to add an Open LDAP provider as an identity source if the Base DN does not contain an “dc=” attribute
Active Directory authentication fails when vCenter Single Sign-On 5.5 runs on Windows Server 2012 and the AD Domain Controller is also on Windows Server 2012
The realese notes can be found here with full details, download now from www.vmware.com
I was a little surprised how quickly these went live but can now share the VMworld vCenter Deep Dive and vSphere Upgrade series: Part 1 – vCenter Server breakout sessions from last weeks VMworld in Barcelona where my sessions were recorded and are now available for your viewing pleasure.
With the announcement at VMworld on the upcoming vSphere 5.5 release, one area that I have been greatly involved with (hence why I have been in stealth mode), has been the new and improved vCenter Single Sign-On. You may still say why do we need it? and why change something that wasn’t broke to begin with! but hang in there and let me highlight the changes and the benefits you will see as you begin to look at vCenter Server 5.5.
With the new release, this shows we heard you loud and clear! vCenter Single Sign-On 5.1 at release lacked some expected functionality (limited Active Directory integration), complex to manage (SSL Certificates) as well as lack of guidance on how to best deploy vCenter Single Sign-On. Not to knock the current version with vCenter Server 5.1 Update 1b which is now a very stable platform to build on and guidance available via a recent deployment whitepaper, vCenter Single Sign-On 5.5 builds on these challenges and now provides a rich and fully capable vSphere authentication experience with much of the complexity removed.
VMware vCenter Multi-Hypervisor Manager is a component that enables support for heterogeneous hypervisors in a VMware vCenter Server environment. It provides the following benefits to your virtual environment:
An integrated platform for managing VMware and third-party hypervisors from a single interface.
A hypervisor choice for the different business units in your organization to accommodate their specific needs.
No single hypervisor vendor lock-in.
When you add a third-party host to vCenter Server, all virtual machines that exist on the host are discovered automatically, and are added to the third-party hosts inventory.
The ability of vCenter Multi-Hypervisor Manager to migrate virtual machines from third-party hosts to ESX or ESXi hosts is implemented by exposing the capabilities of vCenter Converter Standalone in the vSphere Client. See VMware KB article 2048927 for information about dependency between vCenter Multi-Hypervisor Manager and vCenter Converter Standalone.
vCenter Multi-Hypervisor Manager 1.1 introduces the following set of basic management capabilities over third-party hosts:
Third-party host management including add, remove, connect, disconnect, and view the host configuration.
Ability to migrate virtual machines from third-party hosts to ESX or ESXi hosts.
Ability to provision virtual machines on third-party hosts.
Ability to edit virtual machine settings.
Integrated vCenter Server authorization mechanism across ESX/ESXi and third-party hosts inventories for privileges, roles, and users.
Automatic discovery of pre-existing third-party virtual machines
Ability to perform power operations with hosts and virtual machines.
Ability to connect and disconnect DVD, CD-ROM, and floppy drives and images to install operating systems.