SAGEPO-950

SAGEPO-939

Issue: Agent-to-server communication fails after applying ePO 5.10 Update 11. The error below is recorded on the Agent log, indicating a TLS handshake failure:
 

Issue: After you upgrade to ePO 5.10 Update 10, you can't access the ePO Cloud Bridge and add new credentials.
You see the error below after selecting the McAfee ePO Cloud Bridge option under Server Settings:

Issue: Security advisory vulnerabilities:

CVE-2020-2604, CVE-2019-2949, CVE-2019-2989, CVE-2019-2975, CVE-2020-2593, CVE-2019-2894, CVE-2020-2654, CVE-2020-2590, CVE-2020-2583, CVE-2019-2933
 

Resolution: ePO JRE 1.8.0 241

Issue: Low-severity issue in ePO.
 

Resolution: Update the Apache Tomcat version to 7.0.99.

Issue: [Security] Security advisory issues by Oracle for Java vulnerabilities for the below:

Resolution: Update ePO JRE to 1.8.0.222

Issue: Insufficient Transport Layer Protection (CVE-2019-3619).
Traffic between the AH and SQL Server isn't encrypted when the conditions below are met:

Issue: You see the incorrect message below when a user tries an incorrect logon beyond the set limit.

Issue: The two issues below are observed:

Issue: Checking in of the Endpoint Security (ENS) Platform Extension version 10.7.0.988 fails when the EPOPolicySettingValuesMT table reaches its maximum value. You see the error below when you install an extension:
"Unexpected error"

Issue: An error appears when accessing the Permission Set console.

The Orion.log records the error below:

Issue: The API command works fine on ePO Update 7, but fails on ePO Update 9 with an error indicating that the password isn't complex:
 

Issue: During an FRP logon, the authentication fails and displays the error below:

Issue: You're unable to log on to the ePO console when using a 63-character password. The error below is displayed when the issue occurs:
 

The Orion.log records the error below:

NOTE: The same user can log on with another less complex password.

Issue: The error message below appears during an FRP logon. This issue is seen with AD synchronized users, location-based policies, and encryption key assignment. 

Issue: Subactions of a server task trigger even when there aren't any systems on the list.

Orion.log records the error below:
 

Issue: Unable to rebuild indexes using API. The error below is seen when running ePOCore.RebuildIndexesCommand:
 

Issue: Delays are seen when opening the Policy Approvals and Event Filtering page.

Issue: Clients intermittently fail to communicate with the ePO server after installation of ePO 5.10 Update 8. The server log records the following error many times:
 

IMPORTANT: If ePO 5.10 Update 9 (RTS) is installed first on the ePO server, reapply ePOI 5.10 Update 9 (GA) using the Repair option.

Issue: After you perform a Quick System Search on Rollup Data, the following error is returned:
 

Issue: Running an API addUser command against the ePO Server fails to create a Windows user in ePO.
The following error is shown:
 

Issue: The Apache.exe crashes intermittently. The faulting modules are listed below:

Issue: The ePO Events\Debug folder is flooded with millions of 0-KB events, because *.PKG events are being sent from MA. 

Resolution: 0 KB *.PKG events are now uploaded to the MA 'bad' folder.

Issue: When opening a computer systems property, the following error is displayed:
 

The Orion.log records the following error:
 

Issue: Unable to compare Security for Microsoft Exchange policies. The following error is displayed during comparison:
 

Issue: The following is observed on the 'Assigned Client Tasks' page viewed from the System Tree:

Issue: The following error is seen when you to log on to the ePO console using a specific permission set:
 

Issue: Issue in Chrome when viewing the Tag Catalog page. You observe the following:

Issue: The Web API command issue.listIssues fails when run on a Linux system with root permissions. The following error is displayed:
 

Issue: The following error is seen while accessing the Client task assignment, and breaking inheritance:

Issue: Exported Queries and Reports is blank and missing the incident details after you apply ePO 5.10 Update 7 or later.
 

Resolution: Check in the DLP Extension 11.6.400.5. See the related article for details.

Issue: Unable to log on to the ePO Console. User is prompted to change their password when logging on using either Windows or Certificate authentication.
 

Workaround: See the related article for details.

Issue: Unable to log on to the ePO console when using an ePO 5.10 authenticated account containing a backslash '\'.

User sees the error below:
 

Workaround: See the related article for details.

Issue: Policy Comparison viewed from the Policy Approval workflow in ePO shows zero differences.

Workaround: See the related article for details.

Issue: You observe the following when you navigate to the System Tree to modify tasks for a Single System:

Issue: The following error is seen when you view the properties of a system in ePO 5.10:
 

Issue: The following error is displayed when the AD group contains special characters:
 

Issue: Many configured Policy Assignment Rules fail to display properly in ePO 5.10 Updates 5 and 6.

Issue: A missing image file in Repository Management.

Audit Log
 

URL 404, HTTP Error /RepositoryMgmt/images/blank.gif
 

Orion.log
 

Issue: Installation of ePO 5 .10 5 fails and rolls back. The following error is recorded in the log file:
 

Issue: Delete or Deleted not shown when creating an Automatic Response and applying the Threat Action Taken filter. Instead, the following string is shown:
 

Issue: You can see the following when you select Server Settings, Logon Protection, and click Configured in Automatic Responses:

Issue: The Systems Details page loads slowly in ePO 5.10 environments with large numbers of client events.

5.10.0

Update 5

Issue: A blank page is seen when you try to view systems with a specific tag or export all systems with a specific tag.

