MC Analyze - 20200716150700

The pre-existing, but not enabled by default, functionality of PostProcessingAnalyze 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.

Added several new views for PostProcessing:

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 user's mailserver).

It shows which icons on end users' desktops were:

• • found in the catalog
  • found in the catalog but only on different servers
  • not found in catalog but other databases for the same server were still found
  • 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, please contact panagenda support.

Local Databases\by Filename

This new view has the following toplevel categories:

• • 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 the catalog
  • non-duplicate/unique databases

Local Databases\by ODS Distance 

This new view shows 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) = log.nsf, bookmark.nsf, cache.ndk and the users desktop file (file depends on Notes release), for any ODS distance > 2
  • 25 warning = local databases for any ODS distance > 2 - the higher the number the greater the delta between Notes release and ODS
  • 30 bad (system) = same as "warning (system)" above, but for an ODS distance of 1 or 2
  • 35 bad = same as "warning" above, but for an ODS distance of 1 or 2
  • *good* = local databases for which the ODS corresponds to the Notes release

Local Databases\by NTF Inheritance, \by BuildVer & File, and\by File & BuildVer 

These new views will show information about the templates used by local databases, including:

• • whether the databases have relative, absolute, or network paths
  • which template is being used by a given database (if any)
  • whether there are duplicate templates for a given database

The "BuildVer" views have categories that display the notes:version_number to understand whether local databases are based on older template versions.

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