VMware vCenter Configuration Manager Release Notes
What's in the Release NotesThe release notes cover the following topics:
This release integrates VCM compliance monitoring with vCenter Operations Manager and provides VMware Level 1 and Level 2 support for international markets. In addition, this release allows you to activate VCM with vCloud and vCenter Operations suite license keys, and includes improvements in the areas of reporting, assessment downloads, and vCenter collections.
Compliance Integration with vCenter Operations Manager
VCM now sends compliance information about your virtual infrastructure and guest operating systems to vCenter Operations Manager.
VCM adds a Compliance sub-badge under Risk and dashboard to vCenter Operations Manager so that your configuration compliance posture is now combined with your capacity information to form the overall risk assessment of your virtual environment. Included with the dashboard are links that launch VCM in context to the compliance template and detailed compliance results that are in question. After you access VCM, you can understand what is affecting your posture and take action, for example by creating an exception or correcting the conditions that placed the system out of compliance. Multiple compliance standards have templates that are supported for mapping into vCenter Operations Manager. These include virtual objects such as vCenter Server, hosts, virtual machines, and guest operating systems that run on the virtual machines.
In vCenter Operations Manager, VCM machine groups now appear in the navigation tree on the left as part of the new capability for custom grouping and sharing context between the two products.
VMware Level 1: This version of VCM runs on non-English operating systems, and it can support non-English input and output characters.
VMware Level 2: This version of VCM supports locale-specific formats for dates and times, calendars, numbers, and so on.
Internationalization for this version targets the EMEA and APJ regions. Formal testing was performed using German, Simplified Chinese, Japanese, French, and Spanish. Informal testing occurred using Korean. The tested languages exposed the software changes that were necessary for supporting the remaining languages in the target regions.
Suite Licensing Support
When you receive VCM as part of the vCloud Suite or vCenter Operations Management Suite, you can enable object management with your suite license key when installing VCM. VCM license keys may also be updated after installation. With a suite key, object management is unlimited, provided that the objects are part of the suite and covered in the EULA.
Separate VCM server and workstation keys are still supported.
Change Log Data and Reporting Improvements
In this release, VCM makes change logs more usable for the vSphere environment. VCM now presents object data from vCenter differently, by performing a lookup and replacing the MOID with the more user-friendly object name. In addition, you can filter by object name, including wildcards, in change log reports.
vCenter Roles and Privileges
In vCenter environments, VCM now collects and presents vCenter user role names and the detailed privileges that those roles have.
New and Updated Virtual Environment Reports
VCM has enhanced the vCenter and vCD Permission Report by adding the new vCenter role names and privileges data. The improved report reveals which users have access to which objects, and what the users' permissions allow in vCenter. This release also adds new vCenter and Cluster Summary dashboards.
Linux or UNIX Assessment Content Download Process Changes
VCM can detect which Linux or UNIX operating systems are being managed and can download only the patching content that applies to those operating systems. When you add a new Linux or UNIX operating system to your managed machines, VCM downloads the appropriate patching content.
Mixed Machine Groups
VCM now supports Windows and Linux or UNIX systems in the same machine group.
Managed Machines Platform Support
VCM 5.6 adds support for the following platforms.
This release freezes support for the following platforms. The version 5.6 Agent and new 5.6 features are not supported on these platforms, but you can still collect and manage these platforms using previous features and previous agents.
VCM 5.6 drops support for the following platforms:
Center for Policy and Compliance ContentIndependent of the VCM 5.6 release, the following templates have recently been added or enhanced by the Center for Policy and Compliance to support new or changed compliance standards.
This release delivers a number of bug fixes that are documented in the Resolved Issues section and the VMware Knowledge Base.
The vCenter Configuration Manager Administration Guide and online Help include Getting Started information that guides you through the compliance integration process with vCenter Operations Manager.
This release includes two installation guides.
For information about how to install VCM in single-tier, two-tier, and three-tier deployment models, see the vCenter Configuration Manager Installation Guide. For information about configuring VCM to collect and manage data from your virtual and physical environments, see the vCenter Configuration Manager Administration Guide. Documentation can be downloaded from the VMware vCenter Configuration Manager documentation page.
When installing and upgrading VCM, consult the VMware Knowledge Base to view all issues related to the current release.
Open Source Components for vCenter Configuration Manager
The copyright statements and licenses applicable to the open source software components distributed in vCenter Configuration Manager 5.6 are available at Download VMware vCenter Configuration Manager, on the Open Source tab. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent generally available release of vSphere.
Upgrades to This Release
To upgrade your version of VCM to the current version, you must have VCM 5.4.0 or later. To migrate your environment to the current version of VCM, you must have VMware VCM 5.3, EMC Ionix SCM 5.0 or later, or Configuresoft ECM 4.11.1 or later.
Upgrades: An upgrade installs the new version of VCM on the 64-bit Windows machines in your single-tier, two-tier, or three-tier installation deployment models.
Migrations: A migration to VCM 5.6 requires you to install VCM in a 64-bit environment and migrate your 32-bit database to the 64-bit database. Before you perform the migration, update your environment to include the Windows Server 2008 R2 operating system, SQL Server 2008 R2, and SQL Server Reporting Services, and then migrate your existing VCM, SCM, or ECM data to the 64-bit environment.
Earlier Releases of VMware vCenter Configuration Manager
Features and known issues from earlier releases of vCenter Configuration Manager are described in the release notes for each release.
The following issues are resolved in the VCM 5.6 release.
This list of issues pertains to VCM 5.6 only. Some known issues from earlier releases might also apply to this release. If you encounter an issue that is not provided in this list of known issues, you can review the known issues from earlier releases, search the VMware Knowledge Base, or let us know by providing feedback.
The following issues are known to occur in the VCM 5.6 release.