Issue: Queries fail after you upgrade to ePO 5.10 cumulative Update 3 and show the error below:
 

"An unexpected error occurred"
 

Some dashboard monitors can fail and show the error below:
 

"This monitor can't be displayed due to an unrecoverable error"
 

Workaround: See the related article for details.

Issue: A custom ePO Server task can't be imported. The following error displays during the import:
 

Issue: Installation of Update 3 fails. The following key errors are recorded in the Orion.log:

Resolution: Update 4 installs successfully over previous updates without an error.

Issue: A user with the correct permission set is unable to drag and drop Tags in the Tag Catalog. But, the user can successfully use the Actions, Move feature. The following error displays when the drag-and-drop action fails:
 

Issue: Using a permission-set-based user to modify multi-slot policy assignment results in an unexpected error.

Workaround: Modify the multi-slot policy assignment using an account with global administrator rights.

Issue: Roll up queries fail to execute after you upgrade to ePO 5.10. The following error displays in the console when running the query: 
 

Issue: A user's email address might be included multiple times when a selection is made to export systems using email to SV, XML, HTML, or PDF.

The selection is made from Contacts and Users.

Issue: The McAfee Active Response pages in the ePO console fail to load and display the following error:
 

Issue: You're unable to send an email after undertaking a rollback to ePO 5.10 Update 13. The port number changes to 587. The Server Setting page shows the error below:
 

Workaround: Change the port to the default SMTP port number.

Issue: The error below is seen while installing ePO 5.10 Update 11 or later.
 

Resolution: To continue with the installation, the unsupported characters in the directory path must be removed.

Issue: The stderr.log is rapidly growing in size.
The stderr.log records many alerts that reference the string: 'org.bouncycastle.tls.TlsFatalAlert'

Resolution: See the related article for details.

Issue: After you try to install ePO 5.10.0 Update 3, the install fails and displays a message:
 

After the failed update, you're unable to log on to ePO. The following error displays in the console even though the credentials are correct.
 

Resolution: See the related article for details.

Issue: The Security Resources page in ePO 5.10 is unable to load feeds when using a Proxy.
 

Workaround: See the article for details.

TSET-4730

5.10.0

Update 5

Issue: Upgrade to ePO 5.10 Update 5 fails. The following errors are seen:

NOTE: Research indicates that the ePO database is moved. The dataset is moved from an ePO Server that isn't supporting partitions to a server that supports partitions.

Issue: [User Interface] You can't select the option for a query from under Queries and Reports. This issue is seen after you select any canned query and perform a drag-and-drop action. 

Workaround: To select the option, either log off and log on again, or click the browser refresh option.

Issue: [Policy Management] When you import multi-slot policy assignments, the following error occurs:
 

Issue: A newly created user with a limited permissions set sees the following error message when logging in:
 

Issue: A client task might continue to report "In Progress" even after the task is complete.
 

Resolution: See the related article.

Issue: New Java installation doesn't have the correct certificates in the Java trusted certificates store if the following criteria are met:

Resolution: To import the certificates in the new Java trusted certificate store, implement Solution 4 in the related article.

Issue: The agent installation URL generated by the remote command below fails to allow file download.

Resolution: Use the graphical user interface to generate the agent installation URL.

Issue: You see the following error during ePO installation:

Resolution: Make sure that the remote connection to the SQL service works. Also, make sure that the SQL Server process is up and running on the specified port. See the related article for details.

Issue: When you cancel the migration utility before a migration is complete, the following are left behind on the target system:

Resolution: Delete the ePO installation folder and registry keys from the target system.

Issue: When you use a web browser to access the Web API directly, the browser caches credentials, which potentially leads to a privilege escalation. If a privilege escalation occurs, users might be granted access to data or commands for which they aren't authorized.
 

Resolution: The purpose of the Web API is for programmatic automation of tasks. If you choose to use a web browser to access the Web API directly,
for example, https://servername:port/remote/core.help,
close your browser window after you've purged your cached credentials.

Issue: After you create the first AutoUpdate ePO stack, two emails are unexpectedly sent. The emails are sent to the person mentioned as the operator of the stack.
 

Explanation: A limitation with how AWS handles paused and resumed pipelines causes this issue. Subsequent auto-updates send only one email.

Issue: The Server Health check fails on the ePO Server.
The Orion.log records the following error:

 

Issue: Client systems send data from the beta account tenancy, after moving to the production account (paid account).

Resolution: When the extension is uninstalled, the currently linked tenancy's IAM credentials are deprovisioned. This action means that agents can no longer send POST trace data with this tenancy.

Issue: MVISION Cloud Bridge can't relink accounts when there's a proxy configured. The following error is displayed:

 

Issue: A user account that's associated with more than one tenancy can't be used for linking in Cloud Bridge. User gets a response that says the following:
 

Example: If a user signs up for an MVISION account and accepts an invitation from another MVISION user, a user who belongs to a different tenancy, the account is now associated with two different tenancies. Such accounts can't be used for linking in MVISION Cloud Bridge.

Resolution: Only link single tenancy accounts. 

Issue: You're unable to log on to ePO on-premises using your MVISION account. This issue is seen when using either Microsoft Edge or Safari.

Resolution: Make sure that the options below are disabled in the browser Privacy Settings:

Issue: MVISION Single Sign On (SSO) logon fails. The user is redirected back to the ePO log on page in the below scenarios.

Resolution: See the related article for details.

Issue: You're unable to install or upgrade Protection Workspace extensions from the Software Manager or Software Catalog. The following error is recorded in the Server Task log: