MC Analyze - 20200716150700

Added a new functionality to 

The pre-existing, but not enabled by default, functionality of PostProcessing Analyze content is now generally available and has been improved significantly

If you would like to use it, enable execution of Postprocessing via the Audit agent via Administration\Audit Configuration

Alternatively, you can also select any number of documents in the Users\* views and run Actions\Y. Postprocessing

The new Postprocessing feature will be further enhanced in future releases.

NEW: Added a new view Insights from PostProc.\Desktop Catalog Sync.

This new view is synchronized with your database catalog (catalog.nsf on the same server as the analyze database where the audit agent runs or when run via client, on that users' mailserver).

It shows

- which icons on end user desktop were found in catalog,

- which icons were found in the catalog but only on different servers

- which icons were not found in catalog but other databases for the same server were still found

- which icons were not found in catalog and not a single other databases was found for the same server

NOTE: You need a replicated domain catalog. If you would like to use this functionality but need us to support a different setup, then please contact panagenda support.

NEW: Added a new view Insights from PostProc.\Local Databases\by Filename with the following toplevel category:

- duplicate replica ids on clients

- duplicate mail files with same replica id on clients

- non-duplicate/unique mail replicas

- non-duplicate/databases which are a replica from a serverside database according to catalog

- non-duplicate/unique databases

NEW: Added a new view Insights from PostProc.\Added a new view Insights from PostProc.\Local Databases\by ODS Distance showing how much older the ODS of each local database is compared to the user's Notes release:

- 10 critical (system) = names.nsf (local personal addressbook) for which the ODS does not exactly match that of the Notes release (leading to stability issues and Domino policies not working)

- 15 critical = any local database for which the ODS is newer than the Notes release of the user (meaning that the user cannot open the database)

- 20 warning (system) = same as "bad (system)" but for any ODS distance > 2

- 25 warning = same as "bad" but for any ODS distance > 2

- 30 bad (system) = same as above, but for an ODS distance of 1 or 2 for log.nsf, bookmark.nsf, cache.ndk and the users desktop file (file depends on Notes release)

- 35 bad = local databases for which the ODS is 1 or 2 older than the users recommended Notes release ODS - the higher the number the greater the delta between Notes release and ODS

- *good* = local databases for which the ODS corresponds to the Notes release

NEW: Added a new view Insights from PostProc.\by NTF Inheritance\by BuildVer & File and Added a new view Insights from PostProc.\Local Databases\by NTF Inheritance\by File & BuildVer with the following toplevel category:

The enhanced category content will visualize the notes:version_number to understand whether local databases are based on elder template versions.

Unfortunately, not all locally created databases like names.nsf and similar have this information ...

Improved behavior when opening a user document from any detail document (desktop, notes.ini etc.).

Previously it was only attempted by replica id, potentially searching for the user document in the replica on the top of the MC Analyze icon stack. Now, the Analyze database first checks whether the user document can be found by current file path, with fallback to replica id.