Installation Procedure for MS Windows

The following procedure is used to install the Management and/or Monitoring Server components onto a machine running the MS Windows® operating system.

If required, the Windows Client and/or Web Application can also be installed with the server onto the same machine. To do this, select the required client components along with the server at Step 4.

Administrator rights are required for the machine onto which the Prognosis Server is being installed.

Download the installer to a local hard disk and then run the Prognosis 11.7.0.exe file.

The exe file is a self-extracting executable that will extract into a folder named 'Prognosis 11.7.0'. On slow machines this may take a few minutes. Once extracted, the folder will contain:

- Backup-restore folder

- MST folder

- Prerequisites folder

- Prognosis 11.7.0.msi

- Setup.exe

Should the installation files be provided by way of a DVD, place the disk into the DVD drive of the required machine, if Autorun is activated the DVD will start the installation automatically. If the installation fails to start, go to Windows Explorer, select the DVD drive, copy the installer to a local drive and then run the Prognosis 11.7.0.exe file.

Setup.exe will now run automatically and check for the required Installation Checklist for MS Windows.

a)   If the pre-requisite software is not found on the destination machine, it will be automatically installed. This may result in some non-Prognosis dialog boxes being displayed, but normally it will only be necessary to 'click' through these until the software has been installed.

b)   If the required pre-requisite software is found on the destination machine, or after it has been installed, the Welcome dialog will open.

Click the Next button to proceed.

End-User License Agreement

The next step in the installation is the acceptance of the End-User License Agreement (EULA).

Carefully read the End User License Agreement and then click the checkbox to accept the terms and conditions.

The 'Send usage data to IR' option will be selected by default. Please read these conditions and if this is not acceptable, uncheck the adjacent checkbox. For further details see the Usage Analytics.

The Next button will become active once the License Agreement has been accepted and can then be selected to continue with the installation.

If the End-User License Agreement (EULA) is not acceptable, click the Cancel button and the installation will be aborted.


The installation will now request the Prognosis License File information.

In most cases, the license information is sent by email as an attached text file. When received, it is recommended that the license file be saved to the same folder as the Prognosis installation files

The License dialog box will default to the same folder path as the installation files, should the license be located elsewhere or should an invalid license be found, an alternative license location can be specified or browsed for.

The license field may be left blank. However, this will only allow the Prognosis Windows Client to be installed.

When completed click the Next button to continue.

Prognosis Components

From this dialog box select the components that are to be installed on this machine. For details about each component see the Prognosis Components.

If deciding not to install the Web Application or Windows Client on this server during the installation, it will not be possible to install these components at a later date without performing a Prognosis uninstall and re-install on this system. As well, when upgrading the system, it will not provide the options to install these components.

a)   To only install the Prognosis server components check:

the Management and/or Monitoring Server options (leave other options unchecked).

It is recommended to use the Management Server at all tiers in the topology for Payments or Infrastructure environments. For further details refer to Management and Monitoring Server Differences.

b)   To add one or both client components check either or both of the following options:

Windows Client

Web Application

In order to select the Web Application option, a Management or Monitoring Server component must also be selected. A warning message will be displayed if it is not.

Click the Next button to continue.

Destination Folder

This dialog box is used to assign the folder path where this copy of Prognosis will be installed.

Check that the default path shown in the Destination Folder field is where you wish Prognosis to be installed. If not, click the Browse button where an alternative folder path can be specified.

Please note the following:

  • Prognosis cannot be installed into any of the following folders of an MS Windows machine:

- /Program Files
- /Program Files (x86)
- /Users
- /Documents and Settings

This is because Prognosis needs to save/modify files in its installed location as the logged in user. In MS Windows, problems can occur when trying to do this unless the user is an administrator, which may not be the case.

  • Prognosis cannot be installed into an existing folder. A new folder must be created.

Absolute file name length cannot exceed 258 characters. As the relative path and field names of the Prognosis packaging can reach up to 210 characters, it is strongly recommended to limit the absolute path for the Prognosis home installation folder to 45 characters.

Click the Next button to continue. If a new folder name has been entered Prognosis will now create the new folder.

Prognosis Web Application Port

The following dialog box will only appear when the Web Application component has been selected and the default port 443 is already in use. When the default port is found to be in use, the Prognosis installer will try to find an alternative port starting with 8080 and incrementing by 1 up to 8089. When one of these ports is found to be available, it will be shown in the input field on this dialog box, if none of these ports are found to be available, the input field will be empty.

If the installer nominated port number is acceptable, click the Next button to proceed.

If the nominated port number is not acceptable, an alternative user-selected port number can be entered. In this case, after clicking the Next button, the installer will check the port number for both formats (digit only and < = 65535) and availability. If the format is incorrect the following warning message will be displayed and if the port is unavailable the Prognosis Web Application Port dialog box will be redisplayed.

Ready to Install Prognosis

This dialog box confirms that all the installation settings that have been made and that Prognosis will make any necessary Firewalls changes. If the Web Application component has been included it will confirm the port that has been configured.

If any changes are required click the Back button to return the required dialog and make the necessary adjustments.

If you are satisfied with the settings, click the Install button to begin copying the installation files to the nominated folder.

When the installation is complete the final dialog box will be shown

Click the Finish button to complete the installation.

The Prognosis installation may include new drivers. These drivers may not become effective until after the next reboot of the Windows Server. If a reboot is required, a prompt will be shown advising that a reboot of the machine can be made now or later.
Prognosis PASSWORDS Configuration entry
During installation on a Windows platform, a 'Prognosis' entry will be added to the Prognosis PASSWORDS Configuration. This entry is used by Analysts and Thresholds (and is used by the default Windows Analyst) to tell Prognosis to run commands with the Local System Account (NT AUTHORITY/SYSTEM) and not the user that started the Analyst. As such, it is recommended that the SECURITY Configuration be modified to limit access to this PASSWORDS Configuration entry to specific users.


After the installation has been completed, there are a number of configuration steps that need to be undertaken.

  • Management Server
    If a Prognosis Management Server is being used with remote Monitoring Servers, it will be necessary to configure the Management Server to see the other machines. To do this see the Setup a Management Server topic.

  • Monitoring Server
    Each Monitoring Server may need vendor specific configurations for the type of data monitoring that it will be undertaking. Please refer to the Configuration for further directions.

Provide feedback on this article