Page tree
Skip to end of metadata
Go to start of metadata

Before you install the Fix Pack, perform the following steps:

BMC ProactiveNet server

  • (UNIX) Ensure that x11 is installed and configured. Both 32-bit and 64-bit RPMs must be installed.
  • (Windows) Ensure that:
    • Disable User Account Control (UAC) and turn off Data Execution Prevention (DEP) for install.cmd.
    • Stop the BMC ProactiveNet Server and restart the host machine to unlock any process running in the background.
  • (Solaris) If you are upgrading from Fix Pack 1 to Fix Pack 2, correct the environment variable BPPM_SERVER_HOME in the InstalledDirectory/etc/bmc.profile and InstalledDirectory/etc/bmc.chrc files such that it points to the Fix Pack 1 installation folder.
  • If installing on a virtual machine (VM), back up the VM before installing the Fix Pack.
  • If installed on a physical computer, back up the complete BMC ProactiveNet Server installation, so that the original BMC ProactiveNet Server installation can be restored in case of an issue with the Fix Pack installation. For more information, see backing up the installation on Windows or UNIX.
  • Back up critical installation and database files. For more information, see for Oracle and for SAP Sybase SQL Anywhere.
  • If you are using an Oracle database, ensure that it is running before and during installation of the Fix Pack on the BMC ProactiveNet Server.
  • Ensure that the BPPM_SERVER_HOME environment variable is set to the server installation directory. For example, on a Windows computer, this environment variable is set to C:\Program Files\BMC Software\ProactiveNet.

To back up the BMC ProactiveNet Server files on Microsoft Windows

  1. Check the size of the InstalledDirectory\ProactiveNet\pw folder and verify that you have sufficient disk space for the backup.
  2. Stop the BMC ProactiveNet Server by running the pw system stop command.
  3. Ensure that none of the processes are running by running the pw process list command.
  4. Create an archive of the BMC ProactiveNet Server installation directory. For example, if the BMC ProactiveNet Server is installed at C:\Program Files\BMC Software\ProactiveNet, create an archive of the entire ProactiveNet directory.

To back up the BMC ProactiveNet Server files on UNIX

  1. Check the size of the InstalledDirectory/ProactiveNet/pw folder and verify that you have sufficient disk space for the backup.
  2. Stop the BMC ProactiveNet Server by running the pw system stop command.
  3. Ensure that none of the processes are running by running the pw process list command.
  4. Create an archive of the BMC ProactiveNet Server installation directory. For example, if the BMC ProactiveNet Server is installed under /opt/bmc/ProactiveNet/pw then go to /opt/bmc/ProactiveNet and run the following command:
    tar -cvf <backupfilename>.tar pw

Remote Integration Service and remote cell

  • Back up your current installations of all Integration Services connected to the BMC ProactiveNet Server. See To back up the Integration Service files.
  • (UNIX) If you installed BMC ProactiveNet 9.6 Fix Pack 1 (9.6.00.001) and configured TLS on the Integration Service, back up the following files:

    /etc/patrol.d/_opt_bmc_TSIMAgent_pw/security_policy_v3.0/bppmpis.plc

    /opt/bmc/TSIMAgent/pw/patrol/common/security/keys/access
     

To back up the Integration Service files

The local Integration Service files are backed up when you back up the BMC ProactiveNet Server files. You need to manually back up all the remote Integration Services that are connected to the BMC ProactiveNet Server. The default installation paths are:

  • (Windows)  \Program Files\BMC Software\BPPMAgent 
  • (UNIX)  /opt/bmc/BPPMAgent

Check the size of the installation directory and verify that you have sufficient disk space for the backup.

Where to go from here

Related topic

Downloading the Fix Pack

9 Comments

  1.  

  2.  

    1.  

  3.  

    1.  

  4.  

  5.  

  6. hi,

    just a comment:

    (Windows) Ensure that:

    • Disable User Account Control (UAC) and turn off Data Execution Prevention (DEP) for install.cmd.

    DEP cannot be configured for .cmd files, only .exe

    cheers rop

    1. Hello Roland,

      Thanks for the feedback.

      While you cannot browse and select non .exe files, you can enter the file name and it gets picked up and listed in the DEP-exclusion list.