Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

Perform the following tasks before launching the BMC ProactiveNet installation program.

  • Clean your temporary directories. Start with the temporary folder in your home folder. Also clean the %Temp%, %Tmp% directories, and C:\WINNT\Temp or C:\Windows\Temp if present. You might not be able to delete all the files, but BMC recommends that you remove any files or directories that begin with ProactiveNet.
  • If Terminal Services is enabled, configure it to save installation log files after the installation is complete; otherwise, the log files will be deleted.
  • Enable Windows short path configuration.

Configuring Terminal Services to save the log files

Terminal Services creates a temp directory for each user account, and the installation program creates log files in this directory. At the end of the session, Terminal Services deletes the temp directory and any files that it contains, including the installation log files. By using the Terminal Services configuration tool, you can change Terminal Services so that it saves the log files.


If you do not configure Terminal Services to save the log files, the installation will fail.

To configure Terminal Services to save log files

  1. Choose Start > Programs > Administrative Tools > Terminal Services Configuration.
    The Terminal Services Configuration/Server Settings tool is displayed.
  2. Open the Server Settings folder.
  3. In the Delete temporary folders on exit dialog box, choose No and click OK.
  4. In the Use temporary folder per session dialog box, choose No and click OK.
  5. Close the Terminal Services Configuration/Server Settings tool.
  6. Open the Registry Editor and navigate to the following registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server
  7. Verify that the following registry keys in the Terminal Server registry have the appropriate settings:



    Data value







    This registry value exists only if flat temporary folders are enabled. If flat temporary folders
    are disabled, the FlatTempDir key is not present.



Reboot the computer.


BMC Software recommends that you retain the Terminal Services settings after installing BMC ProactiveNet. Retaining these Terminal Services settings will make it easier for you to upgrade to future versions of BMC ProactiveNet.

Enabling Windows short path configuration

Enabling the Windows short path configuration allows your system to return the short path used by programs that require the 8.3 file naming convention.

To enable Windows short path configuration

  1. Go to the Start menu => Run..., type regedit and press Enter.
  2. On the left pane of the Registry Editor, select HKEY_LOCAL_MACHINE and press Ctrl+F to open the Find window.
  3. Search for the binary data NtfsDisable8dot3NameCreation.
  4. On the right pane, select NtfsDisable8dot3NameCreation and go to Edit => Modify.
  5. Update Value data to 2, and click OK

Checking the pre-installation requirements for Windows

When you start the BMC ProactiveNet Server installation, the installer checks to ensure that the target computer is configured based on the recommended settings. The installer checks the environment and reports a status of OK or Not OK for each configuration variable that it checks.

For Windows, the following pre-install checks are run:

Pre-installation check



Determines whether or not the firewall service is running. The firewall should be turned off.


Checks to determine if the user running the preinstallation utility is an administrator or part of the administrator group.


Checks that the operating system patch (if any) is supported.


Checks that the necessary amount of RAM is available.

Hard Disk Space

This check:

  • obtains the list of drives
  • obtains the list of quorum in case of cluster systems
  • determines the disk space available for each of the drives
  • identifies the drive (for example, during install, it will identify if it is a C or D drive)


Checks that the processor configuration is supported.


Checks that the required ports are available. For the list of ports required, see Security.


Checks the page file size.


Checks whether the NIC card is available.


Confirms the IP address.


Verifies that the default gateway is not blank.


This check:
identifies the file system (for example, on Windows it will say NTFS which is supported for Windows)

Disk Info

This check:

  • obtains the list of drives
  • obtains the list of quorum/common data disks if there is a cluster installation
  • identifies the disk space available for each drive
  • identifies the drive and file system, and checks for sufficient space


Checks that there is enough free disk space on the system boot drive.


Looks for the presence of the MSVCP60.dll file, which is required for BMC ProactiveNet Server installation or upgrade.


Determines if the system architecture is 32 or 64-bit.


Checks to ensure that Terminal Services is configured to save log files. If the check fails, then follow the instructions in Configuring Terminal Services to save the
log files.


Checks to ensure that BMC Impact Explorer is not installed.


Checks to see that the Task Scheduler service is running.

Cluster installation

If this is a cluster installation, the pre-installation utility checks to see if the following services are running on primary and standby nodes:

  • ClusSvc
  • W32Time
    and ensures that the necessary cluster resources (Cluster Name, Cluster IP, Cluster Disk, and Quorum Disk in the same group) are available.

When the pre-installation check utility finishes, it creates a log file and saves it to your desktop. Review the log file to determine the success or failure of the pre-installation checks. Correct any errors before you launch the installation program. If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any checks that display Not OK, see the [BMC ProactiveNet Troubleshooting Guide|PDFs^ProactiveNet_Troubleshooting_9.0.pdf].


  • No labels