Upgrading product components on Microsoft Windows
The following topics provide information about upgrading the individual components of the TrueSight Server Automation system on Microsoft Windows, using the component installers.
Step | Description |
|---|---|
Review the supported upgrade paths and upgrade considerations and perform the preliminary upgrade steps, such as shutting down the TrueSight Server Automation environment and backing up the installation directories for all Application Servers and PXE servers. You must also download the installers (see Downloading-the-installation-files). | |
Run the configurator utility on all Application Servers and PXE Servers to migrate configuration data. | |
Do not restart the Application Server until you complete the database migration. Note that an upgrade of the Application Server also upgrades the Network Shell. | |
Run the postmigration (.exe or .sh) file to update BLPackages that refer to old Group Policy Object (GPO) assets or to migrate rules. | |
Upgrade at least one TrueSight Server Automation Console. Note: As of version 8.9 of TrueSight Server Automation, you can choose not to upgrade certain consoles. For more information, see To enable communication with clients of an earlier version of TrueSight Server Automation. | |
If you have upgraded the provisioning server (the Application Server enabled for provisioning), upgrade the components that TrueSight Server Automation uses in provisioning operating systems to bare metal machines. | |
Upgrade the other TrueSight Server Automation Application Servers, consoles, RSCD agents, and other components in your enterprise (including on any file servers or virtual servers). Note: If the TrueSight Server Automation file server resides on a different computer from the Application Server, upgrade the RSCD agent on the computer on which file server resides. The file server and the database must be at the same version before you run TrueSight Server Automation. | |
Upgrade any custom configuration objects that you have created and distributed. You can perform this step at any time after the upgrade. Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. |