Retain 4.10: How Retain Works
- Retain 4.10: How Retain Works
- Key Concepts
- What Retain Does
- How Retain works
- Retain Components and Their Roles
- Modules Overview
- Profiles
- How Retain Stores the Archives
- Retain’s Archive Data Organization
- Retain Functional Overview
- Importing and Archiving Data
- Metadata Vs. Message Data
- Exporting Data from Retain
- Removing Data from Retain
- Target Systems and Data Streams
- Smart Phone Targets
- Email System Targets
- Search Engine Targets
- Jobs
- How Archive Jobs Work
- An Archive Job Example
- Retain Users and Groups
- Populating Retain’s Archive Address Book
- Retain Users and User Accounts
- Retain Handles Users with the Same Name
- Archive Address Book Users Are Protected from Removal
- Retain’s LDAP Service
- General Account Control
- Authentication, Standard and Multi-factored
- Authentication in Retain
- Authentication Part 1: Username/Password or OpenID Connect
- Authentication Part 2 (Multi-factor Authentication)
- All Retain Users Can Be Enabled for MFA Authentication
- Duplicate LDAP User Entries Are Not Allowed
- MFA Can Work When Back-end Messaging Systems Are Offline
- When Google and Office 365 Systems Require an App Password
- Authentication is persistent
- Retention Services and Item Store Flags
- How Retain Works with GroupWise Retention Services
- How Retain Works with Exchange and Office 365
- How Retain Works with Gmail
- Retain Unified Archiving Version Numbering
- Legal Notice