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.

Upgrading the Application Server on Windows

An upgrade of the Application Server on Windows upgrades both the Application Server and the Network Shell.
Upgrading the Application Server does not upgrade the BMC Server Automation Console, the RSCD agent, the PXE server, or the file server. You must upgrade those components separately.

Note

  • You must upgrade the Application Server and BMC Server Automation Console to the same version, whether they are located on the same computer or different computers.
  • If the Application Server and the BMC Server Automation Console are on the same computer, you must upgrade the Application Server before upgrading the console.
  • If you are upgrading from version 7.6.xx or 7.7.xx, you should be aware that the upgrade changes the location of your installation directory. The upgrade process keeps the old version's installation location and creates an NSH directory there. Then the upgrade moves user files to the NSH folder and copies new files there. For example, if the old version's installation location is C:\Program Files\BMC BladeLogic\OM, the upgrade moves it to C:\Program Files\BMC BladeLogic\OM\NSH.

If the host computer on which you are installing the Network Shell has:

  • A supported version of Perl installed — The Network Shell installation automatically installs the Network Shell Perl module. (For information about the Perl versions that BMC Server Automation supports, see Perl support.)
  • An unsupported version of Perl installed — The installation copies files that enable you to install the Perl module after you have installed the supported version of Perl.

To perform a silent upgrade of an Application Server, see Using-silent-mode-to-upgrade-the-Application-Server-Windows.

Before you begin

  • To perform the upgrade of the Application Server, you must have local Administrator privileges.
  • If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on Windows 2003 or 2008, you must use one of the following options:
  • On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.
  • If you have not already done so, stop the Application Server.
  • If there is an agent on the Application Server, upgrade the agent before you upgrade the Application Server. These components must be at the same version level.
  • If the file server is not on the Application Server, upgrade the file server before you upgrade the Application Server.
  • Perform the upgrade steps in this order:
    1. Shut down the Application Server.
    2. Upgrade the RSCD agent.
    3. Verify that the agent is running and has been upgraded by running the following command: agentinfo <serverName>
    4. Upgrade the Application Server.

To upgrade the Application Server on Windows

  1. Navigate to the directory that contains installation files and run the installation program for BMC Server Automation. (Installation program names follow the convention: BBSA<version>-<platform>.

    Note

    BMC Server Automation does not support multiple instances of the Application Server on the same machine.

  2. In the Setup Type window, select Upgrade, and then click Next.
  3. To complete the upgrade to your installation, click Finish.

Related topics

Release-notes-and-notices

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*