Appliance Installation

Virtual Appliance

The BMC Atrium Discovery solution is supplied as a virtual appliance. Apart from installation, all interaction with a virtual machine based appliance is identical to the hardware appliance.

See Virtual Appliance for more information.

Kickstart DVD

The kickstart DVD can be used to install BMC Atrium Discovery on customer supplied hardware.

See Installing BMC Atrium Discovery for more information. See also Supported platforms for installing BMC Atrium Discovery for more information on the hardware onto which you can install BMC Atrium Discovery using the kickstart DVD.

Physical Appliance

The BMC Atrium Discovery solution was previously supplied as a physical appliance with all software pre-installed, including the BMC Atrium Discovery application.


BMC Atrium Discovery is sold and licenced as a whole virtual machine that ships with everything pre-installed, including the application, the operating system and a number of other commercial and open source third party packages and products. The entire package is licenced to customers for use in that way. BMC Atrium Discovery customers have the right to create as many VMs as they deem necessary to conduct an inventory of their environment.

Therefore, for software licensing purposes BMC Atrium Discovery customers should disregard any instances of Red Hat that are running in a BMC Atrium Discovery appliance. Any queries from Red Hat regarding those instances should be referred to BMC Software.

Virtual Appliance

Ensure that you have entitlement with BMC to download the VA from the BMC site To check the entitlement, contact

Raise an internal service request to allocate ESX/VMware Server space and to install the Virtual Appliance.


The Virtual Appliances are packaged as a compressed zip file that contain a single VMware Server virtual machine and a pdf of the Getting Started Guide guide.

They are built using VMware Server version 2.0 (build 122956) and will run without modification in VMware Server, Player and Workstation. However, to deploy the Virtual Appliance into the VMware Enterprise class products (ESX/ESXi), an additional conversion process is required.

Disk Space Requirement

The Virtual Appliances are packaged as VMware Server virtual machines because the Enterprise class images pre-allocated disk space is very large. Prior to deployment, you should ensure that you have sufficient free disk space available. See sizing guidelines for more information.


The following sections detail how the Virtual Appliance is supported in its two configurations.


Although the BMC Atrium Discovery Virtual Appliance can run in any of the VMware products in the following section, BMC supports various deployments at different levels:

Recommended: These environments are the preferred platforms recommended by BMC.
Supported: These environments, although not preferred, are supported by BMC.

Free VMware Products

BMC can only support Virtual Appliances deployed into one of the freely available VMware virtualisation tools (ESXi or VMware Server), if the customer has in turn purchased support from VMware.

VMware support matrix

For sizing guidelines for each of the deployment platforms, see Appliance sizing guidelines.

Community Edition

Users of the Community Edition can get support from the BMC Community. This is best achieved by reading and posting to the public forums.

In addition to those products listed above, the BMC Atrium Discovery Virtual Appliance will also run in the following tools:

A link to the relevant VMware support site is provided below:


The following sections specify the default specifications of the Virtual Appliances supplied by BMC.

Production Appliance

  • CPU: 1
  • RAM: 2048MB
  • Hard Disk: 1 x SCSI 54 GB (set to grow as necessary in 2 GB file increments)
  • CD/DVD Drive: 1 (auto detect)
  • Network Interface Cards: 1 (eth0) bridged, configured to use DHCP to obtain an IP address.

The Network Interface Card (eth0) is configured to use DHCP. However, this can be changed to use a static IP.
During the install process, the following network configuration is required:

  • DHCP or static IP for eth0 interface
    If Static IP then provide the following:
    • Appliance IP Address
    • Gateway
    • Subnet Mask
    • DNS for address lookup


For initial testing at a small scale, the default configuration is sufficient. For production use, or use at scale you must increase the RAM, CPU and disk configuration in accordance with the sizing guidelines. One size Virtual Appliance is supplied, because a single size simplifies delivery and does not require you to download various sized VMs for various applications such as scanning and consolidation appliances.

2GB RAM is insufficient to activate a TKU in an acceptable time. To use a TKU in testing, you must increase the amount of RAM in the system to 4GB or more.

Community Edition Virtual Appliance

The BMC Atrium Discovery Community Edition Virtual Appliance is supplied as a compressed zip file and built with the following default configuration:

  • CPU: 1
  • RAM 512MB
  • Hard Disk: 1 x SCSI 24 GB (set to grow, in 2 GB file increments)
  • CD/DVD Drive: 1 (auto detect)
  • Network Interface Cards: 1 (eth0) bridged, configured to use DHCP to obtain an IP address.

To run the BMC Atrium Discovery Community Edition Virtual Appliance, your system must have sufficient RAM to support your operating system and the Virtual Appliance (1 GB RAM is recommended) and a minimum of 25 GB of hard disk space should the Virtual Appliance grow to full capacity. Additional CPUs and RAM can be allocated to improve performance.

Was this page helpful? Yes No Submitting... Thank you


  1. $author.fullName

    Why are the default specs for a production appliance different to those shown in the sizing guidelines? This can be confusing.

    Nov 16, 2011 04:03
    1. Duncan Tweed

      Hi Brandon,

      Thanks for taking the time to comment. There are a couple of reasons that the default production appliance is not the same size, actually considerably smaller, as any of those mentioned in the sizing guidelines. Firstly, we'd need to supply a selection of differently sized VMs, even then you'd probably need to modify the size for your particular environment. If you were setting up scanning and consolidation appliances, you'd probably want each one of those to be differently sized too. Also, unless you're careful when uploading the VM to VMware ESX, it will attempt to allocate the full disk requirement immediately, which is unlikely to be exactly what you're intending. So we supply a single production VM and instructions on modifying the disk size, or adding an additional drive.

      I'll modify the Warning box on this page to add some of this explanation.

      Thanks again for your feedback, Duncan.

      Nov 17, 2011 08:54