check-circle-line exclamation-circle-line close-line

VMware vRealize Configuration Manager Release Notes

VMware vRealize Configuration Manager 5.8.4 | 18 January 2018 | Build 223

Last Document Update: 29 January 2018

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

vRealize Configuration Manager 5.8.4 provides supports to several upgraded programs and includes new features.

  • JRE upgrade to 1.8.0_141
    JRE has been upgraded to 1.8.0_141.

  • SCAP 1.2 support for Linux
    In addition to OpenSCAP support for Windows, VCM 5.8.4 supports the compliance assessment of all the SCAP 1.2 content on all the supported Linux platforms.

  • SCR 6.2.53
    The Software Content Repository Tool version is changed to 6.2.53

  • OpenSSL Security 1.0.2l
    OpenSSL Security 1.0.2l support has been provided for Linux, UNIX, and Windows platforms.

  • Python upgrade to 2.7.14
    Python version has been upgraded to 2.7.14 for Linux, UNIX and Windows platforms.

  • Replaced Pivotal TC Server upgrade to Apache TC Server
    Pivotal TC server has been replaced to Apache TC Server 8.5.23.

  • XLSX support format for scheduled reports.
    VCM 5.8.4 enables you to export larger scheduled reports in XLSX format.
    Note: XLSX format is supported on SQL Server 2012 and later.

  • Enable editing of Asset Extensions to all Admin users, in addition to the built-in admin.
    When you assign an Admin role to a user, the new admin user can edit the Asset Extensions.

Updated Documentation

Only the following documents have been updated for the vCM 5.8.4 release. For other documents, please refer to the earlier release documentation set at https://docs.vmware.com/en/VMware-vRealize-Configuration-Manager/index.html.
  • vRealize Configuration Manger Online Help
  • Software Content Repository Tool Guide
  • Release Notes

Upgrades to This Release

To upgrade your version of VCM to the current version, you must be running VCM 5.7.3 or later. To migrate your environment to the current version of VCM, you must be running VCM 5.7.2 or earlier, 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 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.

  • Migrations
    A migration to VCM 5.8.4 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, SQL Server 2014, or SQL Server 2016 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 https://docs.vmware.com/en/VMware-vRealize-Configuration-Manager/index.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.4 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.

Internationalization

The VCM 5.8.4 release addresses and resolves internationalization defects that affected how VCM processes and displays non-ASCII characters and various date formats.

Resolved Issues

The following issues are resolved in the VCM 5.8.4 release.

  • The collection against a linux machine fails.
    The agent does not respond to the execute command from the vCM server and sends FIN packet to vCM Server.

  • Multiple instances of agent running in the daemon mode.
    You see multiple instances of agent and the following error message.
    The request dispatcher thread has stopped. The request CANNOT be queued HRESULT 0x80004005 = Unspecified error;

  • The machineEnv rest API does not work and returns the SQL Grammar Exception.
    SQL Grammar Exception error appears while running the machineEnv API.

  • Unable to import the XML file containing Collection Filters into vCM.
    When you attempt to import the XML file containing Collection filters into vCM, the import process stops responding and does not complete.

  • The VM count in the vCenter server inventory and in vCM does not match.
    You could not see all the VMs under Available Machines in vCM.

  • Unable to enter more than 30 characters
    Though the field can support up to 2000 characters, you could not enter more than 30 characters because of the field property limitation.

  • The file system collection failed to transform
    The vCM file system collection failed to transform with the following error:
    Cannot insert duplicate key row in object 'dbo.ecm_dat_file_system_directories' with unique index

  • Unable to download Windows patch bulletins by using proxy server
    When you attempt to download the Windows patch bulletins, you see the Open Connection Failed error.

  • Unable to upgrade vCM 5.7.3 to 5.8.1
    vCM upgrade from 5.7.3 to 5.8.1 failed with the Installation error.

  • vCenter Guest compliance enforcement is processing enforcement multiple times
    vCenter Guest compliance enforcement is creating one job for each object, but each job is processing all enforcement

  • vCM is unable to complete the Database Heartbeat job.
    The Database Heartbeat job failed with the following error message:
    Could not find stored procedure

  • The active directory collection is successful, but the user and group data does not appear on the UI.
    After you add new users to the active directory domain and run the collection, you see the following error:
    [AD.Search.ClientControlsList]dynamic object did not contain a value.
    Empty Hds results stream returned from inspector

  • Licensing or unlicensing a machine in vCM is taking a long time.
    When you license or unlicense a machine in vCM (Administration > Machine Manager), the UI freezes for a while ( 3 to 4 minutes) before it completes the action.

  • PCI DSS 3.1 vSphere 5.5 Compliance Assessment fails on Network rule with an error
    After you import PCI DSS 3.1 vSphere 5.5 content, when you run an instant or scheduled compliance assessment, the assessment fails with the Invalid length parameter error.

  • When you have PowerShell data types included in the collection, the folders does not delete automatically
    When the collection contains the Windows Auditing Settings powershell data type, after completion of the collection job, the CollectorData folder is not deleted.
  • The template report and the data grid view report does not match with the Virtual Environment Assessment results
    After completion of the Virtual Environment Assessment, the result summary report for rules does not contain all the rules.

  • When you run the bulletins for AIX, the summary report is empty
    When you view the assessment result for all bulletins of AIX, you see an empty report. But, the data appears in data grid view.

  • After 5.8.3 upgrade, you could not use https to communicate with VCM remote agent
    After you upgrade to 5.8.3 version, when you use https to communicate with a remote agent, you see the following error:
    Cannot reach host: https://vcmd/VCMRemote/ECMRemoteHTTP.ASP

  • While performing a collection, the filter for a machine group is not working
    When creating a collection job, when you select a machine, the wizard does not filter to display the objects that belong to the selected machine.

  • The CIS Compliance For Windows Server 2008 does not process exceptions
    After you create a filter and run the template, when you create exceptions, only one execution works. You see the following error:
    Incorrect syntax near 'Access'

  • You observe performance issues while running an assessment
    When you run a patch assessment, the process takes a long time and sometimes fail.

  • The SSRS report does not display correct filtered results
    Though you add a filter to see only selected vCenter Server data in the SSRS report, you see all virtual objects from other vCenter Servers also.

  • Data collections for Software Inventory - Packages fails on OEL 7.3 machine
    The data collection for Software Inventory - Packages fails on OEL 7.3 machine fails and you see the following error message:
    Unable to find the RequestId attribute for the data file. HRESULT 0x80004005 = Unspecified error;

