Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading
- Order of upgrade in an environment with Compliance Accelerator or Discovery Accelerator
- Silently installing Enterprise Vault from the command line
- Installing Outlook on the Enterprise Vault server
- Securing Enterprise Vault web applications
- Weak protocols and ciphers are blocked
- Improved consistency when applying a retention period to items
- Classification using Microsoft File Classification Infrastructure on Windows Server 2016
- Data Classification Services does not support all the types of retention categories available in Enterprise Vault 12.3
- eDiscovery Platform compatibility with Enterprise Vault
- Additional points to note when upgrading from Enterprise Vault 11.0 or 11.0.1
- Steps to upgrade your system
- Enterprise Vault server preparation
- Single server: upgrading the Enterprise Vault server software
- Multiple servers: upgrading the Enterprise Vault server software
- Veritas Cluster Server: upgrading the Enterprise Vault server software
- Windows Server Failover Clustering: upgrading the Enterprise Vault server software
- Upgrading standalone Administration Consoles
- Upgrading Enterprise Vault Reporting
- Upgrading MOM and SCOM
- Upgrading Exchange Server forms
- Upgrading Domino mailbox archiving
- About upgrading Domino mailbox archiving
- Domino client version required to run EVInstall.nsf
- Preparing for the upgrade of Domino mailbox archiving
- Upgrading Domino mailbox archiving
- Granting the Domino archiving user access to mail files
- Identifying internal mail recipients
- Run the Domino provisioning task
- Upgrading the FSA Agent
- Compatible versions of the FSA Agent and Enterprise Vault server
- About upgrading the FSA Agent
- Upgrading FSA Agent services that are clustered for high availability
- Upgrading the FSA Agent on a target Windows file server from the Administration Console
- Upgrading the FSA Agent on an FSA Reporting proxy server from the Administration Console
- Upgrading the FSA Agent manually
- Upgrading Enterprise Vault Office Mail App
- Upgrading OWA Extensions
- Upgrading SharePoint Server components
- Upgrading SMTP archiving
- Required and optional tasks when upgrading SMTP Archiving
- Checking the SMTP journaling type configuration
- Checking the permissions of the SMTP Archiving task account
- Checking the 'Journal report processing' advanced SMTP policy setting
- Checking the 'Selective Journal Archiving' site setting
- About upgrading legacy SMTP archiving components
- Migrating existing targets to provisioning groups
- Reconfiguring targets that are configured for target address rewriting to use multiple archives
- Upgrading your Enterprise Vault sites to use Enterprise Vault Search
- About Enterprise Vault Search
- Server requirements for Enterprise Vault Search
- Defining search policies for Enterprise Vault Search
- Allowing privileged Enterprise Vault Search users to restore items to other users' mailboxes
- Setting up provisioning groups for Enterprise Vault Search
- Creating and configuring Client Access Provisioning tasks for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Configuring Enterprise Vault Search for use in Forefront TMG and similar environments
- Setting up Enterprise Vault Search Mobile edition
- Upgrading Enterprise Vault API applications
Setting up provisioning groups for Enterprise Vault Search
A search provisioning group identifies the users and user groups to whom you want to assign a search policy for Enterprise Vault Search. After you install Enterprise Vault, a default search provisioning group is available with which you can assign the default search policy to all users. If you want to assign a custom search policy to selected users or groups, you must set up a custom provisioning group. The default provisioning group continues to target those users whom you do not assign to a custom provisioning group.
You can set up any number of custom provisioning groups for different sets of targets. However, each provisioning group can target the users in one Active Directory domain or Domino domain, so you require at least as many groups as you have domains.
To view the properties of the default search provisioning group
- In the left pane of the Administration Console, expand your Enterprise Vault site.
- Expand the Client Access container and then expand the Search container.
- Click the Provisioning Groups container.
- In the right pane, right-click Default Search Provisioning Group and then click Properties.
You cannot amend any of the properties.
To set up a custom search provisioning group
- In the left pane of the Administration Console, expand your Enterprise Vault site.
- Expand the Client Access container and then expand the Search container.
- Right-click the Provisioning Groups container, and then click New > Active Directory Provisioning Group or New > Domino Provisioning Group.
The New Search Provisioning Group wizard appears.
- The provisioning group takes effect when the Client Access Provisioning task has run.
Complete the fields and then click Create Provisioning Group. The wizard prompts you to specify the following:
The name of the provisioning group.
The search policy to assign.
The domain to which the provisioning group applies. You can enter the details of a new domain, if necessary.
For an Active Directory domain, you must choose a trusted domain in your environment and optionally specify the required Global Catalog server. For a Domino domain, you must specify the name and password for the ID file that Enterprise Vault will use to access the domain, and the fully-distinguished name of any Domino server in the domain.
The targets (individual users and user groups) of the provisioning group.
The Enterprise Vault server that is to host the Client Access Provisioning task for this provisioning group. This task applies the required search policy to the targets of the provisioning group. You can host the task on any Enterprise Vault server in your site. However, if the task is to provision a Domino domain then you must ensure that Notes is installed on the server.
Enterprise Vault creates the task automatically if one does not already exist for the nominated domain.