Below is a list of new features in vCenter Server 5.0
Next-generation browser-based vSphere Client.
A browser-based, fully-extensible, platform-independent implementation of the vSphere Client based on Adobe Flex. The vSphere 5.0 release includes both the new browser-based client and the Windows-based client available in prior releases. In this release, the browser-based client includes a subset of the functionality available in the Windows-based client, primarily related to inventory display and virtual machine deployment and configuration.
vCenter Server Appliance.
A vCenter Server implementation running on a pre-configured Linux-based virtual appliance. This appliance significantly reduces the time required to deploy vCenter Server and associated services and provides a low-cost alternative to the traditional Windows-based vCenter Server.
The vCenter Server Appliance has the following limitations:-
- No Update Manager
- No Linked-Mode
- No support for the VSA (vSphere Storage Appliance)
- Only support for Oracle as the external database
- Embedded database, DB2, only supports 5 hosts and 50 VMs
- No support for vCenter Heartbeat
VMware customers and partners can extend vCenter Server in multiple ways, including the inventory, graphical user interface, and agents. vCenter Server includes a manager to monitor the extensions. By deploying extensions created by VMware partners, you can use vCenter Server as a unified console to manage your virtualized datacenter.
Solution Installation and Management.
The vCenter Solutions Manager provides a consistent interface to configure and monitor vCenter-integrated solutions developed by VMware and third parties. It provides a simpler installation, configuration, and monitoring interface for managing solutions. Using the new vSphere ESX Agent Manager, you can deploy, update, and monitor vSphere agents on ESXi hosts. vSphere agents inter-operate efficiently with other vSphere features such as maintenance mode and distributed power management.
Enhanced logging support.
vSphere 5.0 adds several enhancements to system message logging. All log messages are now generated by syslog, and messages can now be logged on either local and/or one or more remote log servers. A given server can log messages from more than one host. Log messages can be remotely logged using either the Secure Sockets Layer (SSL) or TCP connections. The vSphere syslog listener is available as an optional plug-in to vCenter on Windows; in the vCenter Virtual Appliance (VCVA), logging is accomplished using the native syslog-ng facility. With vSphere 5.0, log messages from different sources can be configured to go into different logs for more convenience. Configuration of message logging can also be accomplished using ESXCLI in addition to the vSphere client.