VMware vCenter Server 4.1 update 1 build 345043

[arjanhs]

Virtualisatie heeft de laatste jaren een prominente plek veroverd. Bekende namen zijn onder andere Xen en VMware. Het laatstgenoemde bedrijf heeft met zijn vSphere 4 een stevig platform in handen. Een belangrijk onderdeel van dat platform is VMware vCenter Server, waarmee een complete virtuele omgeving kan worden beheerd. Voor meer informatie verwijzen we jullie door naar deze pagina. De ontwikkelaars hebben een nieuwe versie vrijgegeven met ditmaal 4.1 update 1 build 345043 als de versieaanduiding. De lijst met veranderingen ziet er als volgt uit:

    What's New

    This release of VMware vCenter Server 4.1 Update 1 offers the following improvements:

        * Additional Guest Operating System Customization Support: vCenter Server now supports customization of the following guest operating systems:
              o Windows 7 SP1 (x32 and x64)
              o Windows Server 2008 R2 SP1 (x32 and x64)
              o RHEL 6.0 (x32 and x64)
              o RHEL5.5 (x32 and x64)
        * Additional vCenter Server Database Support: vCenter Server now supports the following databases:
              o Microsoft SQL Server 2008 R2
              o Microsoft SQL Server 2005 SP3
              o Oracle 11g Standard/Enterprise Release 2, 11.2.0.1.0 or later, (x32 and x64)
              o IBM DB2 9.7.2 Express C (x32 and x64)
              o IBM DB2 9.7.2 Enterprise (x32 and x64)
                For more information about using IBM DB2 - 9.7.2 database with vCenter Server 4.1 Update 1, see KB 1033201.

    Resolved Issues

    Licensing

        * Cannot view the licensing usage reports with the Licensing Reporting Manager

    Miscellaneous

        * vCenter Orchestrator client executable file is not available in the vSphere 4.1 installation DVD or ISO image
        * Searching for Users and Groups in a large environment when using Add Permission wizard results in error or incomplete result
        * VMware Update Manager logs are not collected when generating vCenter Server logs
        * vCenter Server 4.1 reports redundant errors when HA and DRS are enabled

    Security

        * JRE updated to version 1.6.0_21, which addresses multiple security issues that existed in earlier releases
        * Tomcat updated to version 6.0.28, which addresses multiple security issues that existed in earlier releases of Tomcat
        * Updates the OpenSSL package to OpenSSL 0.9.8n
        * vCenter Tomcat Management Application Credential Disclosure
        * Updates to the Microsoft SQL Server 2005 Express Edition package

    Server Configuration

        * vSphere Client reports incorrect host profile compliance while using the Advanced configuration option
        * Alarms for the compliance or non-compliance of ESX host profiles are not triggered

    Storage

        * Multipathing status for datastores that have fully redundant paths might be reported as having Partial/No Redundancy
        * vCenter Server reports errors while performing the Synchronizing host task

    Upgrade and Installation

        * Agent Pre-upgrade Check tool is unable to detect 64-bit ODBC DSNs
        * vCenter 4.1 Data Migration Tool might fail to back up or restore a database
        * Using the Data Migration Tool to upgrade from VirtualCenter 2.5 Update 6 to vCenter Server 4.1 causes Mulitpathing Status to display blank
        * After an upgrade to vCenter Server 4.1, vCenter Server fails to start and issues an error message
        * Agent Pre-Upgrade check tool consistently reports insufficient disk space for ESXi 3.x hosts
        * Installing or upgrading to vCenter Server 4.1 fails on a non-English MSSQL with the error: ODBC error 22007 (KB 1024737)
        * VMware VirtualCenter Server service fails after upgrading to vCenter Server 4.1 in an environment configured with Nexus 1000v (KB 1026009)
        * Upgrading to vCenter Server 4.1 fails with the error: Trigger, procedure or function created with PL/SQL compilation error (KB 1026331)
        * Upgrading a vCenter Server instance that is deployed with Microsoft SQL Server 2005 database might cause the transaction log file size to consume large amounts of disk storage space
        * Upgrading to vCenter 4.1 might fail when you use the Do not overwrite existing Database option during vCenter Server installation
        * VMware VirtualCenter Server service fails after upgrading to vCenter Server 4.1 (KB 1026688)
        * vCenter Server stops responding when alarm modules fail to perform correctly during database recovery

    vCenter Server, vSphere Client, and vSphere Web Access

        * vCenter Server alarm actions are triggered repeatedly even after the state of the alarm reverts to normal
        * Performance chart data for networking displays incorrect information
        * The locale subsystem repeatedly issues a warning message to the vpxd.log file when the correct localized string cannot be found
        * In vSphere Client, the percentage values displayed for memory usage counters of cluster entities are incorrect
        * When vCenter Server Linked Mode is configured and you log in using a domain account, hardware statuses of hosts are not displayed
        * Storage Monitoring Service synchronization fails when the data source name of the vCenter Server host ends with a space
        * Search functionality might not display results if you use vSphere Client 4.1 to access vCenter Server 4.0
        * A missing database index causes performance problems in vCenter Server
        * Using Remote Desktop Connections causes vSphere Client to fail on subsequent logins
        * Messages for Datastore usage on disk or Datastore Disk Overallocation alarms display metrics in kilobytes instead of percent
        * Attempts to use vSphere Client to set the memory size in MB for a virtual machine that supports hot-addition fail
        * VMware VirtualCenter Management Webservices (vws) fails to retrieve vCenter Service health status data
        * vCenter Server might fail when Distributed Power Management tries to put a host into standby mode
        * Replacing SSL certificates in vCenter Server with custom certificates generated using OpenSSL 1.0.0 or later causes Storage Monitoring Service to fail
        * Storage Monitoring Service synchronizations are erroneously sent as health status changed alarms
        * Virtual disk provisioning with scheduled Storage vMotion task fails
        * When vSphere Client 4.0 and 4.1 coexist on the same machine, modification of existing Enhanced vMotion Compatibility clusters by using vSphere Client 4.0 fails
        * When vCenter Server and vCenter Converter are installed on the same or different hosts, vCenter Server Status reports inaccurate health status (Red alert) for vCenter Converter
        * vCenter alarms are not triggered if another alarm on the same object is disabled
        * vCenter Server takes longer than expected to connect to a remote Oracle Database
        * After an upgrade to vCenter Server 4.1, vCenter Server fails in certain environments when you click Edit Settings on a virtual machine
        * vCenter Storage Monitoring plug-in might not get enabled if vSphere Client 4.1 is connected to vCenter Server 4.0
        * Storage Monitoring Service does not start when a LUN is visible to an ESX host over multiple protocols
        * On a virtual machine running in full-screen mode, the mouse does not function properly in the lower portion of the screen
        * Deploying large number of virtual machine by using Lab Manager API scripts might cause the VMware Agent Service to stop responding
        * Performance Overview charts fail to display data after change of time due to Daylight Saving
        * Performance Overview data might not display after upgrading to vCenter Server 4.1
        * Performance data might be missing for certain intervals after upgrading to vCenter Server 4.1

    Virtual Machine Management

        * The default vCenter Server alarm for virtual machine total disk latency does not function on vCenter Server 4.0 and vCenter Server 4.1
        * Reconfiguring a virtual machine after adding a virtual hard disk might cause vCenter Server to stop responding
        * On vCenter Server, guest heartbeat status of a powered-on virtual machine fluctuates from green to either yellow or red

    VMware High Availability and Fault Tolerance

        * ESXi 4.0 host configures HA but displays an error after upgrading to vCenter Server 4.1 (KB 1027628)
        * When configuring high availability (HA) on a cluster, an error appears and HA does not configure on ESXi 4.0 and later hosts

Website   VMware
Download    http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vsphere_4/4_0