Enterprise Vault™ Introduction and Planning
- About this guide
- Introduction
- Overview of Enterprise Vault
- How Enterprise Vault works
- About single instance storage
- About Enterprise Vault indexing
- About Index Server groups
- About Enterprise Vault Administration Console
- About Enterprise Vault sites, Directory, and Directory database
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Enterprise Vault Outlook Add-In
- About IMAP access to Enterprise Vault archives
- About the Enterprise Vault Client for Mac OS X
- About Microsoft Exchange forms
- About the Office Mail App for OWA 2013 and later and Outlook 2013 and later
- About Enterprise Vault extensions for Notes
- About Enterprise Vault Search
- About Enterprise Vault monitoring and reporting
- FIPS 140-2 compliance
- Enterprise Vault administration
- About Enterprise Vault administration
- Administration Console configuration of archiving
- Administration accounts and roles
- How to archive PST file contents
- How to archive NSF file contents
- How to export archived items
- Welcome message and other notifications
- About reporting and monitoring in Enterprise Vault
- How to script management tasks
- Checklist of day-to-day management tasks
- Single Sign-On for Enterprise Vault Search
- Exchange Server archiving
- Exchange Public Folder archiving
- File System Archiving
- About File System Archiving
- About File archiving policies
- About shortcut files with File System Archiving
- About setting up File System Archiving
- File System Archiving in a clustered environment
- The process of File System Archiving
- How File System Archiving handles older versions of archived files
- How File System Archiving synchronizes permissions
- File System Archiving reports
- How to restore files with File System Archiving
- About FSAUtility
- How to back up and scan shortcut files with File System Archiving
- Pass-through recall for placeholder shortcuts with File System Archiving
- Retention Folders and File System Archiving
- FSA Reporting
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Microsoft Teams Archiving
- Skype for Business Archiving
- Enterprise Vault Accelerators
- About the Enterprise Vault Accelerators
- Differences between the Enterprise Vault Accelerators
- About Compliance Accelerator
- About Discovery Accelerator
- Building in resilience
- Planning component installation
- About planning component installation
- About valid computer names for Enterprise Vault servers
- Prerequisites for Enterprise Vault components when planning installation
- Factors to consider when planning deployment of Enterprise Vault components
- Enterprise Vault Directory Service installation planning
- Where to set up the Enterprise Vault Services and Tasks
- How to plan installing Exchange Mailbox Archiving Tasks
- How to plan installing Exchange Journaling Tasks
- How to plan installing Exchange Public Folder Tasks
- How to plan installing Domino Journaling and Mailbox Archiving Tasks
- How to plan installing the Move Archive task
- How to plan installing the Storage Service
- How to plan installing the Indexing Service
- How to plan installing the Shopping Service
- How to plan installing File System Archiving
- How to plan installing SharePoint Archiving
- How to plan installing SMTP Archiving
- How to plan installing Accelerator Services
- Enterprise Vault databases and planning their installation
- Vault store groups and vault stores installation planning
- Administration Console installation
- Installation planning for client components
- Planning your archiving strategy
- About archiving strategies
- Where to define default settings for the Enterprise Vault Site
- How to allow users flexibility
- How to plan the types of items to archive
- How to define your archiving policy for user mailboxes
- How to plan the archiving policy for journal mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan an archiving strategy for FSA
- How to plan a strategy for SharePoint archiving
- How to plan settings for retention categories
- How to plan the automatic deletion of archived items
- How to plan PST migration
- How to plan NSF migration
- How to plan shared archives
- How to plan vault stores and partitions
- How to plan single instance storage
- About Enterprise Vault reports
About Compliance Accelerator
The use of Compliance Accelerator does not in itself make an organization compliant with regulatory requirements, such as NASD 3010 and 3110. However, it provides a tool for implementing a compliance strategy.
A company's compliance strategy may typically require the following:
A certain percentage of employees' electronic messages to be captured and checked by compliance officers on a regular basis. Electronic messages may include email, instant messages, social media messages, faxes, and, particularly in the financial sector, Bloomberg messages. Depending on the compliance strategy, monitoring may be required of internal messages (messages sent between employees in certain departments), or external messages (messages sent between employees in certain departments and people outside the company).
Regular searches to be run on electronic messages to capture any instances of unacceptable language or illegal business practice, such as insider dealing.
Messages to be stored securely for several years and retrieved quickly at any time.
Detailed audit information showing the review history of a message.
Enterprise Vault can be used to provide secure archiving of all company messages. Compliance Accelerator then builds on Enterprise Vault to provide the following additional features to assist an organization in implementing their compliance strategy:
The option to collect a configurable, random sample of items from a variety of archives (Exchange or Domino journal mailbox, SMTP, or shared), and add them to the set of messages for review.
A system for defining the employees that are to be monitored and grouping them in an organizational structure that reflects the departments within the company. The messages of certain employees (called "exception employees"), such as senior managers, can be kept separate and reviewed by specially assigned reviewers.
A client application that enables compliance administrators to configure Compliance Accelerator to fit the requirements of the company's compliance strategy. For example, departments of employees can be managed, granular access permissions can be assigned to designated compliance officers and administrators, automatic searches of messages can be scheduled, and sets of words for searches can be added and managed.
The client application also enables designated compliance officers or reviewers to read and mark the messages that are captured.
History information about all employees monitored, messages captured and the review process applied to each message is kept securely in a SQL database.