vRealize Business Standard 6.0 Release Notes

vRealize Business Standard |09 December 2014 | Build 2323216

Last updated: 09 December 2014

Check for additions and updates to these release notes.

The release notes covers the following topics:

  • What's New
  • Documentation
  • Known Issues and Limitations
  • What's New

    The release contains the following enhancements:

  • Integration
    • vRealize Automation 6.2 version. The release of vRealize Business Standard 6.0 is compatible with the vRealize Automation 6.2 release.
    • EMC SRM. vRealize Business Standard can integrate with EMC Storage Resource Management (SRM), which provides storage array details and helps to determine the storage cost of virtual machines based on its LUNs' base rate. vRealize Business Standard supports EMC SRM 3.2 or later versions and also supports VNX, VMAX, and VPLEX array families.
  • Cost analysis
    • Enhancements to pricing. vRealize Business Standard lets you set and edit the price for the virtual machines manually or by creating policies according to the properties of vRealize Automation, vCloud Director, and vCenter Server.
    • Improved consumption analysis. vRealize Business Standard lets you compare budget, actual cost, and allocated charge for virtual machines at monthly and yearly intervals.
    • Support for budgeting. vRealize Business Standard lets you set budget values for a consumers based on categorization such as vCenter Server, vRealize Automation, and vCloud Director.
    • Visibility to storage cost. vRealize Business Standard provides storage cost visibility in terms of disks and LUNs, which computes base rates of LUNs and datastores automatically. These base rates are used to determine the storage cost of virtual machines.
    • Support Costing of physical servers. vRealize Business Standard support the costing of physical servers managed in vRealize Automation.
    • Support new currencies. vRealize Business Standard supports several additional currencies for cost calculation, which you can set during vRealize Business Standard deployment.
    • New roles added in vRealize Automation. New vRealize Business Standard roles (Tenant Administrator and Business Management Controller) are added in vRealize Automation to assign specific permissions to the selected users.
  • Cloud comparison
    • Support for data center comparison. vRealize Business Standard enables you to compare costs of data centers and helps you to plan for deploying the virtual machines in a cost effective approach.
  • Public cloud
    • Enhancements to AWS support. vRealize Business Standard provides details about virtual machines and the cost for an Amazon Web Services (AWS) account. It also enables you to compare cost of reserved and on-demand Pay As You Go (PAYG) instances.
    • vCloud Air usage cost visibility. You can add and manage vCloud Air accounts to vRealize Business Standard. You can view the account usage details, total vCloud Air cloud cost information, along with the account specific information.
  • Report enhancements
    • Storage Reports. You can generate reports for storage array and storage LUNs cost details.
    • Track historical data. You can export the virtual machine details and export its cost for the current month or any previous month of a year.
    • Public Cloud Reports. You can generate reports to view the details of virtual machines and virtual machines' monthly costs that are hosted on AWS account and vCloud Air accounts.
  • Documentation

    VMware vRealize Business Standard Installation and Administration Guide

    VMware vRealize Business Standard User's Guide

    Known Issues and Limitations

    The following limitations and issues are known to occur in this vRealize Business Standard release:

    • When you attempt to filter reports by using a long string as a filter criterion, an error appears.
      Workaround: To resolve the issue, change the HTTP connector size to 64000 or greater in the server configuration. For example, maxHttpHeaderSize="65536".

    • The vCenter server storage service might fail during storage data collection and the failure causes storage profiles to not appear in vRealize Business Standard.
      Workaround: See the Storage Synchronization Failure topic in the VMware vRealize Business Standard Installation and Administration Guide.

    • When the system process is complete for the first time and updates the cost calculation and connections, the cost data is not displayed on the dashboard.
      Workaround: Refresh the browser to view the updated cost data.

    • If the vRealize Business standard server has to manage more than 10,000 virtual machines, the server might restart or you might see an out of memory error.
      Workaround: Perform the following steps to increase the memory size.
      1. Stop the itbm-server service.
      2. Navigate to the following path /usr/local/tcserver/vfabric-tc-server-standard/itbm-server/bin.
      3. Take a backup of the setenv.sh file.
      4. Open the setenv.sh file.
      5. Search for the Xmx4096m string.
      6. Replace Xmx4096m with Xmx6144m.
      7. Start the itbm-server service.

    • If the vRealize Business Standard server is overloaded, you see an internal server error.
      Workaround: Access vRealize Business standard after sometime.

    • Even after the successful completion of vCenter Server data collection, the system status appears in red.
      Workaround: Do not change the time zone of vRealize Business standard virtual appliance. You must use UTC time zone.

    • After you edit the Server Hardware CSV file in Microsoft Excel, uploading the CSV file might fail.
      Workaround: Use Notepad to edit the CSV file. Editing in Microsoft Excel might change the date format.

    • If you edit the reference cost and then change it back to its original value, the legend still shows the message Costs have been manually entered.
    • If you migrate ESXi hosts from one vCenter Server to another vCenter Server without deleting the ESXi hosts from the first vCenter Server, vRealize Business Standard considers the cost of twice during cost calculation, because the cost of host is considered once from the source vCenter Server and once from the target vCenter Server.
      Workaround: To avoid duplication of costs, delete the ESXi hosts from the vCenter Server after migration.
    • Even after users are granted permission to perform a new task, they are unable to complete the task.
      Workaround: After being granted new permissions, users with permissions need to log out and re-login to confirm the change.
    • When a client machine is suspended and then restored after 7 or 8 hours of inactivity, you see an error message about a malformed security token shell.
      Workaround: Reload the application to restore functionality.
    • When you attempt to connect to a vSphere or vApp provisioned resource with Internet Explorer, you see an error message indicating that the virtual machine is not powered on or is not available on the network.
      Workaround: Define the virtual machine mode.
      1. Log in to the Internet Information Services (IIS) machine as administrator, navigate to C:\Program Files (x86)\VMware\vCAC\Server\Website\VMRC folder, and open vmrc.js with a file editor.
      2. Search for the following line:
        var startup = function (modes, msgMode, advancedConfig) {
      3. Add two lines to define modes and msgMode so that the content of the file looks like this:
        var startup = function (modes, msgMode, advancedConfig) {
        modes = 2;
        msgMode = 2;

      4. Save and close the file.
      5. Restart the IIS machine.