Installing BMC Configuration Drift Management

1.

 Back up the AR System database.

This allows you to restore AR System to its preinstallation state if you encounter problems.

2.

Activate the licenses for all BMC applications that you need to work with Drift Management.

License BMC Atrium CMDB, Change Management, Incident Management, Flashboard Server, and so on, before you install them. Ensure that you apply all the licenses you need.

Note: If a customer installs BMC Configuration Drift Management on the AR System server that is subject to the BMC Atrium SC license restriction, the customer is limited to three (3) fixed users for BMC Configuration Drift Management.

3.

Check for a missing DLL file (Windows 2003).

In Windows 2003 environments, you get an error if the framedyn.dll file is not in the system directory. As a result, the installer cannot capture available memory. To fix the problem, Microsoft has published a Knowledge Base entry and workaround to replace the missing framedyn.dll file.

4.

Verify the amount of TEMP space needed by the installer.

The Drift Management installer needs to use a large amount of disk space at initialization time, several times larger than the space required by the installed Drift Management application. This is because the installer self-extracts its contents to a temporary directory before it can run. The location of this temporary directory is dependent on the underlying operating system.

5.

Install Drift Management and help as non-root - Linux only.

6.

Handle issues with installing Drift Management on an Oracle database.

If you are installing Drift Management on an AR System server with an Oracle database, the installation sometimes stops due to the BMC Remedy Action Request (AR) System server timing out.