Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Before you upgrade PerformanceGuard, make sure that you know the hardware recommendations and software requirements.

Important Prerequisites

It's important to be aware of the following before you begin the upgrade process:

  • You must have administrative rights on the computer that you are going to perform the upgrade on (local administrator).
  • The new version of PerformanceGuard may require a different Java JDK and/or Microsoft .NET Framework version than your old one. If the new PerformanceGuard version requires a different JDK and/or .NET Framework version, it is important that you install the required JDK and/or .NET Framework version on the PerformanceGuard server before you install the new version of PerformanceGuard. See also Software Requirements and Install Java JDK.
  • You should install the new version at the same location as the one you are upgrading. Make a note of the location that PerformanceGuard is currently installed at.
  • You must uninstall first and then re-install the newer version when upgrading if you are using service accounts for accessing the database.

  • If you use SQL Server authentication, passwords for the databases must follow the password policy for the SQL Server that you use.

    View Microsoft's SQL Server password policies (link applies for SQL Server 2012, but you can select other SQL Server versions on the page).

  • You can download the server installer for the latest PerformanceGuard version. You can download the server installer for the latest PerformanceGuard version from the CapaSystems wiki.

If You Want to Upgrade a PerformanceGuard Installation that Uses Windows Authentication


If your current PerformanceGuard installation uses Windows authentication for some or all of its services, perform steps 1-5 in the following, but note that during step 5 you should also specify the Windows account(s) that should run the required service(s). Read more details about this under step 5.


Step 1: Stop PerformanceGuard Services

Select  /Start, type services.msc and press ENTER. Then stop these services:

  • PerformanceGuard Backend Server
  • PerformanceGuard Frontend Server
  • PerformanceGuard Web Server
  • PerformanceGuard Web Server 2

Step 2: Backup Database

Backup the existing Backend and Frontend(s) Databases

See Create a Full Database Backup - SQL Server | Microsoft Docs

Step 3: Copy Configuration Files

Copy the configuration files from the existing installation folder:

  • msiproperties.properties
  • collector/conf/config.properties
  • notification/conf/config.properties
  • display/conf/performanceguard.xml
  • display2/display2.yml
  • display2/display2-ssl.yml

Step 4: Run the installer PerformanceGuardServer.exe

Run the installer

The installer should detect the existing installation and show an upgrade Dialog.

After Clicking upgrade the installer removed the old version and read the configuration from the previous version.

Than continue with the installation, See Install PerformanceGuard Server. Run Install Process like a new install except use the existing Database and Parameters

Strange Behavior After Upgrade?

On rare occasions, PerformanceGuard may behave strangely after an upgrade if its cache and work folders were not cleaned up before you started the new version of PerformanceGuard. Fortunately, there's an easy solution if you experience this: See the troubleshooting topic After Upgrade PerformanceGuard Behaves Strangely.


What About PerformanceGuard Agents?

You don't need to upgrade the PerformanceGuard agents that are installed on your organization's computers. Old agents are compatible with new versions of PerformanceGuard.
Should you wish to upgrade your PerformanceGuard agents anyway, you can download the latest version of the PerformanceGuard agent installer from the CapaSystems wiki. Unless your existing agents are very old (version 5.x or earlier), you don't need to remove existing agents before you deploy the new version.

Search this documentation

On this page

In this section

  • No labels