Software requirements for servers that'll run PerformanceGuard:

Operating System

PerformanceGuard requires one of the following operating systems:

• Windows Server 2012 R2 std. edition
• Windows Server 2016
• Windows Server 2019
• Windows Server 2022

A server that runs PerformanceGuard doesn't need to be a member of one of your Windows domains, it can also be a standalone computer.

Java JDK

PerformanceGuard 7.5 and newer uses OpenJDK included in the installation file

Microsoft .NET Framework

Microsoft .NET Framework 4.6 or newer is required in order to run PerformanceGuard.

Database Server

Each PerformanceGuard frontend server and backend server requires a corresponding PerformanceGuard database running on a SQL Server.
The database server software must be installed prior to running the PerformanceGuard server installation. Follow the setup instructions for the selected database software.
The PerformanceGuard database can either be located on a SQL Server instance on the local PerformanceGuard server, on another dedicated SQL server, or on a SQL Server cluster. If you use an existing SQL Server infrastructure, it must be capable of handling the additional IO load from PerformanceGuard.
The SQL Server must be configured to use SQL Server and Windows authentication. You can change the SQL Server's security settings in SQL Server Management Studio: In the Properties dialog for the required SQL Server, select the Security page and locate the Server authentication section.
PerformanceGuard supports the following relational database management systems:

• SQL Server 2012 (CPU license) from PerformanceGuard version 6.1.16
• SQL Server 2014 from PerformanceGuard version 6.5.100
• SQL Server 2016 from PerformanceGuard version 7.0
• SQL Server 2017 from PerformanceGuard version 7.4
• SQL Server 2019 from PerformanceGuard version 7.5 

PerformanceGuard doesn't itself use SQL Server Enterprise features, but you may use them in case you want to utilize more memory on large installations.

Browsers

Browser recommendations for PerformanceGuard web interface:
We recommend that you use the latest version of Google Chrome when you use the PerformanceGuard web interface. You may also use Microsoft Edge.
 

Install Java JDK

Before you install PerformanceGuard on a Windows server, Java JDK 8 must be available on the server.
The installation of SSL for the PerformanceGuard web interface requires that the Java JDK is running on at least Version 8 Update 181.
Only Java JDK 8 can be used. Earlier or later major JDK versions don't work with PerformanceGuard.
Go to www.oracle.com and search for Java SE Development Kit 8 Downloads. Download and then run the Java SE Development Kit 8 .exe file for Windows 64-bit.

1. Go to www.oracle.com, search for Java SE Development Kit 8 Downloads. Download and then run the Java SE Development Kit 8 .exe file for Windows 64-bit.
2. When you have run the .exe file, find the folder C:\Users\[USERNAME]\AppData\LocalLow\Sun\Java\jdk1.8.0_XXX_XXX.

   
   

The folder contains a .msi file with the name jdk1.8.X_XXX (where the X characters represent the exact version of the JDK 8 you have downloaded, for example jdk1.8.0_181.msi).

1. Run the .msi file.

If You Install PerformanceGuard on a CORE Server

If you are going to install PerformanceGuard on a CORE server (a type of Windows server with no graphical user interface (GUI)), download and run the JDK .exe file on another computer that has a GUI, then copy the folder C:\Users\\[USERNAME\]\AppData\LocalLow\Sun\Java\jdk1.8.0_XXX_XXX to the CORE server and run the .msi file there:

msiexec /i jdk1.8.X.XXX.msi

Make sure to change the X characters so that the command refers to the exact version of the JDK that you have downloaded, for example, jdk1.8.0_181.msi.

SQL Server Checklist

Go through this checklist for SQL Server installations before you install the PerformanceGuard databases.
For a list of SQL Server versions supported by PerformanceGuard see Software Requirements.

1. Install SQL Server instance

If you have installed the SQL server with a named instance, make sure the service SQL Server Browser is running. This will ensure that you can connect to the SQL Server with the server name and instance name. If this service is not running, you will need to know which port your named instance is running on and use this in the connection string.

1. Make sure to install SQL Server Management Studio.

You'll need SQL Server Management Studio for configuring the SQL Server and for troubleshooting any problems, so make sure that you include SQL Server Management Studio when you install SQL Server. If in doubt about how to install SQL Server Management Studio, go to msdn.microsoft.com and search for Install SQL Server Management Studio.

1. SQL Server instance properties: Make sure that your SQL Server instance uses a case-insensitive server collation. A collation is a set of rules that specify how a language (such as Greek) or a character set (such as Latin1_General) is used by the database. If the server collation isn't case-insensitive, the PerformanceGuard database creation might fail.

You can check whether server collation is case-insensitive by opening the properties of your SQL Server instance in SQL Server Management Studio: If the server collation name on the General the page contains the element CI (see highlight in the illustration), it means that the collation is case-insensitive.
For Western European countries we recommend using the collation SQL_Latin1_General_CP1_CI_AS.
Click thumbnail to view the image in full size.

My server collation isn't case-insensitive. How do I change it? Go to msdn.microsoft.com and search for Set or Change the Server Collation.
Then, on the SQL Server properties' Security page, make sure that SQL Server and Windows authentication mode is selected.

1. sa login credentials: Under your SQL Server instance in SQL Server Management Studio, expand Security, then expand Logins. Right-click the sa account, and select Properties. Select the Status page, and make sure that Permission to connect to database engine is set to Grant, and that Login is set to Enabled.

Also, verify that you know the password for the sa log in—or that your database administrator (dba) knows it.

1. SQL Server Configuration Manager properties: Open SQL Server Configuration Manager and expand the Network Configuration section for your SQL Server instance. Right-click the TCP/IP protocol, select Properties and verify that TCP/IP is enabled.

Then select the dialog's IP Addresses tab and enable a network adapter of your choice. Clear any TCP Dynamic Ports for the adapter in question, and use a fixed port like the default TCP Port 1433 instead.

1. SQL Server network connectivity: If PerformanceGuard is going to be installed on another computer than the database server, verify that you can log in to the SQL Server database instance from the computer that's going to run PerformanceGuard. Make sure to use a valid DNS hostname for the SQL Server when you connect from PerformanceGuard services.