VMware vRealize Configuration Manager Release Notes
VMware vRealize Configuration Manager 5.8.1 | 16 September 2015 | Build 90
Last Document Update: 16 September 2015
Check frequently for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
vRealize Configuration Manager 5.8.1 provides several new features and resolves multiple product issues.
- New platform support for Managed Machines
VCM 5.8.1 adds support for the following platforms. VCM can perform collection, patching, compliance, reporting, and machine filters for these platforms.
- SQL Server 2012 support for Always On Availability Group
SQL Server 2012 is supported as part of Always On Availability Group for VCM installation or upgrade. Users can now install or upgrade and run VCM on SQL server 2012 database having Always On Availability Group.
- Upgraded JRE to 1.7.0_85
JRE has been upgraded to 1.7.0_85 in this release.
- Upgraded Python version to 2.7.9
Python version for agent install components has been upgraded to 2.7.9 in this release.
- OpenSSL upgrade to 1.0.1p
OpenSSL in agents of all supported platforms of Linux, Unix, and Windows has been upgraded to 1.0.1p.
- SRF action for OpenSSL upgrade
VCM 5.8.1 introduces a new action button Upgrade OpenSSL that launches a wizard to upgrade the OpenSSL on the selected Linux, UNIX, Mac OS X, or Windows operating systems.
Also, a new column OpenSSL Version is added to the Licensed Windows and Unix data grid.
- Collecting the data for new versions of SQL Server Enterprise Applications
VCM 5.8.1 introduces a new filter to call system, SMO, and SQL commands to enumerate local SQL Server instances and get configuration properties from the newer versions of SQL Server Enterprise Applications, for which the data cannot be collected using the existing data types.
In this release, new features are documented in the VCM online help and the release notes.
The Software Content Repository Tool version is changed in this release to 6.1.21 to support SUSE Linux Enterprise Server 12 platforms and the same has been updated in the latest Software Content Repository Tool 6.1 Guide.
You can access the Software Content Repository Tool 6.1 Guide and the VCM 5.8.1 online help from the VMware Web site at http://www.vmware.com/support/pubs/vcm_pubs.html.
Upgrades to This Release
To upgrade your version of VCM to the current version, you must be running VCM 5.6.0 or later. To migrate your environment to the current version of VCM, you must be running VCM 5.5 or earlier, EMC Ionix SCM 5.0 or later, or Configuresoft ECM 4.11.1 or later.
An upgrade installs the new version of VCM on the 64-bit Windows machines in single-tier, two-tier, or three-tier installation configurations.
In this release, the upgrade process verifies your VCM certificates and gives you the option to select or generate new certificates. You must select or generate new certificates if the current certificates are expired.
A migration to VCM 5.8.1 requires that you 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, Windows Server 2012, or Windows Server 2012 R2 operating system; SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014, and SQL Server Reporting Services, and then migrate your existing VCM, SCM, or ECM data to the 64-bit environment.
For more information about upgrading an existing instance of VCM, see the VCM Advanced Installation Guide on the VMware Web site at http://www.vmware.com/support/pubs/vcm_pubs.html.
Open Source Components for vRealize Configuration Manager
The copyright statements and licenses applicable to the open source software components distributed in vRealize Configuration Manager 5.8.1 are available at Download VMware vRealize 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.
The VCM 5.8.1 release addresses and resolves internationalization defects that affected how VCM processes and displays non-ASCII characters and various date formats.
The following issues are resolved in the VCM 5.8.1 release.
Compliance results are not displayed for Rule with vCenter settings datatype and <=(num) operator
When you create a rule with vCenter settings datatype and <=(num) operator and run a template, Compliance results are not displayed.
This issue is resolved in this release.
VCM is causing excessive logging to SQL Server log files
Excessive logging of messages is observed when log files are interactively printed in the success message.
This issue is resolved in this release.
Security audit log is flooded due to frequent checking of listener service status
When the listener service status is frequently checked, the security audit log is flooded with log messages.
This issue is resolved in this release.
Scheduled reports built using wizard fail in VCM 5.8
When a report is added or edited from Report Wizard in vRealize Configuration Manager UI, it does not display columns for all Data Views and appears to be broken.
This issue is resolved in this release.
Custom Info Win 05: Scheduled Tasks fail when agent machine operating system is Windows Japanese edition
Custom Info Win 05: Scheduled Tasks fail if the agent machine runs Windows 2008R2 Japanese edition.
This issue is resolved in this release.
Software Content Repository (SCR) 6.1.6 fails to download the patches if more than one channels value are specified in properties file
For SCR 6.1.6, if you specify more than one channels value in the properties file, SCR fails to download the patches. For example, if you define channels=orae5,orae6, SCR 6.1.6 downloads only for orae6 and fails to download for orae5. This behavior applies to RHEL, OEL, and CentOS platforms.
This issue is resolved in SCR version 6.1.21.
The following issues are known to occur in the VCM 5.8.1 release. Known issues not previously documented are marked with the * symbol.
Enforcement will not work for vCenter-Guests-Configuration parameters datatype*
When a compliance rule is created with vCenter-Guest-Configuration parameters datatype, the rule cannot be enforced from compliance template results.
Windows HTTP agent may encounter Create connection failed error on machines in which no memory is available during large deployment of patches*
Create connection failed error may be observed with Windows HTTP agent machines in which no memory available during large patch deployment jobs. This is because, the patching process consumes memory in spikes per patch and the TrustedInstaller (part of the Windows OS) does not release all that memory after installing each patch. If the memory available at the agent, while the job status check is done by VCM is not enough, job status check would fail and report the overall patching Job failed with error Create connection failed.
- Use Automatic deployment with reboot enabled so that the machine will reboot after it runs out of memory due to patching, and will then continue the patch assessment and deployment processes after it comes back up.
- Deploy patches in small numbers based on memory of the target machine. Multiple patching templates can be created to achieve this.
Windows Patch Assessments may not respond in large environments*
The auto generated column in some patch assessment related tables are defined as INT. However, in large environments, the column values can be high enough to not fit in the INT data types. As a result, the patch assessments stop responding.
Workaround: Contact VMware Customer Support for information on resolving this issue.
vCenter Custom information collection failed when VCM is installed in non C drive*
When vRealize Configuration Manager is installed in non C drive, vCenter Custom information collection fails.
Workaround: Contact VMware Customer Support for information on resolving this issue or see KB 2037583.
Incorrect data is displayed for SQL Server Database Properties*
Incorrect data is displayed under Console->Enterprise Applications->SQL Server->Database->Properties when data is collected using SQL server filter or Windows Custom Information filter. This issue is observed only in a german setup.
Missing CentOS, OEL, and MAC platforms under vCenter--> Guests--> Manage Guests--> Machine Type*
CentOS, OEL and MAC platforms cannot be added and managed through vCenter Manage guests as the platforms are not available under vCenter--> Guests--> Manage Guests--> Machine Type.
SCR6.1.21 fails to download patches if #channels= is provided in properties file*
SCR6.1.21 will fail to download patches if the value #channels= is provided in the properties file.
Workaround: Specify all the values for the channel parameters in the respective platforms.
Newly added guest configuration setting is not displayed under available settings in Change Settings Wizard
When we add a new guest configuration setting for any guest, a key gets added. If I try to edit the same key immediately after adding it, it does not appear in the list of Change Settings wizard.
Workaround: Performing a delta collection of guest data class makes the new setting available to edit.
Foundation Checker is not checking whether the SQL Server Agent is enabled and running
The SQL Server Agent service is required for housekeeping and scheduled jobs processing. Foundation checker should verify that this service is enabled and running at VCM install time. Currently, Foundation Checker is not making any notification when the SQL Server Agent is disabled.
Linux agent upgrade for Ubuntu through Remote Commands is failing with error Remote Command returned non-zero exit code : 127
Linux agent upgrade for Ubuntu through Remote Commands fails with an error Remote Command returned non-zero exit code : 127. This is because, the script is not in the Unix format.
Workaround: Change the value of the setting RemoteCommandShellCompare in /opt/CMAgent/CSIRegistry to shell script
IP Address column is not populated if Allowed IP Range in vCenter is specified in CIDR notation
If Allowed IP Range in vCenter is specified in CIDR notation, the IP Address column is not populated with data under Console > Virtual Environments > vCenter > Hosts > Advanced Configuration > Security Profile node.
VCM delta collection of File system data type collects all data after time changes due to Daylight Saving
After time changes due to day light saving, the first delta collection of data type File system is treated as a non-delta collection, and also the same is reported in the change management tool.
Collection fails on RHEL 7.X versions when an agent is installed in xinetd mode
If you install an agent in xinetd mode, data collection fails on all RHEL 7.x versions.
Workaround: Install redhat-lsb-core package and execute lsb_release command. This command is available in all RHEL/SLES/Ubuntu templates.
Errors appear in DBE file while opening the Settings registry key
When you start an Unix agent installation from VCM or launch vCloud Director, vCenter Server, or vShield Manager collections from VCM, an error Error while opening the registry key - Settings is displayed in the DBE file. This error does not have any impact on the functionality.
Workaround: Create the registry key Settings under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Configuresoft\CSI\5.0\Common\Settings and create a DWORD EnableFips under this key. This also helps in performing operations in FIPS mode.
Collections from vCloud Director with vCenter Single Sign-On fail because VCM cannot authenticate the user
When VCM collects data from a vCloud Director instance that is configured with vCenter Server Single Sign On, the collection fails, because VCM requires the user name to be in the form username@SYSTEM or username@<OrganizationName>.
If you navigate to Administration > Machines manager > Licensed Machines > Licensed Virtual Environments, click Configure Settings, and provide the user credentials of the SSO user, the collection fails because VCM cannot authenticate the user.
Double-byte characters are not recognized while adding accounts with double-byte full name and description in a high ASCII environment. High ASCII characters are not recognized while adding accounts with high ASCII full name and description in a double-byte environment
In a double-byte environment, when you create user accounts having full name and description in high ASCII characters, the high ASCII characters are not recognized. Similarly, in a high ASCII environment, if the accounts are created in double-byte characters, then the double-byte characters are not recognized.
Unable to deploy patches from imported templates for UNIX/Linux platforms
After you create an imported template with appropriate patching format, if you click Deploy to deploy the patches, the operation fails and the warning message
There are no assessment items to deploy. The deployment is applicable to a machine licensed for Unix patching and with a patch status of 'Not patched'. The wizard will be closed is displayed.
Patch deployment fails for some Linux managed machines, such as CentOS and OEL, when SELinux is enabled on the managed machine
VCM installs the Linux Agent in inetd or xinetd mode by default. When SELinux is enabled on the managed machine, and the Linux Agent on the managed machine is running in inetd mode, patch deployment fails and VCM displays an error similar to the following error: install: %pre scriptlet failed (2), skipping <PACKAGE>. For more information, see KB 2079311
Workaround: Redeploy the Linux Agent to the managed machine in daemon mode.
You cannot set Network Authority to the CMDelegate account when the protocol of a Windows machine is unknown
When you use VCM Remote before an Agent is installed on the managed machine, or when you use an earlier version of VCM Remote, then manually install an HTTP Agent, the protocol setting is empty in Administration > Machines Manager > Licensed Machines > Licensed Windows Machines, and does not change when you run the Change Protocol action. You cannot set the Network Authority to the CMDelegate account, because the Network Authority requires HTTP as the protocol.
Workaround: Wait 2 to 5 minutes for VCM Remote to update the protocol to HTTP in the user interface, then set the Network authority to the CMDelegate account.
VCM does not update the list of snapshots after you delete a snapshot
After you collect data from a vCenter Server instance that includes multiple hosts, guests, and snapshots, when you navigate to Console > Virtual Environments > vCenter > Guests > Snapshot, select one or more snapshots, and click Delete Snapshot, when you view the list of snapshots in Console > Virtual Environments > vCenter > Guests > Snapshot, VCM does not update the list of snapshots, even though the snapshots are deleted. This behavior also occurs if you use the Virtual Environment Compliance remediation action to delete a snapshot.
Workaround: Collect the vCenter Server Guests data from the managed machines, and view the updated list of snapshots.
McAfee Solidifier blocks the VCM installation
When you attempt to install VCM on a machine that has McAfee Solidifier installed, the installation fails.
Workaround: To install VCM on a machine that has McAfee Solidifier installed, either put McAfee Solidifier in update mode, add an exception rule in McAfee Solidifier, or disable McAfee Solidifier until VCM is installed, and then enable it again.
VCM Collector is not trusted as a Managing Agent after upgrade from VCM 5.4
On a VCM Collector that has VCM 5.4 installed and data collected from managed machines, when you upgrade the Collector to the current VCM version, neither the Trust status or the Managing Agent status are enabled for the Collector machine.
Workaround: After you upgrade the Collector to the current VCM version, restart the Collector service, then navigate to Administration > Settings > Certificates on the Collector, and verify that the Trust status and Managing Agent status are enabled for the Collector.