Walkthrough: Upgrading to the latest version for Microsoft Windows

Upgrading using the unified product installer

The unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server and the TFTP server in your environment. If you have selected TrueSight Server Automation Console Upgrade Service option, the console is also automatically upgraded; otherwise, you must manually upgrade it. The checklist below walks you through the process of upgrading Windows and Linux environments using the unified product installer.

In TrueSight Server Automation 8.9.03 and later, you can choose not to upgrade certain consoles. To enable this backward support for any specific Application Server, you must use the blasadmin command versioncompabilitycheck to turn off the version compatibility check that occurs whenever you access a Console. For more information, see To enable communication with clients of an earlier version of TrueSight Server Automation.

Step 1: Review requirements and limitations

The first step is to review the following requirements and limitations when using the unified product installer for product upgrade.

Requirements

Limitations when using the unified product installer

Step 2: Prepare the environment for upgrade

Related topic: (See these topics for additional upgrade considerations and supported upgrade paths)

Preparing-for-a-Windows-upgrade-using-the-unified-product-installer

Minimum-software-requirements

Step 3: Download the files

Download and extract the installation files to a temporary location.

1. Download and extract the TSSA<version>-WIN64.zip file (for example, TSSA89-SP4-WIN64.zip), which contains the unified product installation program files) to the host computer of the Application Server that was set up as a configuration server.
2. Download and extract the TSSA<version>-RSCDAgents.zip (for example, TSSA89-SP4-RSCDAgent.zip) file from the package and copy the rscd folder to ../TSSA<version>-WIN64/Disk1/files/installers/ before running the unified product installer. The unified product installer uses the RSCD installers while installing or upgrading TrueSight Server Automation in your environment.

Step 4: Run the unified product installer on the Application Server

When you run the unified product installer on the Application Server, the unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server, and TFTP server in your environment, with certain exceptions. Before running the upgrade, back up your database and inform your users that TrueSight Server Automation will be unavailable during the upgrade.

1. Navigate to the temporary directory that contains the installation files. 
2. Do one of the following:
   
   • Run the following command:
     setup.exe

   • (Optional) Provide the parameters with the command to upgrade all or any of the following artifacts: ZipKits, blconnect, compliance content, and quick start page
     The following table describes these parameters:

     Parameter name	Description
     -J IMPORT_ZIPKITS	ZipKit packages are used for operating systems and common enterprise applications and databases.
     -J IMPORT_BLCONTENT	The blconnect script is used to create groups, folders, and smart groups that are commonly used by organizations.
     -J CREATE_CONTAINER_COMPLIANCE_ARTIFACTS	SCAP container compliance jobs are created.
     -J ENABLE_QUICK_START_PAGE	The Quick Start page supports the common use cases of .

     Example: To upgrade all these artifacts, run this command:
     setup.exe -J IMPORT_ZIPKITS=true -J CREATE_CONTAINER_COMPLIANCE_ARTIFACTS =true -J ENABLE_QUICK_START_PAGE=true

     If you do not provide any of these parameters, these artifacts are not upgraded.
     

3. Run the installation program (setup.exe for Windows)
   Note: For Windows 2008 or later, right-click the installer file and select Run as administrator.
4. Select the language in which you want to run the installer and click OK. 
   Note: If problems arise during the upgrade, the on-screen error messages contain instructions and guidance to help you troubleshoot the problems, and further information is available in the log files.
5. Read through the basic information about the unified product installer and the types of nodes that are installed in the environment.
   
6. Click Next.
7. Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement, and then click Next. 
   
   Read the copyright statement and select I agree to the terms of the license agreement, and then click Next.

8. Enter your Authentication profile credentials to proceed with the upgrade procedure.

   The profile that you specify must be associated with the same Application Server where you are performing the upgrade. Note that only secure remote password (SRP), LDAP, or Domain Authentication type profiles can be used with the unified product installer. 
   
    

9. Review the TrueSight Server Automation infrastructure discovered in your environment.

   This includes the different types of servers that are present in the TrueSight Server Automation environment, their count, and their status. If your environment includes PXE servers, the installer upgrades the PXE server automatically, if it is up and running during the infrastructure discovery phase.  
   
   If you are running one or more remote PXE servers (that is, on a different subnet than the Application Server), the installer detects and lists them as part of your infrastructure. The unified product installer upgrades the remote PXE servers as part of the upgrade process. The checkbox for the Remote Site field controls how the PXE server installer files are copied to the PXE server, as described in the table below.

   PXE upgrade option	Explanation
   Remote Site field selected (default)	Selecting the checkbox assumes that you have previously manually copied the PXE installer binary (..\installers\pxe_64\PXE<version>-WIN32) to the %SystemDrive%/BSAInstallerDumpDir on the PXE server prior to upgrading. The unified product installer validates the existence of the PXE installer binary under the expected location, and upgrades the PXE server during the upgrade process. For performance reasons, this option is strongly recommended for PXE servers that are on a different LAN/WAN than the Application Server.
   Remote Site field cleared (not selected)	Clearing the checkbox assumes that you want the installer to copy ..\installers\pxe_64\PXE<version>-WIN32 file to the remote host, to the %systemDrive%\BSAInstallerDumpDir folder. De-select the Remote Site option if the PXE server is on the same LAN/WAN as the Application Server. However, note that clearing the checkbox is typically much slower if thePXE server is on a different LAN/WAN than the Application Server.

10. Click Next.

1. Preview the upgrade.
   
2. Select the I acknowledge that the installer will bring down the TrueSight Server Automation environment for upgrade check box.
3. Click Install.

1. If you encounter a failure, fix the underlying cause and re-run the installer. When you see the re-attempt panel, review the information and then click Install. 
2. When the upgrade is finished, review the summary and the upgrade log, and then click Done. 
    

Step 5: Manually upgrade additional components

After the unified product installer completes the upgrade, manually upgrade any components that meet the following criteria. Perform this step anytime after the upgrade.

• NSH clients on non-Application Server host computers - Use the instructions in Upgrading-the-Network-Shell-on-Windows.
• PXE and TFTP servers that reside on separate host computers - When you upgrade a PXE server on a different subnet than the target server, you need to copy the installation files to the remote machine and upgrade the remaining servers manually, as described in Upgrading-a-PXE-server-on-Windows or Upgrading-a-PXE-server-on-Linux-or-UNIX.
  If the TFTP service is not started automatically after the upgrade, manually start it, as described in Starting-and-stopping-a-TFTP-server.
• Upgrade any agents that you may have that fall into the following categories. 
  • Agent on an online or offline patch repository
  • Agent on a basic/standard repeater
  • Agent on a VMware vCenter server. You must upgrade the agent on the vCenter server before you try to use the vCenter integration or the updated VMware configuration object push. For more information, see Setting-up-a-VMware-vSphere-environment and Distributing-configuration-objects.
• If you have not selected the TrueSight Server Automation Console Upgrade Service option, upgrade all the  consoles manually in your environment to match the version of the Application Server. For more information, see Upgrading-the-TrueSight-Server-Automation-Console-on-Windows.

Related topics

Upgrading-the-RSCD-agent-on-Linux-and-UNIX

Upgrading-the-RSCD-agent-on-Windows

Step 6: Perform additional post-upgrade tasks

At any time after the upgrade, complete the following tasks, if they apply to your environment:

Related topics

Walkthrough-Upgrading-using-the-configurator-and-individual-component-installers

Walkthrough-Upgrading-to-the-latest-version-for-Linux