Reference Number |
Related Article |
Found PIA |
Fixed PIA |
Issue Description |
EPO-6549 | KB91682 | 3.1.0.144 | 3.1.0.189 |
Issue: When you run PIA tool version 3.1.0.144, the Installation fails with the error below:
Resolution: PIA 3.1.0.189 (posted July 22, 2019) contains updated signed certificates that resolve this issue. The updated tool is now available as a standalone package from the Product Downloads Site and the ePO Software Catalog, and can be installed in the normal way. Workaround: See the related article for details. |
EPO-6488 | KB91589 | 3.1.0.144 | 3.1.0.189 | Issue: PIA 3.1.0.144 crashes while performing database checks, when the database name is more than 50 characters long. Resolution: PIA now correctly handles database names longer than 50 characters. |
1258139 | - | 3.1.0.140 | 3.1.0.144 | Issue: PIA 3.1.0.140 crashes while it interrogates the database collations. |
TSET-4108 | KB91798 | 3.1.0.189 | - |
Issue: PIA crashes when running checks with PIA 3.1.0.189. The event log records the error below:
|
ePolicy Orchestrator Pre-Installation Auditor Known Issues
Technical Articles ID:
KB88906
Last Modified: 1/30/2024
Last Modified: 1/30/2024
Environment
NOTE: The
Summary
Recent updates to this article
Product Release
To view available release notes, visit the Product Documentation site.
* Only major builds of the PIA tool are released with updated Release Notes.
IMPORTANT:
Contents
Click to expand the section you want to view:
Date | Update |
January 30, 2024 | Added PIA 3.1.0.295 to the Product Release table. |
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Product Release
To view available release notes, visit the Product Documentation site.
Product Version | Release Date |
PIA 3.1.x | |
3.1.0.295 | January 30, 2024 |
3.1.0.282 | April 4, 2023 |
3.1.0.227 | Released to Support (RTS) |
3.1.0.222 | August 11, 2020 |
3.1.0.189 | July 22, 2019 |
3.1.0.144 | December 5, 2018 |
3.1.0.140 | September 18, 2018 |
3.1.0.133 | August 28, 2018 |
3.1.0.129 | August 14, 2018 |
PIA 2.2.x | |
2.2.0.129 | March 1, 2018 |
2.2.0.126 | December 14, 2017 |
PIA 2.1.x | |
2.1.0.106 | September 6, 2017 |
PIA 2.0.x | |
2.0.0.320 | April 26, 2017 |
2.0.0.310 | March 15, 2017 |
2.0.0.295 | March 14, 2017 |
* Only major builds of the PIA tool are released with updated Release Notes.
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.
IMPORTANT:
- Before you install ePO, we recommend that for standalone use of the PIA tool, you should always download the latest ePO PIA tool from either of the following:
- Product Downloads site
- ePO Software Download Manager or Software Catalog
- The ePO PIA tool is bundled with the ePO installer starting in ePO 5.10.0. For the ePO 5.10.0 installer to use the latest ePO PIA tool, follow the steps below:
- Download the ePO PIA tool from one of the locations stated above.
- Unzip the PIA tool and copy the executable to the folder where the ePO installation files are copied.
- Move or copy the existing PIA tool executable to a different folder. Also, copy the new PIA tool file to the ePO installer directory.
- Run the ePO installer (
setup.exe ) and follow the instructions.
Contents
Click to expand the section you want to view:
Reference Number |
Related Article |
Found PIA |
Fixed PIA |
Issue Description |
EPO-9298 | - | 3.1.0.189 | 3.1.0.227 (RTS) |
Issue: When you use the PIA tool 3.1.0.189, the temporary sample user isn't deleted. Resolution: With PIA 3.1.0.227, no sample user is displayed in the |
EPO-8958 | KB93066 | - | 3.1.0.222 | Issue: The PIA tool doesn't undertake a collation check after it performs a disaster recovery snapshot restore procedure. |
EPO-8999 | - | - | 3.1.0.222 | Issue: The ePO change password window doesn't display after you change your password. This issue is seen when the password doesn't match the criteria set from the PIA tool. |
1257036 | - | 3.0 | 3.1.0.144 | Issue: Running the PIA tool against the SQL database disables the Resolution: The Preinstall auditor tool now turns off |
1254740 | - | - | 3.1.0.144 | Issue: The PIA check named 'Database High Availability/Disaster Recovery' directs you to the wrong article. Resolution: The update now directs you to KB86152. |
1258515 | - | - | 3.1.0.144 | Issue: The PIA tool shows a failure for the high availability check if |
1255499 | - | - | 3.1.0.144 | Issue: The PIA tool runs against SQL 2016 or later, shows a warning for trace flag 1118, although the trace flag 1118 isn't applicable for SQL 2016 and later. |
1252001 | - | 3.1.0.129 | 3.1.0.140 | Issue: PIA incorrectly shows a database compatibility level of 100 as a pass when it looks for an upgrade to ePO 5.10. |
1253067 1253055 |
- | 3.1.0.129 | 3.1.0.140 | Issue: An SQL Collation check, which is needed for ePO 5.10, is missing from PIA. |
1250023 | - | 3.1.0.129 | 3.1.0.133 | Issue: A keystore validation error displays if the |
1240766 | - | 2.2.0 | 3.1.0.129 | Issue: Using a domain account to connect to the SQL Server fails when you don't use the default port, even when the correct port is displayed. |
1235726 | - | 2.0.0 | 3.1.0.129 | Issue: ePO upgrade is interrupted when ePO Database mirroring is enabled during an upgrade. |
1221922 | - | 2.2.0 | 3.1.0.129 | Issue: A |
1182562 | KB88745 | 2.2.0.126 | 3.1.0.129 | Issue: The ePO installer doesn't continue the installation process if a needed Windows update isn't installed correctly. (This issue occurs if some Windows updates aren't present on the server.) |
1226131 | - | 2.1.0.106 | 3.1.0.129 |
Issue: While running checks, PIA stops working (crashes) in some environments.
The
Application event log records the following:
Application crash event: 1000, Faulting application name: ePIP.exe, version: 2.1.0.106, time stamp: 0x5964ab59 Faulting module name: ePIP.exe, version: 2.1.0.106, time stamp: 0x5964ab59 Exception code: 0xc0000005 Fault offset: 0x0012af59 Faulting process id: 0xdd0 Faulting application start time: 0xePIP.exe0 Faulting application path: ePIP.exe Faulting module path: ePIP.exe |
1227048 | - | 2.2.0.126 | 2.2.0.129 |
Issue: PIA fails to connect to SQL in some environments, even though valid information is provided. The following error is displayed:
|
1222455 | - | 2.2.0.295 | 2.2.0.126 | Issue: PIA 2.2 stops working (crashes) while it collects SQL information. |
1197370 | - | 2.0.0.320 | 2.1.0.106 | Issue: PIA can stop working when run in the ePO server. |
1198152 | - | 2.0.0.320 | 2.1.0.106 | Issue: RSA check is missing from the PIA checklist. |
1184061 | - | 2.0.0.320 | 2.1.0.106 | Issue: PIA can stop working when you change the password in the tool. |
1199491 | - | 2.0.0.320 | 2.1.0.106 | Issue: PIA returns incorrect platform or ePO version information about Japanese Windows operating systems. |
1176225 | - | 2.0.0.310 | - | Issue: The upgrade time displays an incorrect output if the ePO data is unusually large. Cause: The ePO upgrade process takes a backup of vital folders. With a good computer, and little data in the ePO DB folder, this process takes about 30 minutes. It then continues to the database upgrade. If the configuration data in the DB folder or on the computer is low-end or unusually large, backup can take an extended amount of time. These scenarios aren't considered while calculating the expected upgrade time, so incorrect estimate data can display. |
1184020 | - | 2.0.0.310 | - | Issue: Installation Auditor is unable to obtain local administrator rights to the SQL Server, if a clustered SQL Server is used. The ePO PIA tool doesn't accept the load balancer credentials of the clustered database. PIA doesn't move to the checks page. Cause: If a clustered SQL Server is used, PIA tries to authenticate to the virtual IP/Name of the cluster, because that's what ePO uses to connect to the cluster. PIA must connect to the actual active node of the SQL cluster to complete the checks. NOTE: Currently, Installation Auditor isn't supported on clustered SQL servers. We're evaluating the inclusion of support in a future release. |
1175859 | KB87731 | 2.0.0.310 | 2.0.0.320 | Issue: The SQL Server system RSA compatibility check fails, even if the cipher order is correct and all Microsoft updates are applied. Cause: The logic of the check is incorrect, causing the check to fail in some environments. |
1188877 | - | 2.0.0.310 | 2.0.0.320 | Issue: ePO PIA reports that ePO 5.9 isn't supported on Windows Server 2016. Workaround: Ignore this warning; ePO 5.9 is supported on Windows Server 2016. |
1189632 | - | 2.0.0.310 | 2.0.0.320 | Issue: PIA stops working or crashes when trying to export results in some environments. |
1189431 | - | 2.0.0.310 | 2.0.0.320 | Issue: PIA is unable to find the version for SQL 2016 Express. |
1189085 | - | 2.0.0.310 | 2.0.0.320 | Issue: The " |
1188290 | - | 2.0.0.310 | 2.0.0.320 | Issue: The PIA tool crashes when initiating checks in some environments. |
1189634 | - | 2.0.0.310 | 2.0.0.320 | Issue: The Change Password button is enabled, even when the passwords don't match. |
1188991 | - | 2.0.0.310 | 2.0.0.320 | Issue: The ePO Installed Version drop-down field is editable in the PIA tool, but mustn't be. |
Affected Products
Languages:
This article is available in the following languages: