Privilege Management PMC 2.3.657 Release Notes

September 5, 2019

New Features and Enhancements:

  • Improved Azure PaaS database performance by adding auto-indexing for new installations and upgrades.
  • Added Support for Reporting database 5.4.

 

You must upgrade your reporting database to 5.4 to use PMC 2.3.

  • The last connected time and date is now reflected in the portal each time the adapter connects to PMC.
  • Disabled Auto-Deactivation functionality for PMC 2.3 irrespective of previous setting. This can be re-enabled, if required.
  • Rebranding and EULA changes for the following:
    • PMC Portal
    • Azure PaaS Deployment
    • On-Premises Deployment
    • Windows PMC Adapter
  • Improved time zones for reporting:
    • Implemented improvements for users to have their own time zone reflected in the reports in all tables and 24 hour Interval charts.
    • 7 day / 30 day /6 month / 12 month Interval charts now display in UTC in line with database aggregation requirements.
    • The Event Details report now has the UTC time and the user's local time (for Process, Content, and URL Events) on the Process tab.
  • Added the ability to view Power Rules in the following reports:
    • Events > All
    • Events > Process Detail (including Advanced view)
  • This information includes:
    • Rule match Type
    • Rule Script Name
    • Rule Script Publisher
    • Rule Script Status
    • Rule Script Output
    • Rule Script Version
    • Rule Script File Name
    • Rule Script Result
    • Rule Script Affected Rule
  • Added support for new Mac events: Installable and Deletable.

Issues Resolved :

  • An error message is now displayed if you choose a reserved name such as "Administrator" as a username during an Azure deployment.
  • Corrected some misleading text in the On-Premises deployment wizard.
  • You can now obtain logs from Mac endpoints from the portal.
  • Hardened the Redis configuration for On-Premises installations of PMC.
  • Corrected an issue in which the 'Getting Things Ready' message would not render correctly when loading the PMC portal.
  • Event timestamps now display correctly when the PMC portal is not in a UTC time zone.
  • The wording on the Force Policy Update and Request Logs tooltips has been updated.
  • Resolved an issue with the Events > All reports where, if the platform was set to All or OSX, the operating system context would be lost and default to Windows.
  • Resolved an issue where having the same user in multiple domains would cause a duplicate user error in the database staging process.
  • Resolved an issue with long event descriptions over 1024 characters causing the database cache to fail.
  • Added an index on ApplicationStats to improve performance.
  • Resolved an issue where the number of UAC matches on the unified reporting summary page did not match the summary tile value.
  • Resolved an issue where having the same host in multiple domains would cause errors in the database staging process.
  • Resolved an issue where having large numbers of long command lines would cause database performance issues.
  • Resolved an issue where the PurgeAllData script would incorrectly delete static data from the event details data.
  • Resolved an issue where a product name or product version over 100 characters could break the discovery report.
  • Previously only the Host Name or the User Name was unique. We now add the SID and Domain Name as part of the key.
  • Event 198 is no longer incorrectly duplicated in some scenarios when adding a user to a group using lusrmgr.msc.
  • If an application has more than one entry in the DistinctApplications table, PurgeApplication now correctly deletes all variants.
  • Improved the robustness of CopyFromStaging to ensure it can recover from an unplanned shutdown.
  • The CopyFromStaging stored procedure now waits to obtain a lock when the database is hosted in Azure SQL.
  • The CopyFromStaging procedure now runs successfully when the Event description is longer than 1024 characters.
  • Inconsistencies in the data displayed on the drill-down from the Summary report have been resolved.
  • The ® symbol is now correctly displayed in the reports where it appears.
  • The Event time is now correctly rendered in Events > All.

Notes:

  • The PMC Adapter and MMC are now compatible with Windows Server 2019 and Windows 10 19H1.

Compatibility:

Windows PMC Adapter

  • Recommended: 2.3 (all versions)
  • 2.2 GA
  • 2.1 SR1

macOS PMC Adapter

  • 2.0 (all versions)

Defendpoint Windows Client

  • Recommended: 5.4 (all versions)
  • 5.3 (all versions)
  • 5.2 (all versions)
  • 5.1 (all versions)
  • 5.0 (all versions)

Defendpoint Mac Client

  • Recommended: 5.4 (all versions)
  • 5.2 (all versions)

Reporting Database

  • 5.4 GA

Browsers

  • Microsoft Internet Explorer
  • Google Chrome
  • Apple Safari
  • Mozilla Firefox