Known Issues

The following issues are known to occur in the VCM 5.8.4 release. New known issues are marked with the * symbol.

  • * The context sensitive help does not work for the Install OpenSCAP Engine wizard
    When you click Help on the Install OpenSCAP Engine wizard (Administration > Machines Manager > Licensed Machines > Licensed UNIX Machines > Install OpenSCAP Engine), the help window open the Welcome page.
    Workaround: Open the Install OpenSCAP Engine wizard information manually on the online help page.
    Expand Managing Linux, UNIX, and Mac OS X Machines > Linux, UNIX, and Mac OS X Data and Actions > About Administration > About Machines Manager > Licensed Machines > Licensed UNIX Machines > Install OpenSCAP Engine
  • * The XML file for the XCCDF XML column in SCAP compliance assessment result is not formatted
    In the SCAP compliance assessment result, when you click a link in the XCCDF XML column, the content you see is not formatted in XML.
    Workaround: None
  • The Resubmit Job during UNIX patch deployment is not working*
    When the deployment of a patch on the target UNIX machine fails, when you navigate to Administration > Job Manager > History > Other Job and click Resubmit Job, you see the No data returned error.
  • Unable to upgrade VCM on any other drive other than C:\ drive with 8.3 naming disabled
    Upgrading VCM on any drive other than C:\ drive with 8.3 naming disabled fails with an error message Could not open install.log file. When you click OK on the pop-up screen, the upgrade continues without any impact of VCM functionalities.
    Workaround: None.
  • Windows 2016 Server core machines are reported as full installation instead of core installation
    VCM reports Windows 2016 Server Core machines as full installation instead of core installation. This does not impact patching as the situation is handled in content.
    Workaround: None.
  • In Jlicense, the new SKU of vRealize Operations Management Suite 6 Advanced Edition is displayed as 'Server' edition instead of 'vRealize Operations Manager Advanced Suite'
    During dry run, when you apply Jlicense, the new SKU of vRealize Operations Management Suite 6 Advanced Edition is displayed as 'Server' edition instead of 'vRealize Operations Manager Advanced Suite'. You will notice that the license applied is displayed under 'vRealize Operations Manager Suite Server' Machine Class as expected and the functionality is unaffected.
    Workaround: None.
  • In an upgraded VCM environment, the TLS 1.2 protocol is not supported before the Agent upgrades
    You can use TLS 1.2 protocol only after the Agent upgrades in an upgraded VCM environment.
    Workaround: Follow the steps below to workaround this issue:
    1. Enable all TLS protocols.
    2. Upgrade all Agents.
    3. Disable TLS 1.0 and 1.1 to work with only TLS 1.2 protocol.
  • Solaris 11 does not support agent installation in xinetd mode
    Solaris 11 supports agent installation only through daemon mode and does not support agent installation in xinetd mode.
    Workaround: Install the agent in daemon mode.
  • Microsoft Edge is not supported with vRealize Configuration Manager
    Accessing vRealize Configuration Manager from Microsoft Edge browser is not supported.
    Workaround: Use Internet Explorer 11 to access vRealize Configuration Manager.
  • 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. Currently, Foundation Checker is not making any notification when the SQL Server Agent is disabled.
    Workaround: Validate the SQL Server agent services that must be running.
  • 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.
    Workaround: None
  • 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.
    Workaround: None
  • 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.
    Workaround: None.
  • Manage Guests option under Console > Virtual Environments > vCenter > Guests > Summary creates duplicate machines of same guest name if the guest is already managed
    Manage Guests option on any guest machine under Console > Virtual Environments > vCenter > Guests > Summary is allowed multiple times. This causes the duplicate guest machines to be created if the guest is already managed.
    Workaround: None.
  • 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.
    Workaround: None.
  • 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.
    Workaround: None.
  • Check boxes do not work on Report data page while creating an Active Directory Report in Internet Explorer 10 or 11
    Some checkboxes cannot be selected or do not appear in the Report data page while creating Active Directory Reports in Internet Explorer 10 or 11.
    Workaround: Click Back and return to the Data Type wizard. The check boxes appears correctly.
  • 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.
  • Unable to import Microsoft SQL Reporting Service Report
    You cannot import Microsoft SQL Reporting Service Report when you log in to VCM with a domain user that is added into VCM by a domain user with VCM administrator role. The error message Unable to save one or more reports is displayed. 
    Workaround: None.