Page tree

This section describes how to upgrade from the BMC ProactiveNet Server 9.0.xx or 9.5.xx to the Infrastructure Management Server 9.6.xx on Microsoft Windows.

Before you begin

  • Ensure that the cluster configuration is of node and cluster disk majority type.
  • Ensure that a visible quorum disk is available.
  • Ensure that the HA installer files are not copied to the shared disk.
  • Ensure that Microsoft Clustering is installed on the target computer.
  • Ensure that before you upgrade, you have migrated the customized KBs in your Infrastructure Management 9.6 implementation. Follow the procedure for executing the KB Migration Wizard described in Migrating the configuration of Infrastructure Management cellsWhen satisfied that the merged KB is working properly, you can begin the server upgrade procedure. Note the directory path of each migrated KB. The directory path should follow this hierarchy structure: /topLevelDirectory/mergedKB/serve/etc/cellName, where /server/etc/cellName is the standard subdirectory.
  • For Windows 2012, ensure that the PowerShell execution policy is running in the unrestricted mode.

    Note

    When you upgrade Infrastructure Management on a 64-bit operating system, the JServer, Rate, and Agent Controller processes use 64-bit JRE, and the Self-monitoring Service process uses 64-bit JRE on Windows and 32-bit JRE on Solaris. If you have already configured the 64-bit JRE processes in an earlier version of Infrastructure Management, they are retained. 

Upgrading to Infrastructure Management Server on the primary node

This section explains the steps to upgrade Infrastructure Management Server on the primary node. Failover is automatically handled by Microsoft Clustering services.

To upgrade the Infrastructure Management Server on the primary node 

  1. Access the installation files from the BMC Electronic Product Distribution (EPD) web siteFor information about downloading the installation files, see Downloading the installation files
  2. Log on to a virtual node, ensuring that you are on the primary node.

  3. Extract the contents of the zipped distribution file to an appropriate directory on the computer where the Infrastructure Management Server is upgraded. 
  4. Open the command prompt with the Run as administrator option. Access the <installerLocation>\Windows\BPPMServer\Disk1 directory (where installerLocation is a directory where you have downloaded installer files) and run the following command:

    install.cmd -J INSTALL_TYPE=PRIMARY

  5. Perform step 4 through step 21 of Upgrading BMC ProactiveNet Server 9.0.xx or 9.5.xx to Infrastructure Management Server on Microsoft Windows

  6. Ensure that the newly upgraded Infrastructure Management Server is shut down on the primary node before starting the installation on the secondary node. 

Upgrading to Infrastructure Management Server on a secondary node

The following procedures explain how to upgrade the Infrastructure Management Server on a secondary node. Failover is handled automatically by Microsoft Clustering services.

To upgrade the Infrastructure Management Server on the secondary node 

  1. Ensure that the Infrastructure Management Server is shut down on the primary node and that cluster control is moved to the secondary node computer.

  2. Log on to a virtual node, ensuring that you are on the secondary node.

  3. Extract the contents of the zipped distribution file to an appropriate directory on the computer in which the Infrastructure Management Server is upgraded. 
  4. On the computer hosting the secondary node, open the command prompt with the Run as administrator option. Access the <installerLocation>\Windows\BPPMServer\Disk1 directory (where installerLocation is a directory where you have downloaded installer files) and run the following command: 

    install.cmd -J INSTALL_TYPE=SECONDARY
  5. On the Welcome page, click Next.
  6. On the Read the License Agreement and Select the Appropriate Option page, select I agree to the terms of the license agreement, and click Next. The upgrade routine automatically checks for the upgrade requirements. If it finds any errors, it displays them on a separate window. You can quit the upgrade process at this point, correct the indicated discrepancies, and then rerun the upgrade. The upgrade routine automatically detects the installation directory of the Infrastructure Management Server.

    Note

    If .NET Framework version 3.0 is not installed, you receive an error message. To install .NET Framework, use the Role Management tool. For more information about how to install the .NET Framework, go to the Microsoft web site. When .NET Framework is installed, the upgrade routine starts to copy the files to the specified directory.

  7. On the Installation Preview window, click Next.
  8. On the Installation Summary window, click View Installation Logs to open the installation logs.
  9. Click Done to exit the upgrade on the secondary node.
  10. Set dependencies for the Infrastructure Management Server cluster resource.
    1. Stop the Infrastructure Management Server by using the pw system stop command.
    2. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and select the cluster name.
    3. Scroll down to Cluster Core Resources, right-click PnService, and select Properties.
    4. In the PnService Properties window, on the Dependencies tab, click Insert to add a resource.
    5. Select the cluster name as a resource, and click Insert.
    6. Select the cluster resource with the AND option, and add other resources (IP address and disk where Infrastructure Management is installed) in the same way.
    7. Click Apply, and click OK.
    8. Restart the Infrastructure Management Server by using the pw system start command. You can restart the secondary node to verify that the cluster service is running on the primary node.

Note

You must set dependencies each time you upgrade the Infrastructure Management Server on a cluster. For example, if you are first upgrading to BMC ProactiveNet Server 9.0.xx or 9.5.xx, you must set the dependencies for the cluster. Then, when you upgrade to Infrastructure Management Server 9.6.00, you must set the dependencies again for 9.6.00.

  • No labels