System requirements

Depending on the architecture, the hardware and software requirements must be met before on-premises and cloud installation of BMC Client Management components.

Consider the following high-level tasks of the installation process:

  1. Verify the database server requirements
    1. Recommendations for Oracle
    2. Recommendations for PostgreSQL
    3. Recommendations for MS SQL Server
  2. Verify the master and relay server requirements
  3. Software requirements
  4. Best practices for masters and relays deployed on Linux
  5. Database installation and configuration
  6. Managing the database maintenance tasks

Set up the machines to meet system requirements to ensure that you can successfully install and run the BMC Clients Management.

Supported virtualization

Component

Supported Platforms 1

Virtual Platform Support

BMC Client Management (Client Management ) was proven by BMC Software customers to function properly in virtualized data centers that use VMware® ESXi™, VMware® Infrastructure™ and Microsoft Hyper-V Core Server 2008 R2. Client Management is only supported in these environments if the product is installed on an approved OS platform, web server, and database. Client Management might work properly on other virtualization products, but BMC Software has not tested them and verified that functionality. BMC Software has no documented statistics regarding the performance of Client Management in these environments since the mix of outside vendors' applications and hardware can have a direct impact on overall performance. Additionally, should BMC Software believe that the virtualization layer is the root cause of an incident the customer is required to contact the appropriate virtualization layer support provider to resolve the virtualization issue. Note, that BMC server components are not supported on VMware Server™ or VMware Workstation using the GSX engine in a production environment since it is not designed for hardware optimization.

  1. The OSD Manager (functional agent module/role) is not supported on a virtual platform. It must be designated/reside on a physical host due to TFTP constraints with virtualization.

Miscellaneous prerequisites

If your company's internal standards differ from the general way of dealing with data in BMC Client Management, you can keep the software core data and generated data separate. You must consider this before the master installation to allow for the differences.

Keeping software core data and generated data separate

All data that is generated by BMC Client Management is located in a directory called <InstallDir>/master/data . To take this directory out of the installation directory, create an empty partition and change the path of this partition in the disk management mmc. Then select the data folder (the folder must be empty; otherwise you cannot select it).

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

Comments

  1. Mike Jones

    I see that the documentation on this page states: "That the OSD Manager (functional agent module/role) is not supported on a virtual platform. It must be designated/reside on a physical host due to TFTP constraints with virtualization." My customers and I have used virtual servers for the OSD manager for years and have not encountered any constraints. Could you please advise if this still not supported and if so, is there any documentation that could elaborate on the issue? Thank you. Mike Jones

    Feb 06, 2023 03:06