For the list of all release notes click here.
The following list will give a quick overview about the newest improvements that contentACCESS version 5.1 brings to you:
Email archiving
✓ Extended recover functionality
Ransomware attacks and disaster recovery scenarios are more and more common nowadays. As a respond to the new requirements, we improved contentACCESS archives exactly in the required way to give a powerful tool into the hands of IT administrators solving such cases. Now, administrator can recover data into different location and specify the point in time he needs to recover.
From now on we can support enhanced use-cases, when administrator wants to clone and re-use the folder structure only, because contentACCESS is now able to re-create it on a different location.
The enhanced recovery options are available for File and Email archives.
✓ Archiving In-place archive
In this version, we have introduced a new feature how to archive the archive-mailboxes of users. In contentACCESS we tried to implement it in a better way, outreaching Microsoft possibilities. We merge these two mailboxes (mailbox and archive-mailbox) into one single structure. So, the users do not need to switch between 2 mailboxes to access their data, and administrator will have full control over data and recovery. The feature is available for O365 mailbox and for on-premises mailboxes.
Our solution can be used to have an on-site backup of archive-mailbox data or to fully replace the archive-mailbox and switch to more cost efficient O365 subscription.
✓ Rights protected message archiving
The protected messages are very powerful security feature of O365 as it moves the security to the document level. contentACCESS is now able to archive and index these emails and show a preview to the administrator. Indexing and preview is available only in journal-based archiving scenarios.
✓ Deleting items not marked for deletion
Are you struggling by deleting data from the archive because every email you want to delete must be marked for deletion manually? Most of the companies are having the same issue as their retention category does not include unprotected time configuration.
We have good news for you! We implemented an override option in the delete job which allows you to override this limitation and can delete emails with outdated retention, even if the emails have not been marked for deletion.
File archiving
✓ Extended recover functionality
Ransomware attacks and disaster recovery scenarios are more and more common nowadays. As a respond to the new requirements, we improved contentACCESS archives exactly in the required way to give a powerful tool into the hands of IT administrators solving such cases. Now, administrator can recover data into different location and specify the point in time he needs to recover.
From now on we can support enhanced use-cases, when administrator wants to clone and re-use the folder structure only, because contentACCESS is now able to re-create it on a different location.
The enhanced recovery options are available for File and Email archives.
Sharing
✓ Folder sharing
In contentACCESS version 5.0, we have introduced the sharing feature on platform level. This sharing feature is now extended by sharing whole folders or folder structures. Data sharing was never so easy and secure!
Folder sharing manages the folder content dynamically, which means, if you add or remove files from the shared folders, they will automatically appear in the shared folders too. The security is ensured through retrieving all data from the source system in the name of the sharing user. Every permission change is automatically reflected even in the shared folders. By sharing a folder all the sharing features, like retention, download limit, and auditing are still supported. Recipient of the shared folder can use our powerful search-tool to find required data even in text contents.
Folder sharing is available for all modules: file archive, email archive, SharePoint archive, MS Teams archive and GDPR.
Common
✓ File type group filter in index job
Every data source contains files which can or cannot be full-text indexed. The files which do not contain any textual content or where the iFilter is not present on the system, are reported as failures during the indexing process. This was quite annoying. The solution is to define a (white)list of file types which have textual content and should be indexed. We made this process easier, by having a pre-defined groups of file types. You just need to select the group of needed file types instead of picking every file type separately.
This will save your time during the initial system configuration.
✓ Performance and stability fixes
Improvements were made to make the system faster and more stable, so your contentACCESS experience could be better than it has ever been before.
Update from older versions
✓ Update path: Update is supported from contentACCESS version 3.1 and later. Older versions must be first updated to contentACCESS 3.1 and then from version 3.1 to the latest version.
If the update is done from an earlier version than 3.3, then some new features must be configured manually after the update.
One of these features is the Task runner, which requires a resource storage, where the export files will be stored. This storage must be configured in System -> System -> Resource storage settings. This store must be accessible by all contentACCESS nodes inside a cluster, so it is highly recommended to use a network share.
✓ .NET Framework support: The minimum required .NET version was increased from 4.5.2 to 4.8, for all applications.
✓ Mail app activation: As a result of redesigning the Mail app activation method in contentACCESS Email Archive, new permissions “Org Marketplace Apps” and “User Options” are needed for the super user in order to work.
✓ Outlook forms: If the update is done from an earlier version than 3.4, then as a result of some internal changes in the email archive shortcut format, the Outlook forms must be updated to the latest version to maintain the correct functionality. For contentACCESS 3.8, Outlook forms must be also republished due to authentication changes.
✓ Remote file archiving: While updating from contentACCESS 3.6, existing remote agent definitions will not work, since some of the database structures have been moved from file system archive database to the tenant database.
✓ SQL server support: The minimum required SQL version was increased from MS SQL 2008 to MS SQL 2012.
✓ Redesigned filtering: The old filtering was converted to the new format. Therefore, we recommend checking all job filtering settings after the update from 3.7 or earlier.
Documentation
✓ Documentation – Please check the updated documentation and manuals.
