PI Data Collection Manager release notes

2.8.6.2

Overview

PI Data Collection Manager 2.8.6.2 is a maintenance release that contains only bug fixes and enhancements.

Fixes and Enhancements

Fixes

This section lists items that were resolved in this release of the PI Data Collection Manager:

Enhancements

This section lists enhancements as part of the PI Data Collection Manager release:

• You can install the PI Data Collection Manager using a passwordless virtual service account or a local/domain account.

Known Issues

There are no known issues with this release of the PI Data Collection Manager.

System Requirements

Operating Systems

This product is a 64-bit application.

Distribution Kit Files

Installation and Upgrade

Installing PI Data Collection Manager

PI Data Collection Manager can be installed or upgraded using the PI Data Collection Manager installation kit (PI Data Collection Manager_2.8.6.2_.exe). This installation kit can be obtained by using the How to Download Products link listed in the Customer Portal How To's list. This list is located on the Customer Portal site.

For additional information regarding the PI Data Collection Manager installation, refer to the Install PI Data Collection Manager section of the PI Connector Administration Guide. This guide is located in the PI Connectors section of the AVEVA Documentation Library and can be downloaded from the Customer Portal site.

Uninstalling PI Data Collection Manager

For instructions on uninstalling the PI Data Collection Manager, refer to the Uninstall PI Data Collection Manager section of the PI Connector Administration Guide.

Security information and guidance

We are committed to releasing secure products. This section is intended to provide relevant security-related information to guide your installation or upgrade decision.

We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release. The tables below provide an overview of security issues addressed and their relative severity based on standard scoring.

Overview of New Vulnerabilities Found or Fixed

This section is intended to provide relevant security-related information to guide your installation or upgrade decision. We proactively disclose aggregate information about the number and severity of the security vulnerabilities that are fixed in this release.

For this release of PI Data Collection Manager, two security vulnerabilities have been identified and fixed. The table below provides an overview of the types and severities of security fixes.

Security vulnerabilities fixed

• Upgrade OWIN to version 4.2.2

• Upgrade moment to version 2.29.4

  Severity Category	CVSS Base Score Range	Number of Fixed Vulnerabilities
  Critical	9 - 10	0
  High	7.0 - 8.9	1
  Medium	4.0 - 6.9	2
  Low	0 - 3.9	0

  This table lists the known vulnerabilities along with their mitigation in this product.

  Component	Version	CVE or Reference	CVSS	Mitigation
  Bootstrap (Twitter)	3.4.1	CVE-2024-6484	8.4	Vulnerable code is not in execution path.
  Bootstrap (Twitter)	3.4.1	CVE-2024-6485	8.4	Vulnerable code is not in execution path.
  System.Text.Json	6.0.0	CVE-2024-30105	6.5	Vulnerable code is not present
  JSON Web Token Handler for the Microsoft .NET Framework 4.5	6.19.0	CVE-2024-21319	5.9	Vulnerable code is not in execution path.
  azure-activedirectory-identitymodel-extensions-for-dotnet	6.19.0	CVE-2024-21319	5.9	Vulnerable code is not in execution path.

  This table lists the security vulnerabilities outstanding for this product.

  Component	Version	CVE or Reference	CVSS	Mitigation
  jQuery	3.5.1	BDSA-2021-3651	3.0	Deferred as risk is low

Technical support and feedback

For technical assistance, contact AVEVA Technical Support at +1 510-297-5828 or log a case through the Customer Portal. Additionally, the Contact Us page on the portal offers contact options for customers outside of the United States.

When you contact AVEVA Technical Support, be prepared to provide this information:

• Product name, version, and build numbers

• Computer platform (CPU type, operating system, and version number)

• Time that the difficulty started

• Log files at that time

• Details of any environment changes prior to the start of the issue

• Summary of the issue, including any relevant log files during the time the issue occurred