IT Business Management Standard Edition 1.0 Release Notes

IT Business Management Standard Edition 1.0 | 10 December 2013 | Build 1446817

Last updated: 10 December 2013

Check for additions and updates to these release notes.

The release notes covers the following topics:

Key Features

IT Business Management Standard Edition is part of vCloud Automation Center and provides business management and cost transparency capabilities to your virtual infrastructure.

  • Determines pricing of vCloud Automation Center blueprints by using the current cost and utilization levels of virtual machines as a reference.
  • Helps in decision making process of placement of workloads, either in the private or public clouds, based on the cost and the services that are available in your hybrid cloud environment.
  • Provides showback of virtual machine cost and blueprints based on business unit, application group across the hybrid cloud environment.
  • Lets infrastructure stakeholders to manage costs based on capital expenditure and operating expenditure.
  • Provides all capabilities with minimal configuration with out-of-the-box data.


VMware IT Business Management Standard Edition Installation and Administration Guide

VMware IT Business Management Standard Edition User's Guide

Known Issues and Limitations

The following limitations and issues are known to occur in this IT Business Management Standard Edition release:

  • 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 click Print on the Overview page, the contents are not displayed properly.
  • You cannot configure an NTP server by using IT Business Management Web console.

    Workaround: Log in to the virtual machine console of IT Business Management Standard Edition to configure the NTP server. For more information, see the Installation and Administration guide.

  • If you migrate ESXi hosts from one vCenter Server to another vCenter Server without deleting the ESXi hosts from the first vCenter Server, IT Business Management Standard Edition duplicates the cost of hosts 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, you delete the ESXi hosts from the vCenter Server after migration.

  • If you move an ESXi host from the datacenter level to a cluster level under the same datacenter where the ESXi host is present, duplicate entries ESXi host appear in the Server Generations section under Operational Analysis tab.

    Workaround: Restart the IT Business Management Standard Edition server.

  • If you perform multiple edits to the cost drivers while the global synchronization process is in progress, an error message is displayed in the user interface and StaleStateException appears in the log file.
  • If users are granted permission to perform a new task, they may find that they are unable to complete the task.
    Workaround: After being granted new permissions, log out and then log back in to confirm the change.
  • When a client machine is suspended and then restored after 7 or 8 hours of inactivity, the user sees an error message about a malformed security token shell.
    Workaround: Reload the application to restore functionality.
  • When you try 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.
      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 the file to find the following line:

      3. var startup = function (modes, msgMode, advancedConfig) {
      4. Add two lines that define modes and msgMode so that it looks like this:
        var startup = function (modes, msgMode, advancedConfig) {
        modes = 2;
        msgMode = 2

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