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

General preparations for all operating systems



System requirements

Ensure that the target computers for BMC ProactiveNet meet or exceed the system requirements listed in System requirements and product compatibility and in the following sections.

Port 80

Ensure that port 80 is available for installing the Apache web server. If any other application is using the port, change the port allocation to make the port 80 available for BMC ProactiveNet installation. On the system where you want to host the BMC ProactiveNet Server or the BMC ProactiveNet Integration Service, verify the TCP control port (port 80) availability by running the following command from a command line:

netstat -a | grep "LISTENING" | grep "80"

After BMC ProactiveNet has been installed, you can change the port for the Apache web server to free port 80 for use by your other application. For instructions, see Ports used by BMC ProactiveNet.

Installation media

BMC Software recommends that you install BMC ProactiveNet from a local copy of the installation image and not from a network drive. Installing from a network drive can cause delays in completing the installation.

Host Name

For successful installation, ensure that the host name or the cluster name does not contain an underscore (_).

BMC recommends that you have a dedicated host computer for BMC ProactiveNet and do not install any other applications on it.

Preparations for Microsoft Windows operating system



Installation user

Ensure that the user running the installation program has administrator rights and permissions and is a member of the Administrators group on the target computer.

Installation on European locals

While installing BMC ProactiveNet on Microsoft Windows Operating System in European locales (French, German, and Spanish), ensure that you do not change the default localized Administrators group name. BMC ProactiveNet installation works with only the default localized Administrators group names. For example:

  • English: Administrators
  • German: Administratoren
  • French: Administrateurs
  • Spanish: Administradores

Windows patch level

Ensure that the target computer has the most recent patch level for supported Windows operating systems. If it does not, use Microsoft Update (or Windows Update) to update it. For supported versions, see System requirements and product compatibility.

Users with administrator privileges

If you want users with administrator privileges (not the Administrator user) to access the BMC ProactiveNet Server after the installation, you must turn off the User Access Control (UAC) before you install the server.

Installation directory

Do not install BMC ProactiveNet Server in a root directory (for example C: or D:), on a shared drive, or in the Documents and Settings folder.


Perl should not be installed on the target computer where BMC ProactiveNet Server is being installed.

Preparations for Linux/Solaris operating systems



Installation user

Ensure that the user running the installation program is root.


Ensure that gzip is installed and present in the PATH environment variable.

Installation directory

The installation script creates the installation directory during installation.


The directory where the BMC ProactiveNet Server is installed and all its parent directories must have 755 permissions and must be owned by root, as well as the other group. Without these permissions and ownership, you will not be able to log into the BMC ProactiveNet Server.

BMC ProactiveNet Integration Service

Do not install the BMC ProactiveNet Integration Service in the /usr directory.

  • No labels