Upgrade Instructions
Upgrade Instructions
Upgrade Instructions
Upgrade Instructions
14.1
Enterprise Vault™: Upgrade Instructions
Last updated: 2021-07-01.
Legal Notice
Copyright © 2021 Veritas Technologies LLC. All rights reserved.
Veritas, the Veritas Logo, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator
are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the
U.S. and other countries. Other names may be trademarks of their respective owners.
This product may contain third-party software for which Veritas is required to provide attribution
to the third party ("Third-party Programs"). Some of the Third-party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the Third-party Legal Notices document accompanying this
Veritas product or available at:
https://www.veritas.com/about/legal/license-agreements
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on-premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.
https://www.veritas.com
Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:
https://www.veritas.com/support
You can manage your Veritas account information at the following URL:
https://my.veritas.com
If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:
Japan [email protected]
Before you contact Technical Support, run the Veritas Quick Assist (VQA) tool to make sure
that you have satisfied the system requirements that are listed in your product documentation.
You can download VQA from the following article on the Veritas Support website:
https://www.veritas.com/support/en_US/vqa
Documentation
Make sure that you have the current version of the documentation. Each document displays
the date of the last update on page 2. The latest documentation is available on the Veritas
website:
https://www.veritas.com/docs/100040095
Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:
You can also see documentation information or ask a question on the Veritas community site:
https://www.veritas.com/community
Contents
Upgrading the FSA Agent on a target Windows file server from the
Administration Console ............................................................ 73
Upgrading the FSA Agent on an FSA Reporting proxy server from the
Administration Console ............................................................ 74
Upgrading the FSA Agent manually .................................................. 75
Document Comments
Veritas Enterprise Vault Includes all the following documents in Windows Help (.chm)
Documentation Library format so that you can search across them all. It also includes
links to the guides in Acrobat (.pdf) format.
You can access the library in several ways, including the
following:
Deployment Scanner Describes how to check the required software and settings
before you install Enterprise Vault.
Setting up Domino Server Describes how to archive items from Domino mail files and
Archiving journal databases.
Setting up Exchange Server Describes how to archive items from Microsoft Exchange
Archiving user mailboxes, journal mailboxes, and public folders.
Setting up File System Describes how to archive files that are held on network file
Archiving servers.
Setting up Skype for Business Describes how to archive Skype for Business sessions.
Archiving
Setting up SMTP Archiving Describes how to archive SMTP messages from other
messaging servers.
About this guide 11
Where to get more information about Enterprise Vault
Document Comments
Classification using the Describes how to use the classification engine that is built
Microsoft File Classification into recent Windows Server editions to classify all new and
Infrastructure existing archived content.
Classification using the Describes how to use the Veritas Information Classifier to
Veritas Information Classifier evaluate all new and archived content against a
comprehensive set of industry-standard classification policies.
If you are new to classification with Enterprise Vault, we
recommend that you use the Veritas Information Classifier
rather than the older and less intuitive File Classification
Infrastructure engine.
NSF Migration Describes how to import content from Domino and Notes
NSF files into Enterprise Vault archives.
PST Migration Describes how to migrate content from Outlook PST files into
Enterprise Vault archives.
Registry Values A reference document that lists the registry values with which
you can modify many aspects of Enterprise Vault behavior.
Help for Administration The online Help for the Enterprise Vault Administration
Console Console.
About this guide 12
Where to get more information about Enterprise Vault
Document Comments
Help for Enterprise Vault The online Help for Enterprise Vault Operations Manager.
Operations Manager
For the latest information on supported devices and versions of software, see the
Enterprise Vault Compatibility Charts.
■ Documentation
Note: Enterprise Vault release updates that you have installed do not affect the
upgrades. You do not have to remove Enterprise Vault release updates before you
upgrade.
Documentation
The Enterprise Vault documentation is in the Veritas Enterprise
Vault\Documentation folder on the Enterprise Vault media.
For the latest information on supported devices and versions of software, see the
Enterprise Vault Compatibility Charts.
Chapter 3
Points to note when
upgrading
This chapter includes the following topics:
■ Data Classification Services does not support all the types of retention categories
available in Enterprise Vault 14.1
For more information on supported versions and upgrade paths, see the Enterprise
Vault Compatibility Charts and the article Supported upgrade paths for Enterprise
Vault, Compliance Accelerator, Discovery Accelerator and Discovery Collector at
https://www.veritas.com/docs/100023744.
For detailed instructions on how to upgrade Compliance Accelerator and Discovery
Accelerator, see their accompanying documentation.
Points to note when upgrading 16
Silently installing Enterprise Vault from the command line
For more information, see the "Installing Enterprise Vault (command line)" section
in the Installing and Configuring guide.
https://www.veritas.com/docs/100040583
Note: Outlook performance counters must be disabled when Outlook 2013 SP1,
2016, or 2019 is installed on the Enterprise Vault server. The Enterprise Vault Admin
service automatically disables the Outlook performance counters if it detects Outlook
2013 SP1, 2016, or 2019 on the Enterprise Vault server.
When you upgrade from a version that is earlier than Enterprise Vault 12.3, the
existing configuration of the Default Web Site and Enterprise Vault virtual directories
remains unchanged. To ensure the security of connections to Enterprise Vault web
applications, we strongly recommend that you manually configure an HTTPS binding
on the Default Web Site, and enable SSL on the Enterprise Vault virtual directories.
The procedure below explains how to do this.
The port and protocol that clients use to access the EnterpriseVault virtual
directory is displayed on the General tab of site properties in the Enterprise Vault
Administration Console. Before you change this setting, you must first make the
required changes to the Default Web Site in IIS for each server in the Enterprise
Vault site.
If you change the port or protocol setting in site properties after items have been
archived, existing shortcuts will no longer work. Shortcuts in Outlook and Notes
can be updated with the new protocol or port information by synchronizing mailboxes
in the Enterprise Vault Administration Console, but customized shortcuts, FSA
shortcuts and SharePoint shortcuts cannot be updated.
To create a certificate request, and implement SSL in IIS
1 Create and submit an SSL certificate request to a trusted certificate authority.
Your certificate must include both the short names and fully qualified domain
names of the Vault Site alias (that is, the DNS alias for the Enterprise Vault
site). For example, EVServer1 and EVServer1.domain.com.
You can use any suitable tool to request the certificate. For example, you can
use OpenSSL, which is installed in the Enterprise Vault installation folder. How
to create a certificate request using Microsoft Management Console (MMC) is
described in the document, https://www.veritas.com/docs/100038186.
2 On the Enterprise Vault server, perform the following steps in IIS Manager:
■ Use the Server Certificates feature to install the new certificate.
■ In the site bindings for the Default Web Site, add a binding for the HTTPS
protocol and link it to the new certificate. Bear in mind, if you change the
protocol or port for the Default Web Site, it will affect all virtual directories
in the website.
■ In the SSL Settings pane for each Enterprise Vault virtual directory, select
Require SSL.
These tasks are also described in the document,
https://www.veritas.com/support/en_US/doc/85434533-129299639-0/index.
3 When you have made the necessary changes in IIS, change the port or protocol
setting on the General tab of site properties in the Enterprise Vault
Administration Console.
Points to note when upgrading 19
Weak protocols and ciphers are blocked
Exchange Mailbox Policy This tab has been removed. The settings on the tab related
dialog box > Existing Items to how retention was assigned to items whose shortcuts were
tab moved from one mailbox folder to another. The settings also
applied to existing shortcut items in the mailbox folder. On
(In Enterprise Vault 11.0, this
the Archive Settings tab of the Site Properties dialog box,
tab was called Moved Items)
the Update the category for existing items setting also
controlled how retention was assigned to such items. The
various setting names and their combined effect caused
confusion.
In this release, the item movement behavior has been
standardized across Enterprise Vault. That is:
Site Properties dialog box > The Allow user actions to update categories setting on
Archive Settings tab this tab determines whether, when users perform actions that
could potentially update the retention categories of their
archived items, Enterprise Vault allows the updates to take
place. For example, users may move archived items between
folders to which you have applied different retention
categories, or change the retention categories of items in
Enterprise Vault Search, if permitted. Both actions can cause
the retention categories of the items to change. The following
options now let you control when Enterprise Vault updates
the retention category of such items:
■ Always
■ If item expiry is the same or later, or the record type
changes
Points to note when upgrading 21
Improved consistency when applying a retention period to items
Classification Policy This tab now provides an option, Prevent user actions from
Properties dialog box > updating retention categories, with which you can block
Settings tab unwanted changes to the retention categories that the
Enterprise Vault classification feature has assigned to
archived items. For example, users can potentially update
the retention categories by moving the items from one folder
to another.
Search Policy Properties This tab now contains an option, Allow Retention Category
dialog box > Features tab to be changed, with which you can allow Enterprise Vault
Search users to change the retention categories of the items
in their archives. By default, this option is turned off.
For an overview of retention in Enterprise Vault 14.1, see the technical note
Managing Retention.
service connection pool size for EVServer1 was 6, and the Indexing service
connection pool size for EVServer2 was 3, then the upgrade process chooses 3
as the default Indexing service connection pool size. Additionally, if you had turned
on connection information logging for any of the servers, then the Log database
information option is enabled for all the servers in the site.
Note: When you back up your databases, perform the recommended database
maintenance steps that are described in the following technical note on the Veritas
Support website:
https://www.veritas.com/docs/100022023
These maintenance steps shrink the database, rebuild the table indexes, and update
the database statistics. Such actions enable the upgrade of the databases to proceed
more quickly.
When you have backed up your vault store partitions, the Storage service marks
the relevant files as backed up, and this removes the entries from the WatchFile
table. The Storage service performs these tasks at preconfigured intervals. You
should wait for the WatchFile table to reduce in size before you proceed with the
upgrade. If you do not wait, the Storage service can take some time to restart after
the upgrade is complete. You can use the usage report at
http://evserver/enterprisevault/usage.asp to check the number of files in the Awaiting
Backup column.
Enterprise Vault server preparation 30
Updating required Windows features
Note: If you choose to check SQL Server, the report may show a warning that "SQL
databases contain entities with mixed collations". See the following technical note
for details of how to fix the problem:
https://www.veritas.com/docs/100023860
Preparation
To prepare to upgrade the Enterprise Vault server software on a single server
1 Log on to the Enterprise Vault server as the Vault Service account.
2 Stop the Enterprise Vault Admin service. This stops the Admin service itself,
and any other Enterprise Vault services.
3 Stop any other local or remote services or applications that can lock Enterprise
Vault files. For example:
■ Enterprise Vault Administration Console
■ Enterprise Vault Accelerator Manager service
4 Close any other applications that may be running on the server, including the
Control Panel, Computer Management, Windows Services, and the Windows
Event Viewer.
5 If you are installing on an Enterprise Vault Domino Gateway, make sure that
the Domino server on the Enterprise Vault Domino Gateway is shut down and
that EVInstall.nsf is not being accessed locally.
Caution: If a system restart is needed during silent installation, the server restarts
automatically. If the server restarts, log on again as the Vault Service account so
that the installer can complete the upgrade.
6 If the server restarts, log on again as the Vault Service account so that the
installer can complete the upgrade.
Table 6-1 Space required for the upgrade of the Directory database
Note: Enterprise Vault does not let you proceed with the upgrade unless this
additional space is available.
These estimated space requirements are based on the assumption that you perform
the recommended maintenance activities when you back up the database before
the upgrade.
See “Backing up the upgraded Enterprise Vault databases” on page 37.
The upgrade of a large Directory database may take a long time to complete. The
upgrade time depends on the size of the database, the database recovery model,
the upgrade path, and the available resources.
To upgrade Enterprise Vault’s databases
1 On the target Enterprise Vault server, log in using the Vault Service account.
2 Run the Enterprise Vault Management Shell.
3 In the Enterprise Vault Management Shell, run the following command:
Start-EVDatabaseUpgrade
Note that you can also run Start-EVDatabaseUpgrade -verbose if you want
to see detailed output.
4 Wait for Start-EVDatabaseUpgrade to complete the upgrade of all the
databases.
When the upgrade is complete, you can examine the upgrade reports for errors.
Start-EVDatabaseUpgrade writes the reports in the Reports\DBUpgrade subfolder
of the Enterprise Vault installation folder (for example C:\Program Files
(x86)\Enterprise Vault).
Single server: upgrading the Enterprise Vault server software 37
Backing up the upgraded Enterprise Vault databases
Preparation
To prepare to upgrade the Enterprise Vault server software
1 Log on to the Enterprise Vault server as the Vault Service account.
2 Stop the Enterprise Vault Admin service. This stops the Admin service itself,
and any other Enterprise Vault services.
3 Stop any other local or remote services or applications that can lock Enterprise
Vault files. For example:
■ Enterprise Vault Administration Console
■ Enterprise Vault Accelerator Manager service
4 Close any other applications that may be running on the server, including the
Control Panel, Computer Management, Windows Services, and the Windows
Event Viewer.
5 If you are installing on an Enterprise Vault Domino Gateway, make sure that
the Domino server on the Enterprise Vault Domino Gateway is shut down and
that EVInstall.nsf is not being accessed locally.
9 When the installation is complete, the installer re-enables the Enterprise Vault
services. Do not start any Enterprise Vault services at this time.
10 Repeat this procedure on every computer on which the Enterprise Vault services
are installed.
Caution: If a system restart is needed during silent installation, the server restarts
automatically. If the server restarts, log on again as the Vault Service account so
that the installer can complete the upgrade.
6 If the server restarts, log on again as the Vault Service account so that the
installer can complete the upgrade.
7 When the installation is complete, the installer re-enables the Enterprise Vault
services. Do not start any Enterprise Vault services at this time.
8 Repeat this procedure on every computer on which the Enterprise Vault services
are installed.
Note: You only need to complete this procedure on one Enterprise Vault server.
Table 7-1 Space required for the upgrade of the Directory database
Note: Enterprise Vault does not let you proceed with the upgrade unless this
additional space is available.
These estimated space requirements are based on the assumption that you perform
the recommended maintenance activities when you back up the database before
the upgrade.
See “Backing up the upgraded Enterprise Vault databases” on page 42.
The upgrade of a large Directory database may take a long time to complete. The
upgrade time depends on the size of the database, the database recovery model,
the upgrade path, and the available resources.
To upgrade Enterprise Vault’s databases
1 On any Enterprise Vault server, log in using the Vault Service account.
2 Run the Enterprise Vault Management Shell.
Multiple servers: upgrading the Enterprise Vault server software 42
Backing up the upgraded Enterprise Vault databases
Note that you can also run Start-EVDatabaseUpgrade -verbose if you want
to see detailed output.
4 Wait for Start-EVDatabaseUpgrade to complete the upgrade of all the
databases.
When the upgrade is complete, you can examine the upgrade reports for errors.
Start-EVDatabaseUpgrade writes the reports in the Reports\DBUpgrade subfolder
of the Enterprise Vault installation folder (for example C:\Program Files
(x86)\Enterprise Vault).
Note that Enterprise Vault does not support high-availability upgrades. You must
install the server software on all nodes in the cluster before you start Enterprise
Vault services or run the configuration wizard.
Preparation
To prepare to upgrade the Enterprise Vault server software
1 Log on to the active node as the Vault Service account.
2 Use the VCS cluster administration tools to take all the Enterprise Vault service
resources offline.
Note the following important points:
■ You must stop all Enterprise Vault services in the Enterprise Vault site. For
example, stop the services on non-clustered servers, such as an Enterprise
Vault Domino Gateway.
■ If you install on an Enterprise Vault Domino Gateway, make sure that the
Domino server on the Enterprise Vault Domino Gateway is shut down and
that EVInstall.nsf is not accessed locally.
■ If there are multiple sites that share the Enterprise Vault Directory, you must
also stop all Enterprise Vault services in the other sites.
3 Stop any other local or remote services or applications that can lock Enterprise
Vault files. For example:
■ Enterprise Vault Administration Console
■ Enterprise Vault Accelerator Manager service
4 Close any applications that may be running on the server, including the Control
Panel, Computer Management, Windows Services, and the Windows Event
Viewer.
Caution: If a system restart is needed during silent installation, the server restarts
automatically. If the server restarts, log on again as the Vault Service account so
that the installer can complete the upgrade.
6 When the installation is complete, the installer re-enables the Enterprise Vault
services. Do not start any Enterprise Vault services at this time.
7 Install the Enterprise Vault software on the other servers in your Enterprise
Vault environment, including any cluster failover nodes.
Veritas Cluster Server: upgrading the Enterprise Vault server software 46
Upgrading the Enterprise Vault databases
Note: You only need to complete this procedure on the active node.
Note that you can also run Start-EVDatabaseUpgrade -verbose if you want
to see detailed output.
4 Wait for Start-EVDatabaseUpgrade to complete the upgrade of all the
databases.
When the upgrade is complete, you can examine the upgrade reports for errors.
Start-EVDatabaseUpgrade writes the reports in the Reports\DBUpgrade subfolder
of the Enterprise Vault installation folder (for example C:\Program Files
(x86)\Enterprise Vault).
Use the cluster administration tools to bring all the Enterprise Vault services online.
If there are multiple sites that share the Enterprise Vault Directory, you can start all
Enterprise Vault services in the other sites.
Test that the cluster failover works correctly for Enterprise Vault.
Chapter 9
Windows Server Failover
Clustering: upgrading the
Enterprise Vault server
software
This chapter includes the following topics:
Preparation
To prepare to upgrade the Enterprise Vault server software
1 Log on to the active node as the Vault Service account.
2 Use Failover Cluster Manager or the command-line utility cluster to take the
Admin service resource offline. This takes all the Enterprise Vault services
offline.
Note the following important points:
■ Do not take the EnterpriseVaultServerInstance offline.
■ You must stop all Enterprise Vault services in the Enterprise Vault site. For
example, stop the services on non-clustered servers, such as an Enterprise
Vault Domino Gateway.
■ If you install on an Enterprise Vault Domino Gateway, make sure that the
Domino server on the Enterprise Vault Domino Gateway is shut down and
that EVInstall.nsf is not accessed locally.
■ If there are multiple sites that share the Enterprise Vault Directory, you must
also stop all Enterprise Vault services in the other sites.
3 Stop any other local or remote services or applications that can lock Enterprise
Vault files. Use Failover Cluster Manager to stop clustered services. For
example:
■ Enterprise Vault Administration Console
■ Enterprise Vault Accelerator Manager service
4 Close any applications that may be running on the server, including the Control
Panel, Computer Management, Windows Services, and the Windows Event
Viewer.
Windows Server Failover Clustering: upgrading the Enterprise Vault server software 50
Installing the Enterprise Vault server software
Caution: If a system restart is needed during silent installation, the server restarts
automatically. If the server restarts, log on again as the Vault Service account so
that the installer can complete the upgrade.
4 Open a command prompt window and navigate to the following folder on the
Enterprise Vault media:
\Veritas Enterprise Vault\Server\x64
6 If the server restarts, log on again as the Vault Service account so that the
installer can complete the upgrade.
7 When the installation is complete, the installer re-enables the Enterprise Vault
services. Do not start any Enterprise Vault services at this time.
8 Install the Enterprise Vault software on the other servers in your Enterprise
Vault environment, including any cluster failover nodes.
Note: You only need to complete this procedure on the active node.
Note that you can also run Start-EVDatabaseUpgrade -verbose if you want
to see detailed output.
4 Wait for Start-EVDatabaseUpgrade to complete the upgrade of all the
databases.
When the upgrade is complete, you can examine the upgrade reports for errors.
Start-EVDatabaseUpgrade writes the reports in the Reports\DBUpgrade subfolder
of the Enterprise Vault installation folder (for example C:\Program Files
(x86)\Enterprise Vault).
Windows Server Failover Clustering: upgrading the Enterprise Vault server software 52
Backing up the upgraded Enterprise Vault databases
Step 1 If you are upgrading from Enterprise Use the Microsoft SQL Server Reporting
Vault 11.0.x, remove the existing Services Report Manager web
Symantec Enterprise Vault folder. application to remove the folder.
Step 2 Install the Enterprise Vault 14.1 See “Installing the Enterprise Vault
Reporting component on each computer Reporting component” on page 57.
on which the Enterprise Vault Reporting
component is installed.
Upgrading Enterprise Vault Reporting 57
Installing the Enterprise Vault Reporting component
Step 3 Run the Enterprise Vault Reporting See “Running the Enterprise Vault
Configuration utility on each computer Reporting Configuration utility”
on which the Enterprise Vault Reporting on page 58.
component is installed.
■ Upgrading MOM
Upgrading MOM
If you use Microsoft Operations Manager (MOM) to monitor Enterprise Vault events
then you must install the new management pack.
To install the Enterprise Vault MOM management pack
1 Start the MOM Administrator Console.
2 In the left pane, right-click Processing Rule Groups and, on the shortcut
menu, click Import Management Pack.
3 Select the Enterprise Vault Management Pack, EnterpriseVault.akm, and
work through the rest of the Import Options wizard.
■ Forms85.nsf
Note: The following procedure requires you to replace the forms files with the
original Domino versions. When you replace the forms files you lose any
non-Enterprise Vault customizations that you made to them. If you made any
non-Enterprise Vault customizations to the forms files, you must reapply these
changes to the files after you have upgraded Enterprise Vault.
5 Update the ACLs on the original Domino .nsf files to give Manager access to
the ID of the user that will run EVInstall.
3 Deploy the templates created on the Domino mail server to each target Domino
mail server that has the same Domino Server version. For example, if you ran
EVInstall.nsf against a Domino Server 9.0 target server, deploy the templates
to all Domino Server 9.0 mail servers.
Deploy the templates by creating replicas of the Enterprise Vault mail templates
and running Load Design on each mail server.
It is important that you copy the templates created on the Domino mail server
and not those created on the Enterprise Vault Domino Gateway.
Note that the command Load Design updates all databases on the server. It
may be quicker to restrict the scope of the command so that it updates just
those databases that need changing. In this case, use the command's -I or
-d or -f switches to update all Enterprise Vault mail databases that have had
any of the following templates applied to them:
■ ev_dwa*.ntf
■ ev_iNotes*.ntf
■ ev_Mail*.ntf
See the Domino help for more information about Load Design switches.
4 If you have other target mail servers with different Domino Server versions, do
the following until you have deployed the templates to all mail server targets:
■ Run EVInstall.nsf again.
Upgrading Domino mailbox archiving 66
Granting the Domino archiving user access to mail files
Note: If you intend not to archive unread items then the Domino archiving user
requires Manager access to the mail files. This is because Domino requires Manager
access in order to determine which items are unread.
If Domino administrators have Manager access to all mail files, you can use the
Manage ACL tool in the Domino Administrator client to add the Domino archiving
user to all mail databases.
Repeat the following steps for each target Domino mail server.
To add the Domino archiving user to all mail databases
1 In the Domino Administrator client, navigate to the Domino mail server and
click the Files tab.
2 In the tasks pane, click the Mail folder to display a list of all the mail databases
in the results pane.
3 Select the first mail database, and then press Shift+End to select all the mail
databases.
4 Right-click and select Access Control > Manage.
Upgrading Domino mailbox archiving 67
Identifying internal mail recipients
5 Click Add and then click the person icon to select the Domino archiving user
from the Domino directory list. Click OK.
6 When the user is in the Access Control List dialog box, change the set User
Type to Person and Access to Manager.
7 Select Delete documents.
8 Click OK to add the user to the ACL of all mail databases selected.
If no user has Manager access to every mail database, then do the following:
■ Place the Domino server administrator's user name in the Full Access
Administrators field in the server document.
■ Restart the Domino server.
■ In the Domino Administrator client, choose Administration > Full Access
Administration and complete the procedure described above.
■ If necessary, the administrator can then be removed from the Full Access
Administrators field.
HKEY_LOCAL_MACHINE
\SOFTWARE
\Wow6432Node
\KVS
\Enterprise Vault
\Agents
2 Under the new NotesDomains key, create a subkey for each Notes domain.
For example, if you have Notes domains 'MyNotesDomain1' and
'MyNotesDomain2' you create subkeys 'MyNotesDomain1' and
'MyNotesDomain2'.
3 Under each of the Notes domain subkeys, create a new String value named
InternalSMTPDomains.
4 Assign to each InternalSMTPDomains value a string that lists the domains for
which you want to use local lookup. Use semi-colons (;) to separate domains.
For example:
exampledomain1.com;exampledomain2.com
5 Under each of the Notes domain subkeys, create a new DWORD value called
EnableLocalPartLookup.
6 Give EnableLocalPartLookup one of the following values:
■ 0 to disable local part lookup
■ 1 to enable local part lookup
7 Repeat all these steps for other Enterprise Vault servers that run Domino
archiving or journaling tasks.
Table 14-1 shows how the NotesDomains registry key controls how Enterprise
Vault identifies internal mail recipients.
NotesDomains key is present but has no key Original address is recorded. No lookup.
for the current Notes domain
■ 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
Upgrade FSA Agent services that are See “Upgrading FSA Agent services that are
clustered for high availability. clustered for high availability” on page 72.
Upgrading the FSA Agent 72
Upgrading FSA Agent services that are clustered for high availability
Upgrade the FSA Agent on target Windows See “Upgrading the FSA Agent on a target
file servers from the Administration Console. Windows file server from the Administration
Console” on page 73.
Upgrade the FSA Agent on FSA Reporting See “Upgrading the FSA Agent on an FSA
proxy servers from the Administration Reporting proxy server from the
Console. Administration Console” on page 74.
Upgrade the FSA Agent manually. See “Upgrading the FSA Agent manually”
on page 75.
2 Upgrade the FSA Agent on the clustered file server by using one of the following
methods:
Upgrading the FSA Agent 73
Upgrading the FSA Agent on a target Windows file server from the Administration Console
3 Perform the following steps in the order shown to reconfigure the FSA services
for high availability:
■ Run the Enterprise Vault Administration Console with an account that is a
member of the local Administrators group on each file server node. The
account must also have Full Control permission on the Enterprise Vault
server's FSA Cluster folder. This folder is in the Utilities subfolder of
the Enterprise Vault installation folder, for example C:\Program Files
(x86)\Enterprise Vault\Utilities\FSA Cluster.
■ Any non-Windows file servers for which the file server acts as the FSA
Reporting proxy server.
■ Enterprise Vault 14.1 does not support File Blocking. If you are upgrading from
Enterprise Vault 12.1 or earlier, the upgrade process removes the Enterprise
Vault File Blocking service from the file server.
To upgrade the FSA Agent on a target Windows file server from the
Administration Console
1 Run the Enterprise Vault Administration Console with an account that is a
member of the local Administrators group on the file server.
2 In the Administration Console, expand the Enterprise Vault site until the Targets
container is visible.
3 Expand the Targets container.
4 Expand the File Servers container.
5 Right-click the file server on which you want to upgrade the FSA Agent and
then, on the shortcut menu click Install FSA Agent.
6 Work through the wizard.
Note: As part of the upgrade process, you may be prompted to restart the file
server.
Note: As part of the upgrade process, you may be prompted to restart the file
server.
■ Enterprise Vault 14.1 does not support File Blocking. If you are upgrading from
Enterprise Vault 12.1 or earlier, the upgrade process removes the Enterprise
Vault File Blocking service from the file server.
To upgrade the FSA Agent manually
1 Find the required files on the Enterprise Vault server. The files are in the
evpush\Agent folder under the Enterprise Vault installation folder; for example,
C:\Program Files (x86)\Enterprise Vault\evpush\Agent.
2 Install the required Microsoft Visual C++ redistributable packages on the file
server:
■ vcredist_x86.exe
■ vcredist_x64.exe
3 Log on to the file server with an account that is a member of the local
Administrators group on the file server.
4 Run the Enterprise Vault File System Archiving x64.msi file on the file
server.
Note: As part of the upgrade process, you may be prompted to restart the file
server.
Chapter 16
Upgrading Enterprise
Vault Office Mail App
This chapter includes the following topics:
Note: You must upgrade the SharePoint components. The version of the SharePoint
components must match the version of Enterprise Vault that is installed on the
Enterprise Vault servers.
■ Reconfiguring targets that are configured for target address rewriting to use
multiple archives
■ Granting the Administrators group and system account full access to the SMTP
holding folder
After you upgrade the SMTP Archiving components, we recommend that you perform
the tasks listed in Table 18-1. The sections listed under the column heading, More
information, provide detailed information about each task.
Table 18-2 lists some optional changes that you may want to make to take advantage
of improved functionality.
"Legacy SMTP archiving" refers to the SMTP archiving solution in Enterprise Vault
11.0.0 and earlier. SMTP Archiving was completely redesigned in Enterprise Vault
11.0.1. Although the legacy SMTP archiving components are still supported at this
release, we strongly recommend that you use the current SMTP Archiving feature
instead.
Table 18-1 Checks and tasks to perform after you upgrade Enterprise Vault
Check that the type of SMTP journaling See “Checking the SMTP journaling type
assigned to existing targets is correct. configuration ” on page 82.
Check that only supported archive types are See “Checking the SMTP journaling type
assigned to existing targets. configuration ” on page 82.
Check the permissions of the SMTP Archiving See “Checking the permissions of the SMTP
task account, if the Vault Service account is Archiving task account” on page 87.
not used.
Check the configuration setting for Journal See “Checking the 'Journal report processing'
reports. advanced SMTP policy setting” on page 88.
Check the value of the Selective Journal See “Checking the 'Selective Journal
Archiving site setting. Archiving' site setting” on page 89.
If you use the legacy SMTP archiving If you want to continue running the legacy
solution, re-configure the legacy SMTP SMTP archiving components, then you need
archiving components. to rerun the legacy SMTP archiving
configuration process.
Table 18-2 Optional checks and tasks to perform after you upgrade
Enterprise Vault
Table 18-2 Optional checks and tasks to perform after you upgrade
Enterprise Vault (continued)
Replace address rewriting with targets that See “Reconfiguring targets that are
have multiple archives assigned. configured for target address rewriting to use
multiple archives” on page 91.
Table 18-3 How Enterprise Vault determines the SMTP journaling type
SMTPTarget3 >
ExchangeJournalArchive
SMTPTarget4 >
DominoJournalArchive
Table 18-3 How Enterprise Vault determines the SMTP journaling type
(continued)
Table 18-3 How Enterprise Vault determines the SMTP journaling type
(continued)
Table 18-3 How Enterprise Vault determines the SMTP journaling type
(continued)
USE EnterpriseVaultDirectory
SELECT ST.TargetId, ST.Address, A.ArchiveName, AT.Name AS 'ArchiveType',
CASE WHEN ST.TargetType = 1 THEN 'SMTP Journaling'
WHEN ST.TargetType = 2 THEN 'SMTP Mailbox Journaling'
WHEN ST.TargetType = 3 THEN 'SMTP Group Journaling'
ELSE 'Legacy'
END AS WronglyDetectedTargetType
FROM SmtpTarget ST
INNER JOIN SmtpTargetArchives STA ON STA.TargetId = ST.TargetId
INNER JOIN Root R ON R.RootIdentity = STA.RootIdentity
Upgrading SMTP archiving 87
Checking the permissions of the SMTP Archiving task account
This query returns information about each target such as the ID of the target, the
SMTP target address, name of the archive, and the archive type. You can export
the retrieved results to a CSV or TXT file.
If you want to assign multiple archives to this target, you need to delete the address
and add it again with the supported archive types.
For information about these values, see the section, "Journal Reports settings”
(Advanced SMTP policy settings)", in the Administrator’s Guide.
If you want to continue to use the legacy Enterprise Vault SMTP Archiving
components, install the Enterprise Vault 14.1 SMTP Archiving components, and
rerun the legacy Enterprise Vault SMTP Archiving configuration process as follows:
■ Open a command prompt window and change to the folder, Enterprise
Vault_installation_folder\x64.
4 Take a backup of the aliases file that has the target address domain as its
filename. Remove the alias entry of the routing address and rename the file.
5 Update the properties of the routing address to assign multiple archives.
6 Restart the SMTP Archiving task.
■ Allowing privileged Enterprise Vault Search users to restore items to other users'
mailboxes
■ Creating and configuring Client Access Provisioning tasks for Enterprise Vault
Search
■ Configuring Enterprise Vault Search for use in Forefront TMG and similar
environments
Enterprise Vault Search enables client users to browse and search their archives.
This feature replaces the legacy search applications: Archive Explorer, Browser
Search, and Integrated Search, which are no longer available.
Properties dialog box for the Enterprise Vault site and then, on the Archive
Settings tab, ensure that Users can delete items from their archives is
selected.
■ When using the advanced search facilities in Enterprise Vault Search, choose
from extra options on the Select search property drop-down list. These extra
properties make it easier to build search queries for the items that the Enterprise
Vault records management and classification features have tagged.
Installing Enterprise Vault creates a default search policy automatically. You can
modify the properties of this default policy and define custom search policies. Then
you can assign each policy to a different search provisioning group.
To view and modify the properties of the default search policy
1 In the left pane of the Administration Console, expand your Enterprise Vault
site.
2 Expand the Policies container.
3 Click the Search container.
4 In the right pane, right-click Default Search Policy and then click Properties.
You can change the settings on the Features and Advanced Search tabs,
but you cannot change the settings on the other tabs.
To define a new search policy
1 In the left pane of the Administration Console, expand your Enterprise Vault
site.
2 Expand the Policies container.
3 Right-click the Search container, and then click New > Policy.
The New Search Policy wizard appears.
4 Follow the on-screen instructions. The wizard prompts you to specify the
following:
■ The name of the policy and an optional description of it.
■ The Enterprise Vault Search facilities that you want to make available to
users.
■ For a search provisioning group, the task does not assign the search policy to
any users. When the task next runs, it starts from the beginning and assigns
the policy to all users.
■ For an IMAP provisioning group, those users to whom the task assigned a policy
before it stopped retain that policy; the other users are not provisioned. However,
when the task next runs, it starts from the beginning and reassigns the policy
to all users.
If a suitable Client Access Provisioning task does not exist when you set up a search
provisioning group, Enterprise Vault automatically creates one. However, you can
manually create and configure this task at any time.
To create and configure a Client Access Provisioning task for Enterprise Vault
Search
1 In the left pane of the Administration Console, find and then expand the
Enterprise Vault Servers container.
2 Expand the container for the server to which you want to add the Client Access
Provisioning task.
3 Right-click the Tasks container, and then click New > Client Access
Provisioning Task.
The New Client Access Provisioning Task dialog box appears.
4 Complete the fields and then click OK. The dialog box prompts you to specify
the following:
■ The domain with which to associate the task.
■ The name of the task.
■ Whether to start the task now. If you want to configure the task before it
starts, turn off this option and follow the instructions in step 5.
The settings that you can configure include the times at which the task runs
each day and the level of reporting that it undertakes for each provisioning
run.
5 To configure the task, right-click it in the right pane, and then click Properties.
The online Help provides detailed information on each field in the properties
dialog box.
Upgrading your Enterprise Vault sites to use Enterprise Vault Search 101
Configuring user browsers for Enterprise Vault Search
5 Enter the fully-qualified domain name of the server on which you installed
Enterprise Vault Search, and then click Add. For example, you might type
vault.company.com.
6 Close the Trusted sites dialog box, and then close the Internet Options dialog
box.
To configure Enterprise Vault Search for use in Forefront TMG and similar
environments
1 Locate the following file on the Enterprise Vault server:
C:\Program Files (x86)\Enterprise
Vault\EVSearch\EVSearchClient\Web.config
Caution: You can install the required components on the Enterprise Vault server.
However, if you want to give your users Internet access to Enterprise Vault Search
without exposing your Enterprise Vault server to unnecessary security risks, it is
advisable to install the components on a proxy server.
You can install Enterprise Vault Search Mobile edition on a proxy server on which
you have also installed the following:
■ One of the following versions of Windows:
■ Windows Server 2012
■ Windows Server 2012 R2
■ Windows Server 2016
■ Windows Server 2019
The server must have an NTFS file system.
■ The Enterprise Vault API Runtime. The process of installing Enterprise Vault
Search Mobile edition on the proxy server automatically installs the API Runtime,
if it is not already present.
■ Internet Information Services (IIS) 8.0 or later.
The following table lists the minimum set of role services that you must install
for the Web Server (IIS) role.
4 In the left pane of the Veritas Enterprise Vault Install Launcher, click Enterprise
Vault.
5 Click Server Installation.
6 Choose the required installation option.
To install Enterprise Vault Search Mobile edition on a proxy server, choose
Installation on an additional server.
7 Follow the instructions in the Enterprise Vault installation wizard.
When the wizard prompts you to select the features that you want to install,
do one of the following:
■ For installation on a proxy server, clear all the options except for Search
Access Components.
When you click Next, the wizard requests the Vault Site alias. This alias is
the DNS alias for the Enterprise Vault site.
■ For installation on an Enterprise Vault server, choose all the required
components.
Upgrading your Enterprise Vault sites to use Enterprise Vault Search 107
Setting up Enterprise Vault Search Mobile edition
If you choose to install the Enterprise Vault services, or you have previously
installed them on this server, then you cannot clear the Search Access
Components option. The components will be automatically installed.
■ Upgrading any applications that use the Enterprise Vault API Runtime