Last updated: 20 July 2007

ReadMeFirst for Enterprise Vault™ 7.0

This document provides important information about the Enterprise Vault 7.0 release. For the very latest version of this document, see http://entsupport.symantec.com/docs/289728 on the Symantec support Web site.

The new features and fixes contained in Service Pack 2 (SP2) are described in the Enterprise Vault 7.0 Service Pack 2 document (Updates_EN.htm) on the release media. For the very latest version of that document, see http://entsupport.symantec.com/docs/289727 on the Symantec support Web site.

The new features and fixes contained in the previous Service Pack are described in the PreviousUpdates document (PreviousUpdates_EN.htm) on the release media.

Before you install or upgrade to Enterprise Vault 7.0 SP2, it is important to read the following sections of this ReadMeFirst:

If you are performing a new installation of Enterprise Vault, follow the installation instructions in the Enterprise Vault Installing and Configuring guide. The guide is in the Documentation folder on the Enterprise Vault 7.0 SP2 release media.

If you are upgrading an existing Enterprise Vault installation, follow the instructions in Upgrading to Enterprise Vault 7.0 SP2 (UpgradeInstructions_EN.htm) on the release media.

For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.

For the latest information on Enterprise Vault 7.0 sizing and performance, see the Enterprise Vault 7.0 Performance Guide at http://entsupport.symantec.com/docs/286105.

Contents

New features and changes in Enterprise Vault 7.0

For additional features and changes introduced with Service Pack 2, see the Enterprise Vault 7.0 Service Pack 2 document (http://entsupport.symantec.com/docs/289727 on the Symantec support Web site).

Licensing

Enterprise Licensing System

Enterprise Vault 7.0 uses a new type of licensing: the Enterprise Licensing System (ELS). ELS replaces the previous text file-based licensing technology.

If you are running a version of Enterprise Vault prior to 7.0, your current license file will not work with Enterprise Vault 7.0. You will need to obtain upgraded licenses for Enterprise Vault 7.0.

To upgrade to Enterprise Vault 7.0 from an earlier version, you must download and install a new ELS license that covers all your existing Enterprise Vault product features.

Each ELS license file has a unique name and the extension .slf. The Enterprise Vault installation wizard prompts for the location of your ELS license file, which can be in any folder, and copies the file to the top-level Enterprise Vault folder (typically C:\Program Files\Enterprise Vault).

You can continue Enterprise Vault installation without an ELS license file, but Enterprise Vault will operate in read-only mode until you obtain and install a new ELS license.

Any ELS license present in the top-level Enterprise Vault folder is installed automatically each time the Enterprise Vault Admin service starts. For a multi-server Enterprise Vault deployment, you must copy the ELS license file to the top-level Enterprise Vault folder on each Enterprise Vault server.

The license installation process creates a new folder named Installed Licenses under the top-level Enterprise Vault folder. The Installed Licenses folder contains the ELS license files successfully installed by the Enterprise Vault Admin service when it starts. The files are moved to this folder so that the licenses are not reinstalled on a subsequent restart of the Enterprise Vault Admin service.

For information about licenses and how to obtain them, contact Symantec Customer Care:

http://www.symantec.com/enterprise/licensing/index.jsp

Replacing licenses and installing additional licenses

To replace a license or install an additional license:

For a multi-server Enterprise Vault deployment, you must repeat the steps on each Enterprise Vault server.

Separate license for Domino Server Journal archiving

In previous releases, the Exchange Journal archiving license enabled journal archiving from Exchange Servers and Domino Servers. At this release, a separate Domino Journaling license is required for journal archiving from Domino Servers.


Clustering with Microsoft Server clusters

You can cluster Enterprise Vault servers in a Microsoft server cluster on either Windows 2003 Enterprise Edition or Windows 2003 Datacenter edition, to provide a high availability solution for Enterprise Vault. For more information, see the Installing and Configuring manual.


Roles-based administration

You can now create multiple Enterprise Vault administration roles, each with different levels of permissions. This means that administrators can be given limited access to the Administration Console in order to perform certain everyday tasks. Access to the Vault Service account can then be reserved for senior Enterprise Vault administrators.

In an administration role you can define the following:

In the Administration Console, administrators with a limited access role will see only the functionality options and objects permitted by their administration role. The Directory Service, Task Controller Service and Storage Service perform access permission checks when any other applications, such as Policy Manager, attempt to perform Enterprise Vault administration tasks.

The Vault Service account still has access to all Enterprise Vault objects, and can perform all Enterprise Vault management operations, including creating roles. When you run the Configuration wizard, you must be logged in as the Vault Service account.

Note that Enterprise Vault services and tasks must run as either the Vault Service account or as an account assigned to the predefined Enterprise Vault role, Power Administrator.


Granular provisioning of Exchange Server mailboxes [Ref: 853656]

In this release, each Exchange Server mailbox to be archived must be a member of a Provisioning Group. You create the required Provisioning Groups in the Administration Console and apply a suitable Exchange Mailbox archiving policy to each one. A Provisioning Group can be one of, or any combination of, the following:

Granular provisioning reduces the need to use Policy Manager to enable mailboxes. The vault store and Indexing service to use when enabling mailboxes can be set for a Provisioning Group, an Exchange Server, or an Enterprise Vault server. Using the auto-enable feature, this means that different mailboxes can be enabled on different vault stores depending on their Exchange Server or their Provisioning Group. Policy Manager can still be used to enable mailboxes and apply filters, but users must be assigned to a Provisioning Group before they can be processed.

Provisioning Groups are processed by the new Provisioning task. This task determines all mailboxes that belong to each Provisioning Group and writes the appropriate data to the Directory for each mailbox. There is one Provisioning task per Exchange Server domain. This task is created automatically when the administrator adds the first Exchange Server archiving task to the domain.

Note that the Provisioning task does not enable mailboxes. You can choose to enable mailboxes automatically in the Provisioning Group settings, or you can use the Enable Mailbox wizard to enable mailboxes manually. See the Day-to-day administration section in the Administrator's Guide for more information on Provisioning Groups and enabling mailboxes.

The order in which the Provisioning task processes Provisioning Groups is determined by the order of the Provisioning Groups in the Administration Console. If a mailbox belongs to several Provisioning Groups, the first Provisioning Group that the mailbox belongs to determines the settings that are applied. You can reorder the list of Provisioning Groups in the Administration Console.

Reports created by the Provisioning task provide information about mailboxes enabled, including the following:


Enhancements to File System Archiving

Task-based administration of FSA

File System Archiving is now configured in the same task-based manner as other Enterprise Vault archiving. This provides more flexibility than before. In particular, it is now possible to configure an archiving task as follows:

Remote installation of NTFS Placeholder Service

The FSA Placeholder Service can now be installed on remote NTFS file servers from the Administration Console and also from the Enterprise Vault 7.0 media.

Placeholders on EMC Celerra devices

It is now possible to create placeholder shortcuts on EMC Celerra devices. The Placeholder Service for Celerra devices runs on the Enterprise Vault server; you do not install it on the file server.

When a Celerra placeholder is opened, the corresponding archived file is recalled automatically.

It is also possible to configure Enterprise Vault so that deleting a placeholder on a Celerra device also deletes the corresponding archived file.

Placeholder Service in a clustered environment

It is now possible to make the Placeholder Service highly-available on Microsoft clustered servers and on VERITAS Cluster Server (VCS). See the Installing and Configuring guide for prerequisite software requirements.

Both active/passive and active/active clusters are supported.

File Groups

It is now possible to specify several different file types to be treated together for the purposes of file archiving. This is a file group. For example, you could create a file group called "Web Pages" and within it have the file types *.htm, *.html, and *.gif. Within an FSA policy you could then define a rule that applies to "Web Pages". There is no requirement for you to use file groups.

You can assign file groups to rules in an FSA archiving policy. During an archiving run, files will be archived according to the file groups assigned in the policy rules.

If a file group associated with a policy is modified, then the changes will be reflected in the next archiving run.

Several file groups have already been defined for your use and are available in the Administration Console in the File Groups container, under File System Archiving.

Configuration of archive points

FSA archive points can now be configured from within the Administration Console. Previously, archive points had to be configured using a command-line tool.

When you create a new folder archiving target, the New Folder wizard enables you to create archive points.

You can view and edit archive points using the new Archive Point wizard, which is started by right-clicking a volume in the Administration Console, and selecting the menu option Archive Points.

Automatic deletion when recalling or deleting a placeholder

FSA folder policies now have options that enable you to control whether the archived copy of a file is deleted when its placeholder is recalled or deleted. The options, Delete archived file when placeholder is deleted and Delete archived file when placeholder is recalled are on the Shortcuts tab of the policy properties. The default is not to delete the archived copy.

Care should be taken when using Delete archived file when placeholder is deleted. If you temporarily restore a folder from a backup, and the folder contains placeholder shortcuts, then the archived items will be deleted when you delete the temporary folder.

FSA data mover utility

The new utility, FSAUtility, is a command-line program that enables you to do the following:


Enterprise Vault monitoring and reporting

Monitoring database and Monitoring agents

There is now one Monitoring database per Directory database. A Monitoring agent on each Enterprise Vault server gathers status information every few minutes and records it in the Monitoring database. This information includes the status of Enterprise Vault services and archiving tasks, and the values of performance counters for vault stores, disk, memory, and processors.

The Monitoring database data is used by Enterprise Vault Operations Manager, and by Enterprise Vault Reporting in some of its reports.

Enterprise Vault Operations Manager

Enterprise Vault Operations Manager is a Web application that makes remote monitoring of an Enterprise Vault site possible from any computer with Internet Explorer 6.0 or later. It enables you to monitor:

To use Operations Manager to monitor the Enterprise Vault servers in an Enterprise Vault site, you must install the Operations Manager component on at least one Enterprise Vault server in the site. For more details, see the Installing and Configuring manual.

Enterprise Vault Reporting

Enterprise Vault Reporting provides enterprise-level reporting, using Microsoft SQL Server Reporting Services as the reporting mechanism. Administrators view reports and manage report content using the Reporting Services Report Manager Web application.

The supplied reports cover a variety of topics, including:

You can customize report content, export reports in several formats, and schedule the running of reports at regular intervals.

To use Enterprise Vault Reporting, you must install the Enterprise Vault Reporting component on a machine running Microsoft Reporting Services, after you have installed and configured your Enterprise Vault servers. For more details, see the Installing and Configuring manual.


Tool for removing orphaned shortcuts

An orphaned shortcut is an Enterprise Vault shortcut that points to an item that no longer exists in the archive. This can occur if a user does the following:

In this release, the deletion of orphaned shortcuts during a scheduled shortcut deletion run is supported for Exchange Server mailboxes and public folders.

Shortcut deletion is controlled using options on the Shortcut Deletion page of the archiving policy properties. To enable the deletion of orphaned shortcuts, select the option Delete orphaned shortcuts on this page.

Shortcut deletion runs are scheduled using the Shortcut Deletion page in the properties of Exchange Mailbox and Public Folder tasks.

Details of orphaned shortcuts that have been deleted are included in the report produced during a shortcut deletion run.


Outlook not required for FSA or SharePoint archiving [Ref:854434]

In Enterprise Vault 7.0, Outlook is only needed on Enterprise Vault servers that perform Exchange Server archiving. It is no longer required for new installations of FSA or SharePoint archiving.

In a new installation of FSA or SharePoint archiving, if you plan to archive Exchange Server MAPI messages on file servers or SharePoint Servers, then you will need to install Outlook on the Enterprise Vault server that hosts the Storage service.

If you are upgrading to Enterprise Vault 7.0 from an earlier version, you still require Outlook on all Enterprise Vault servers that host the Enterprise Vault Storage service in order to access items archived using earlier versions.


Client support on Mac computers

On Mac computers, customized shortcuts are supported with Entourage, and Browser Search is supported with Safari.

For supported versions of Entourage and Safari, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.


New look Enterprise Vault Browser Search [Ref CAP422]

Enterprise Vault 7.0 introduces a new look, or skin, to the Browser Search, with new icons, colors, and the Symantec logo.

There have been no changes to the names of options or to their functionality or relative positioning.


Accessing Outlook hidden message

In Outlook, you can display information about the Enterprise Vault User Extensions by clicking Tech Info on the About Enterprise Vault dialog. The Enterprise Vault Information dialog is displayed. The information displayed has been extended to include hidden messages; at the end of the System Information list, a section called Hidden Messages in Folder has been added. This section lists details of all the Enterprise Vault hidden messages for the currently selected folder.

If enabled on the user's computer, the user can also delete an Enterprise Vault hidden message by using the Delete Hidden Message button on the Enterprise Vault Information dialog. This button only appears if a hidden message is listed and the DWORD registry setting,
HKEY_CURRENT_USER\Software\KVS\Enterprise Vault\Client\DeleteHiddenMsgBtnVisible

is configured on the user's computer with a non-zero value.


Self-healing client

There are new Desktop policy settings, in the Advanced page of the Exchange Mailbox policy properties, that enable the Enterprise Vault User Extensions to automatically attempt to fix the following issues:

A settings is also available to provide status information on the HTTP connection to the Enterprise Vault Web server. This is given in The Tech Info dialog, displayed when you click Help > About Enterprise Vault >Tech Info.

In addition, the utility, ResetEVClient, enables administrators to perform a number of housekeeping tasks in an attempt to fix common client problems.


Searching offline archive from Windows Desktop Search (WDS)

A Windows Desktop Search (WDS) plug-in is included with the Enterprise Vault User Extensions (EVClient_lang.msi) and the Windows Installer version of the Self-Installing User Extensions (EVClientHTTP_lang.msi). This plug-in enables users to include their offline vault in searches using WDS. You enable this feature using an Offline Vault setting on the Advanced page of the Exchange Mailbox Policy properties.

Additionally, Desktop settings in the Exchange Mailbox Policy properties enable you to add Enterprise Vault search links to WDS. Using these links, users can search their online archive using WDS.

Only Windows Desktop Search 2.6.5 is supported at this release. For the optional, online archive search links, MSN Search Toolbar V02.06 is supported.

The WDS plug-in is supported with Outlook XP and Outlook 2003, but not Outlook 2000.

Note that the WDS feature is not available with the web-based installation of the Self-Installing User Extensions (EVDesktop.cab).


Language versions available

The Enterprise Vault Administration Console, help and administration manuals are available in English and Japanese.

The User Extensions, OWA 2003 clients, Archive Explorer, Enterprise Vault Search applications and SharePoint Archive Search Web Parts are available in:

Danish
Dutch
English
French
German
Hebrew
Italian
Japanese
Simplified Chinese
Spanish (Castillian)
Swedish


Enterprise Vault Add-ons

An increasing number of storage management applications are being integrated with Enterprise Vault to manage the collection and migration of archived data. For details of these integrations and instructions on what you need to configure to use the products with Enterprise Vault, see the Symantec support knowledge base article, http://entsupport.symantec.com/docs/286013.

Enterprise Vault 7.0 media contains the following third party applications and adapters that integrate with Enterprise Vault to provide additional functionality.

Adapter for RMS 7.0

The Enterprise Vault Adapter for RMS enables the removal of RMS protection, and encryption, from Exchange Server journaled email messages as they are stored in Enterprise Vault.

Protection is also removed from supported office documents and other email messages that are attached to protected email messages.

The Adapter stores certain parameters or metadata about the protection in the archive. You can later search the archive and tailor your query based on these parameters.

Full documentation on how to install and configure the software is included with the software.

Automatic Classification Engine 4.7

Enterprise Vault Automatic Classification Engine (ACE) is an OEM version of Orchestria Active Policy Management (APM). It extends the existing capabilities of Enterprise Vault to include intelligent categorization using tagging rules. Specifically, it enables Enterprise Vault to apply rules to Exchange Server journaled messages to categorize them according to their content or context.

These rules enable Enterprise Vault to:

Full documentation on how to install and configure the software is included with the software.

Connector for EMC Documentum Retention Policy Server 7.0

The Enterprise Vault integration to Documentum provides two main features:

Full documentation on how to install and configure the software is included with the software.

User Classification Engine 7.0

This feature integrates Trusted Edge Desktop Data Management with Enterprise Vault Exchange Server mailbox archiving, to provide additional document classification, capture and retention capabilities at user desktops.

The administrator uses Trusted Edge to create policies that determine which files should be captured, and where they should be stored. These policies are then implemented on user desktops, using the Enterprise Vault user extensions; users are required to apply Trusted Edge policy information to items created in their Exchange Server mailbox.

When mailbox items are archived by Enterprise Vault, the policy information is stored with the item. Depending on the policy settings, the item can also be stored automatically in additional repositories, such as a records repository.

Trusted Edge can upload captured documents to one or more repositories. Currently supported repositories include

Full documentation on how to install and configure the software is included with the software.

IM Manager 8.1

Symantec IM Manager is a software proxy for securing, managing, and logging IM messages for public and enterprise IM protocols. It delivers real-time threat protection, management, and compliance for your organization’s IM activity through the following features:

Enterprise Vault IM Archiving Option delivers the compliance features necessary to log and archive Instant Messages to Enterprise Vault. For security features a full license of IM Manager 8.1 is required – contact your local Symantec representative for upgrade options, if desired.

Full documentation on how to install and configure the software is included with the software.

Points to note

Deployment Scanner

The Deployment Scanner has been updated for Enterprise Vault 7.0, and is included in the folder Deployment Scanner on Enterprise Vault 7.0 media.

Before installing Enterprise Vault 7.0, or upgrading, we strongly recommend that you run the Deployment Scanner to check prerequisite software and settings.

Use the Vault Service account when running the Deployment Scanner.

To install Deployment Scanner Windows Installer 3.1 must be installed on the Enterprise Vault server computers. You can download Windows Installer 3.1 from the Microsoft Download Center.

Note:  Deployment Scanner supersedes the older Environment Scanner.


Changed prerequisites for Enterprise Vault

It is important that you check in the Installing and Configuring guide the prerequisites for the types of archiving and Enterprise Vault features that you plan to implement.

Note Microsoft .NET Framework 2.0 is required on the Enterprise Vault Reporting computer for all supported versions of Microsoft SQL Server Reporting Services. (This requirement is documented incorrectly in the Installing and Configuring guide).

If you are upgrading to Enterprise Vault 7.0, this section highlights the significant changes to prerequisites.


Software no longer supported

The following software is no longer supported on Enterprise Vault servers:


Enterprise Vault servers

Outlook on Enterprise Vault servers

If Outlook is required on the Enterprise Vault server, do not install Outlook 2000 or Outlook 2002 (from Office XP), or Outlook 2007. Enterprise Vault 7.0 servers are not compatible with these versions of Outlook.

If you install Outlook 2003, the installation is not complete until you run Outlook. If you install Outlook 2003 as a prerequisite on an Enterprise Vault server then, before you install Enterprise Vault, you must start Outlook, complete its configuration, and close it.

If you plan to use earlier versions of the User Extensions and Self-Installing User Extensions with Enterprise Vault 7.0 servers, or need to access data archived using earlier versions of Enterprise Vault, Outlook is required on Enterprise Vault servers that host the Enterprise Vault Storage service.

Lotus Notes client support on Enterprise Vault servers [Ref 858858]

On an Enterprise Vault server that is archiving from Domino, the only Notes client that is supported is 7.0.1.

It is important that you do not run the Lotus Notes client on the Enterprise Vault server when the Domino Journaling task is running.

Domino archiving limitation [Ref 859149]

You cannot use a Domino archiving task to archive from more than one Domino domain.

Maximum number of tasks [Ref 31631]

Do not exceed a maximum of 40 running tasks per Enterprise Vault server. Note that this maximum includes tasks that have been started but are not processing because they are not within their scheduled archiving windows.

Monitoring database

During the configuration you are prompted to supply a location for the Monitoring database data and log files. Do not specify a root folder for these files, otherwise the configuration will fail.

For supplementary information on maintaining and managing the Monitoring database, see the following document on the Symantec Support Web site: http://entsupport.symantec.com/docs/286081.

Backing up Enterprise Vault in a clustered environment

For supplementary information on backing up Enterprise Vault in a VCS cluster or Microsoft server cluster, see the following document on the Symantec Support Web site: http://entsupport.symantec.com/docs/285839.


Enterprise Vault Operations Manager and Reporting

If you want to install the Enterprise Vault Operations Manager or Reporting features on a machine that has other Enterprise Vault components already installed:


Roles-based administration

The Vault Service account still has access to all Enterprise Vault objects, and can perform all Enterprise Vault management operations, including creating roles.

If you want other accounts to be able to perform a large number of Enterprise Vault administration tasks, apart from running the configuration program, then the Vault Service account needs to assign the required accounts to the predefined Power Administrator role.

When you run the Configuration wizard, you must be logged in as the Vault Service account.

To run the Administration Console you must be logged on either using the Vault Service account, or using an account that has been assigned an Enterprise Vault administration role by the Vault Service account. You cannot run the Administration Console using a local administrator account that has not been assigned to an Enterprise Vault administration role.

Enterprise Vault services and tasks must run as either the Vault Service account (recommended) or as an account assigned to the predefined Enterprise Vault role, Power Administrator.

Prerequisite software for roles-based administration

Roles-based administration uses Microsoft Windows Authorization Manager. Creating and managing roles using the Administration Console requires the Authorization Manager MMC snapin, which is only available on the following:

Windows Server 2003 Administration Tools Pack can be downloaded from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=c16ae515-c8f4-47ef-a1e4-a8dcbacff8e3&DisplayLang=en

For roles-based administration settings to be honored on Windows 2000, the following must be installed:

Microsoft do not provide an Authorization Manager MMC snapin for Windows 2000 Server, so changes to the roles and role assignments must be done using an Administration Console on Windows Server 2003 or Windows XP Professional.

Windows 2000 Authorization Manager Runtime can be downloaded from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=7edde11f-bcea-4773-a292-84525f23baf7&DisplayLang=en

Local administration rights required if Windows Server 2003 SP1 is installed [Ref 858584]

If you use the roles-based administration facility to assign an Enterprise Vault administration role to a user, and you have installed Enterprise Vault on a Windows Server 2003 SP1 computer, that user can only run the Administration Console remotely if he or she has local administration rights on the Enterprise Vault computer.

Limitations to administrator permissions [Ref 83753]

In Enterprise Vault 7.0 you can assign administrator permissions to grant or deny access to individual targets in the Administration Console. You could, for example, grant an administrator access to a single Exchange Server computer.

You can assign permissions to grant or deny access to any of the following:

You cannot, however, assign permissions to control access to tasks. Thus, for example, if you have denied an administrator access to a particular file server, you cannot prevent that administrator from running the tasks that process that file server.

For more information about using administrator permissions, see the "Managing Administrator Security" chapter in the Administrator's Guide.

Permissions required by Exchange Provisioning task [Ref 843908]

If you configure the Exchange Provisioning task to log on as a user other than the Vault Service account, you must give the account extra permissions, as follows:


File System Archiving

Installing the Placeholder Service on a remote NTFS file server

If you are installing the Placeholder service using the Install Placeholder wizard in the Administration Console, then the remote file server must have the following prerequisite software installed:

Alternatively, you can install the Placeholder service on a file server using the Windows Installer kit:
Enterprise Vault\EVPush\Agent\Enterprise Vault File System Archiving.msi

If you install the MSI kit on a file server running Windows Server 2003, then the prerequisites for the remote file server are as follows:

When you install the Placeholder Service using the Install Placeholder wizard in the Administration Console, you must supply the credentials of a user account that has administrator permissions on the file server.

Placeholder services in a VCS cluster

When installing Placeholder services in a VCS cluster, the following additional step is required.

After Installing VCS Authentication client on the Enterprise Vault server, you need to set up a trust between the Enterprise Vault server and the Veritas Security Service Root Broker for VCS (VCS SS Broker). This only needs to be done once, not for each node.

To set up the trust:

  1. Navigate to: C:\Program Files\VERITAS\Security\Authentication\bin
  2. Enter the following line:
    vssat setuptrust –broker <VCS_SS_Broker> --securitylevel low
    For example,
    vssat setuptrust --broker VCS2 --securitylevel low
  3. If the trust is successfully created, the following message is displayed:
    setuptrust
    ----------------------
    ----------------------
    Setup Trust With Broker: vcs2
    ----------------------

Creating archive points on NTFS volumes

When you create a new folder archiving target, the New Folder wizard enables you to create folder archive points. To create an archive point for a volume, use the ArchivePoints.exe command line tool.

You can view and edit archive points using the new Archive Point wizard, which is started by right-clicking a volume in the Administration Console, and selecting the menu option Archive Points.

Celerra placeholder delete option restricted to volume level [Ref 841475]

The placeholder folder policy option Delete archived file when placeholder is deleted does not apply to Celerra devices. For Celerra volumes, use the same option in the volume policy properties.

Avoiding duplicate placeholder shortcuts [Ref 854415]

Archived items can be deleted unintentionally when you are using the policy settings Delete archived file when placeholder is deleted or Delete archived file when placeholder is recalled.

The typical situation in which this occurs is as follows:

  1. A user inadvertently deletes some files that are needed.
  2. The help desk restores the whole folder to a temporary location so that the user can copy the required files. If the restored folder contains placeholder shortcuts, these may now be duplicates.
  3. The user checks the files, copies the ones that were inadvertently deleted, and then deletes the temporary folder. This can have the following consequences:

It is possible to turn off the automatic deletion by setting the registry values DeleteOnRecall and DeleteOnDelete, but these registry values affect the whole file server. Thus, disabling automatic deletion for that one user also disables automatic deletion for all users on that file server. See Automatic deletion of archived items for a description of these registry values.

It may be possible to restore the folder to a temporary location without restoring any placeholder shortcuts.

Alternatively, instead of restoring the items to a temporary folder on the same file server, if the placeholder shortcuts have been backed up from an NTFS volume, it may be possible to restore them to a file server that does not have DeleteOnDelete or DeleteOnRecall set.

Automatic deletion of archived items [Ref 846814,846052]

Enterprise Vault 7.0 volume policies and folder policies have the following options that enable you to control the deletion of archived items:

Caution

If you use these settings, take care to avoid duplicate placeholder shortcuts, otherwise it is possible to delete archived items unintentionally. See Avoiding duplicate placeholder shortcuts for more information.

When a placeholder is deleted or recalled, the policy is applied in two stages, as follows:

  1. The setting of Delete archived file when placeholder is recalled or Delete archived file when placeholder is deleted are checked to see whether the policy requires the archived item to be deleted.
  2. If the policy requires that the item is to be deleted, a server registry value is checked to determine whether the deletion is allowed.

The registry entries that control whether deletion is allowed are as follows:

Registry entry

Type

Values

DeleteOnDelete

DWORD

0: (Default) Do not allow the deletion of an archived item when its placeholder is deleted.

1: Allow the deletion of an archived item when its placeholder is deleted.

DeleteOnRecall

DWORD

0: (Default) Do not allow the deletion of an archived item when its placeholder is recalled.

1: Allow the deletion of an archived item when its placeholder is recalled.

These registry values are created automatically by the Placeholder service the first time it starts, under the following location:

 
HKEY_LOCAL_MACHINE
 \SOFTWARE
  \KVS
   \Enterprise Vault
    \FSA
     \ArchivedFilesFlags

For NTFS devices the registry on the file server is used, which is the one that is local to the Placeholder service.

For NetApp and Celerra devices, the registry that is used is the one on the Enterprise Vault Storage Service server that archives the volume.

The default values of DeleteOnDelete and DeleteOnRecall prevent the automatic deletion of archived items. If you change either value you must restart the appropriate service the in order to implement the change, as follows:

These registry entries give you the flexibility to control, for each file server, whether the policy settings for Delete archived file when placeholder is deleted and Delete archived file when placeholder is recalled are obeyed.

Note that the policy that is applied when a placeholder shortcut is deleted or recalled depends to some extent on the type of device that is being archived, as follows:

Preparation for FSAUtility [Ref 859092]

If you intend to use FSAUtility to restore files, you must do the following so that multiple file recalls do not exceed the recall limits:

  1. Set the BypassRecallLimitsForAdmins registry entry so that multiple file recalls do not exceed the recall limits:
    1. If the file server is a NetApp device, start the Administration Console, open the properties of the file server and select Ignore recall limits for local administrators.
    2. For other file servers, create a DWORD entry called BypassRecallLimitsForAdmins under the following registry key: on the file server that runs the Placeholder service:
c.   
d.  HKEY_LOCAL_MACHINE
e.   \SOFTWARE
f.    \KVS
g.     \Enterprise Vault
h.      \FSA
     \PlaceholderService
    1. Give BypassRecallLimitsForAdmins a value of 1 to enable local administrator accounts to bypass the recall limits.
  1. Use FSAUtility from an account that has local administrator permissions on the file server that is running the Placeholder service or, if the device is a NetApp fileserver, the Enterprise Vault server where the associated archiving task is configured.

Copying or restoring placeholders for very large files [Ref 32648]

When copying or restoring a placeholder for a large file, typically hundreds of megabytes, it may not be possible to retrieve the file. The user receives the error Cannot copy filename: The remote storage service was not able to recall the file. where filename is the name of the file.

At the same time, an event such as the following is logged to the Enterprise Vault event log:

Event Type: Error

Event Source: Enterprise Vault

Event Category: File Placeholder Service 

Event ID: 20539

Date: 23/11/2006

Time: 16:01:35

User: N/A

Computer: MYSERVER

Description:

Downloaded file is not the expected size

The problem is due to an IIS file size restriction.

The file can be restored successfully using Archive Explorer.


Exchange Server archiving

Exchange System Manager on Enterprise Vault servers [Ref: 29546]

If Exchange Server archiving is being implemented, Enterprise Vault servers with an Exchange Mailbox task, Exchange Journaling task, or the Storage Service must have the Exchange System Manager tools and fixes shown below:

Operating System on
Enterprise Vault Server

Exchange Server Version

Exchange Server 2000

Exchange Server 2003

Windows Server 2003

  • Exchange Server 2003 Exchange System Manager
  • Exchange Server 2003 Exchange System Manager

Windows 2000 Server

Vault Service account 'Send As' permission on Exchange Servers

As a result of the Microsoft Exchange 2003 Service Pack 2 updates (KB912442 and KB916803) there have been changes to the Send As Exchange permission. These changes are detailed in the following knowledge base article: http://support.microsoft.com/kb/912918.

If you have installed these updates, you need to check whether the Vault Service account still has Send As permission on the Exchange servers.

For information about how to set up Exchange Server permissions, see the Enterprise Vault Installing and Configuring guide.

Mailbox permissions for groups

Enterprise Vault synchronizes mailbox permissions to the corresponding archives. If a group with Full mailbox access or Owner permissions has access to the mailbox then, after synchronization, every member of the group will have the equivalent access to the archive.

You are recommended to check that mailbox permissions are set correctly before you install Enterprise Vault 7.0.

Synchronizing mailbox permissions [Ref: 29084]

Enterprise Vault synchronizes permissions for each newly-enabled mailbox. In the Administration Console, the permissions for the corresponding archive show that only the mailbox owner has access. (This is the equivalent of the SELF mailbox right.)

If, however, additional users have been granted Full Mailbox rights (using the Extended Mailbox Rights tab in Active Directory Users and Computers) you may see a much more extensive list because the synchronization includes other mailbox rights such as 'Enterprise Admins', 'Exchange Domain Servers', and so on. This behavior results from the way Active Directory handles permissions and is expected.

Message Classes [Ref:CAP-0924]

In this release, new message classes can be added using the Message Classes tab in Directory properties. You can include or exclude message classes in Exchange Mailbox, Exchange Public Folder and Exchange PST Migration policies.

When you add a new message class in Directory properties, it is displayed in the message class list in each policy, but is not selected; that is, these message types will be excluded. To include the new message type, you need to select them explicitly in policies.

There has been a change to the way that Enterprise Vault resolves conflicts in situations where wildcarded message classes are added, and subsets of the message class are already selected for inclusion in policies. Now, an exclude condition is only honored if the excluded message class is a subclass of an existing included message class.

The following examples illustrate how Enterprise Vault resolves such conflicts:


Enterprise Vault 7.0 OWA 2003 Extensions [CAP-0951]

Exchange Server 2003 hotfixes may modify OWA control files. If you have installed an Exchange Server 2003 hotfix that has created an unsupported version of the OWA control files folder, or modified any files in the control files folder, a “Save file error” will be reported when you attempt to install the Enterprise Vault OWA Extensions.

The Enterprise Vault 7.0 OWA Extensions provide support for the following versions of OWA 2003 control files:

Exchange Server 2003 SP1

<Exchange install folder>\exchweb\6.5.7226.0

Exchange Server 2003 SP2

<Exchange install folder>\exchweb\6.5.7638.1

Exchange Server 2003 SP2 +
Hotfix KB 911829 v 1

<Exchange install folder>\exchweb\6.5.7651.9

Exchange Server 2003 SP2 +
Hotfix KB 911829 v 2

<Exchange install folder>\exchweb\6.5.7651.25

Exchange Server 2003 SP2 +
Hotfix KB 924334

<Exchange install folder>\exchweb\6.5.7651.43


Installing SMTP archiving license

Enterprise Vault licenses are automatically installed by the Enterprise Vault Admin service. To install the SMTP Archiving service on a separate Windows SMTP Server computer, that does not have the Enterprise Vault Admin service, follow the instructions given in the support note, http://entsupport.symantec.com/docs/286104.


Enterprise Vault clients

Enterprise Vault User Extension version support

For information on which Enterprise Vault client versions work with which Enterprise Vault server versions, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.

If users have the Beta version of the Enterprise Vault 7.0 User Extensions installed, these must be removed before installing the released version of the User Extensions.

Use the same type of Enterprise Vault User Extensions when upgrading. This means that existing User Extensions should be upgraded to Enterprise Vault 7.0 SP2 User Extensions, and Self-Installing User Extensions should be upgraded to Enterprise Vault 7.0 SP2 Self-Installing User Extensions.

If you want to upgrade from User Extensions to Self-Installing User Extensions or vice versa, additional steps are required. For details, see the support note, http://entsupport.symantec.com/docs/286107.

Installing the User Extensions on Enterprise Vault servers

The Enterprise Vault server installation includes the User Extensions. You cannot do a separate installation of the User Extensions on an Enterprise Vault server.

Offline Vault

Due to restrictions in cross-domain security, Offline Vault is not supported if the user's computer is in an untrusted domain.

Running Archive Explorer in a stand-alone browser session

You may want to use Archive Explorer in a stand-alone browser session, for example if you are implementing File System Archiving. You do not need to configure policy settings, but you will need to send the required users the Archive Explorer URL. This will take the form:

HTTP:\\ev_webserver\EnterpriseVault\archiveexplorerui.asp

Changes to WebApp.ini settings for Archive Explorer

The following WebApp.ini settings, which controlled aspects of Archive Explorer behavior, are no longer supported. If you have any of these settings in WebApp.ini you are recommended to remove them:

Known issues

This section describes known issues with Enterprise Vault servers and clients.

You may want to inform users of the behavior described in Enterprise Vault User Extensions.

Installing and upgrading Enterprise Vault

Monitoring database configuration fails if you specify a UNC path for the data and log files [Ref 989888]

The Enterprise Vault Configuration wizard prompts you to specify the locations on the SQL server for the Monitoring database data and log files. If you enter a UNC path such as \\servername\C$\datafiles, the configuration of the Monitoring database will fail. Please specify a local path such as C:\datafiles.


Using Windows Installer

Installing MSI packages from a remote location [Ref 854463]

There is a Windows Installer limitation that may prevent you from installing the Deployment Scanner or Enterprise Vault User Extensions MSI packages when the installation file is in a remote location.

The solution is to copy the package to the local computer and install from there, or to copy the package to a network server that does not require Windows Installer to authenticate during the installation.


Enterprise Vault servers

Failure to update DCOM on x64-based versions of Microsoft Windows Server 2003 [Ref 842891]

When you run the Configuration wizard for a new installation of Enterprise Vault on an x64-based version of Microsoft Windows Server 2003, the following message may be displayed:

   Unable to update DCOM details

A report similar to the following is written to the event log:

   Event 10016



   The application-specific permission settings do not 

   grant Local Launch permission for the COM Server 

   application with CLSID {...} to the user username SID (...).  

This error is not fatal, and the services are created successfully. It is only the DCOM credentials that are not updated.

The same message may be displayed when you attempt to change the Vault Service account.

In both situations, you can use the following steps to force an update of the DCOM details:

  1. When the Configuration wizard has completed, stop the Enterprise Vault Admin service.
  2. Then restart all the Enterprise Vault services.
  3. Start the Administration Console.
  4. Right-click the Enterprise Vault Directory container in the left pane and select Properties.
  5. Click the Service Account tab to display the details of the Vault Service account.
  6. Change the Vault Service account password. You can re-enter the existing value.
  7. Click OK.
  8. This forces DCOM details to be updated.

The cause of this problem is a known Microsoft issue with updating DCOM details on x64-based versions of Microsoft Windows operating systems. See the Microsoft Knowledge Base article http://support.microsoft.com/?kbid=899965. Do not use the workarounds described in the Microsoft article. Instead, use the steps described above to update DCOM details.

Resource allocation

If you encounter problems that may be due to resource allocation issues, you are recommended to apply registry keys as described in the Microsoft Knowledge Base article Server is unable to allocate memory from the system paged pool (http://support.microsoft.com/default.aspx?scid=kb;EN-US;312362).

Size of collection files [Ref 857282]

The default size of a collection file is 10 MB. The Help for the Collections tab of Vault Store Partition properties incorrectly states that the default size of a collection file is 200 MB.

For performance reasons, do not make the size of a collection file larger than 10 MB.

Searching archives using the Administration Console archive search [Ref: 851558]

In the Administration Console, an administrator with access permissions on an archive can search the archive by right-clicking the archive and selecting Search Archive. This feature is not supported on systems that do not have Outlook installed on the Enterprise Vault server, for example, in FSA or SharePoint archiving only environments.

Error on shutting down Admin Service [Ref 32730]

When shutting down the Enterprise Vault Admin Service it is possible for an event such as the following to be logged in the Enterprise Vault event log:

Event Type: Error

Event Source: Enterprise Vault 

Event Category: Index Server 

Event ID: 8390

Date: 02/11/2006

Time: 07:55:01

User: N/A

Computer: MYSERVER

Description:

The EnterpriseVault.DirectoryConnection object reported an error.

 

General access denied error

The event is generated because it is possible for the Directory Service to shut down before the Indexing or Storage services. You can ignore this event if it is logged when the Admin Service is shut down.


Roles-based administration

"Failed to load the Authorization store" message when starting the Administration Console [Ref 859608]

If you receive the following message when you start the Administration Console as a user other than the Vault Service account, close the Administration Console and choose the option to save the console settings. Then restart the Administration Console.

Failed to load the Authorization store 'path\EvAzStore.xml'

Reason: The name of the directory machine cannot be blank.

Check that the Vault Directory Service is running and the 

computer is reachable on the network.

PST migration

Hard disk searches fail on NetApp VFiler devices

The PST Locator task cannot perform hard disk searches for PST files on NetApp VFiler devices.

Memory leak when accessing or creating PST files [Ref 764355]

There is a risk of a substantial memory leak when running Microsoft Outlook 2003 SP2 with the Enterprise Vault server or client software. The leak occurs when Enterprise Vault accesses or creates PST files.

For details of the problem and a link to the Outlook 2003 update that removes the risk of the memory leak, see the following support document: http://entsupport.symantec.com/docs/281568.


File System Archiving

New Volume wizard does not list all hidden shares [Ref 849772, 848955]

When you run the New Volume wizard to add a new volume for archiving, the second page of the wizard asks for the name of the share to add. If you click Browse and then choose to list "Hidden" shares, the resulting list shows only drive root hidden shares (C$, D$, and so on). If the hidden share you require is not shown, click Cancel to close the list of shares and then type the name of the share.

Error when synchronizing auto-enable folders [Ref 857290]

When Enterprise Vault synchronizes folder policies an error similar to the following is logged for each auto-enable folder that does not have a folder policy:

** Warning *** - One more Root folders were not synchronized



        Root folder: \\evdemo.demo.local\fsa1\user is not 

        synchronised as it is not marked with a policy

You can ignore these errors when they refer to auto-enable folders.

Unicode characters in ZIP file names are corrupted [Ref 796082]

Unicode characters in the names of ZIP files (or in the names of files stored inside a ZIP file) are incorrectly handled, with the result that you cannot subsequently open such files.

Note that this is a limitation of the ZIP file format, which does not currently support the use of Unicode characters in file names.

Creating an fpolicy on Network Appliance Vfiler systems [Ref 700551]

A limitation with versions of Network Appliance Data ONTAP earlier than Data ONTAP 7.2 prevents Enterprise Vault from working correctly with Network Appliance MultiStore Vfiler systems. Enterprise Vault is unable to create an fpolicy on the filer automatically, and an error message appears in the event log on the Enterprise Vault server.

For details of how to create an fpolicy for Enterprise Vault to use, see the following support document: http://entsupport.symantec.com/docs/280369.

"Exception handle" message when installing Placeholder service on a clustered file server  [Ref 859485]

You may receive the following message when you use the Install Placeholder wizard to install the Placeholder service on a remote file server that is a member of a VERITAS or Microsoft Cluster Server cluster:

Inside ThreadToPush exception handle. Unknown error

If you receive this message, close and restart the Administration Console, and then re-run the wizard.

Uninstalling Enterprise Vault Placeholder Services

You must uninstall Enterprise Vault before uninstalling the Enterprise Vault Placeholder service. You may prefer to disable the Enterprise Vault File Placeholder Service instead of uninstalling it.


Enterprise Vault monitoring and reporting

Monitoring database and Monitoring agents

To troubleshoot problems with the Monitoring database or the Monitoring agents, see the following document on the Symantec Support Web site: http://entsupport.symantec.com/docs/285813.

Enterprise Vault Operations Manager

To troubleshoot problems with installing or using Enterprise Vault Operations Manager, see the following document on the Symantec Support Web site: http://entsupport.symantec.com/docs/285814.

Enterprise Vault Reporting

To troubleshoot problems with installing or using Enterprise Vault Reporting, see the following document on the Symantec Support Web site: http://entsupport.symantec.com/docs/285815.


Enterprise Vault searching in East Asian languages [Ref 849912]

Enterprise Vault does not currently permit case-insensitive searches for full-width characters in East Asian languages (for example, Japanese). For more information, see the following document on the Symantec Support Web site: http://entsupport.symantec.com/docs/286028.


Enterprise Vault User Extensions

Upgrading Self-Installing User Extensions [Ref 859256]

The installation process currently prompts users to restart their computer before the installation complete page is displayed. If users click Yes on the restart prompt, the End Program dialog is displayed for Outlook. This dialog is displayed because Windows is trying to shut down Outlook but the installer is trying to open the installation complete page. Users can safely ignore the End Program dialog and click No on the Do you want to save changes? prompt.

Outlook 2003 in Exchange Cached Mode

When the User Extensions are used with Outlook 2003 in Exchange Cached Mode, manual archive and restore behave as though the Self-Installing User Extensions were installed:

If the user turns off Exchange Cached Mode, manual archive and restore behave normally.

Enterprise Vault icons not displayed

When in Exchange Cached Mode, some computers do not display the Enterprise Vault icons until an archived item is opened. The icons then appear for the current Outlook session but have disappeared when Outlook is restarted. Symantec are discussing the solution to this problem with Microsoft.

Searching archives with delegate access [Ref 858792]

If user A grants user B permission to view an Outlook folder then, when user B searches archives, user A's archive is not visible by default in the list of available archives.

To solve this, user A must edit the mailbox root properties and, on the Permissions tab, add user B and grant the permission Folder visible.

Folders set as non-deletable in EVPM may still be deletable [Ref 604111, 701091, E894933, E917484, E917486]

An Outlook user can, in some circumstances, delete a mailbox folder created by the Enterprise Vault Policy Manager (EVPM) script utility, even though the folder has been set to NonDeletable by the script.


Client-driven PST migration

Automatic space allocation in client-driven PST migration [Ref 326913]

In Enterprise Vault 7.0 you can configure the Enterprise Vault User Extensions so that they automatically upload PST files so that they can be migrated. Items that will be migrated from PST files can be automatically added to Offline Vault, so they do not need to be downloaded after migration.

There is a setting, Automatically add space to offline archives, that should enable offline vaults to grow automatically to accommodate items added as a result of the PST Migration. Currently this automatic growth does not happen.

If you want migrated items to be automatically added to Offline Vault, ensure that the maximum size of offline vaults is sufficient to accommodate the new items.

Accessing PSTs on mapped drives using RPC over HTTP [Ref 806946]

When a user is connected to Exchange Server using RPC over HTTP, mapped network drives are unavailable. If a user's PST file is on a mapped network drive, client-driven PST migration fails because Outlook is unable to access the PST file.

The user receives Outlook errors similar to the following:

The path specified for the file Z:\myoldmail.pst is not valid.
An error occurred while reconnecting Z: to \\192.168.0.2\pst

Microsoft Windows Network : The network path was not found.

This connection has not been restored.

Client-driven PST migration will continue when the PST file is again available to Outlook.


Archive Explorer

Archive Explorer may not show old items [Ref 29572]

Archive Explorer uses new indexing properties to find archived items. This means that items archived with Enterprise Vault versions before 3.7 will not appear in Archive Explorer until you replay the archive indexes using the Index Volume Replay utility, which is described in the Utilities guide.

Archive Explorer view of new Exchange Server mailbox archive [Ref 29509]

If there have been no items archived from a newly-created mailbox, Archive Explorer does not show the mailbox's folder structure. This is expected.

The folder structure will be shown after the next run of the Exchange Mailbox archiving task. Alternatively, you can manually archive an item from the mailbox.

Archive Explorer on Windows 2003 [Ref 29233]

When Archive Explorer is first used on Windows 2003 then, if the web site is not in the trusted sites zone, the user must choose to add it to the trusted sites zone. Once this has been done, Archive Explorer must be closed and restarted and will work correctly thereafter.

If Archive Explorer is not restarted, any attempt to access archived items produces an Internet Explorer Script Error similar to one of the following:

An error has occurred in the script on this page

Error: Permission denied

Do you want to continue running scripts on this page?



An error has occurred in the script on this page

Error: Access is denied

Do you want to continue running scripts on this page?

Windows Desktop Search (WDS)

Administrator privileges required for WDS search of online archive

Searching offline archives using WDS is supported in both the Enterprise Vault User Extensions and the Self-Installing User Extensions. This feature is enabled using an Offline Vault setting in the Exchange Mailbox Policy. Users do not need Administrator privileges on their desktop computer to use this feature.

Additionally, Desktop settings in the Exchange Mailbox Policy enable users to search their online archive using WDS. Microsoft registry restrictions mean that users must have Administrator privileges on their desktop computer to use this feature.

Offline Vault option in WDS

The option Offline Vault will show up in the WDS Location menu for any user, regardless of whether that user has Offline Vault enabled.

Re-enabling WDS plug-in after uninstalling/reinstalling User Extensions

The Enterprise Vault WDS plug-in is installed, but not enabled by default, when you install the User Extensions or Self-Installing User Extensions.

When you enable the WDS plug-in, the evoffline:// search location becomes available in the WDS Locations list.

If you uninstall the User Extensions or Self-Installing User Extensions, the WDS plug-in is disabled and uninstalled, as you would expect. But the evoffline:// search location still appears in the WDS Locations list, even though it cannot be used, because WDS has failed to remove it.

If you then reinstall the User Extensions or Self-Installing User Extensions and do not re-enable the WDS plug-in, the evoffline:// search location will mislead users into thinking that the plug-in is enabled.

So if you uninstall and reinstall the User Extensions or Self-Installing User Extensions, you need to re-enable the WDS plug-in. For details of how to do this, see the Enterprise Vault Installing and Configuring guide.

Duplicate search results in WDS [Ref CAP1077, 798822]

It is possible for WDS to show duplicate search results in either of the following circumstances:

eLearning courses

The following Symantec Education eLearning courses are included in the Enterprise Vault 7.0 release media. They will help you get the most benefit from your investment in Symantec software. 

Note: Compliance Accelerator and Discovery Accelerator are optional components of Enterprise Vault.

Pointers to Enterprise Vault documentation

All the Enterprise Vault documentation is available online.

The following documentation is available in the Documentation folder on the Enterprise Vault 7.0 media:

Document

File names

Comments

Introduction and Planning

Introduction_and_Planning.pdf
Introduction_and_Planning.chm

Provides an overview of Enterprise Vault functionality.

Installing and Configuring

Installing_and_Configuring.pdf
Installing_and_Configuring.chm

Provides detailed information on installing and configuring Enterprise Vault.
Instructions for upgrading from an earlier release are now included in this ReadMeFirst, not in the Installing and Configuring guide.

Administrator's Guide

Administrators_Guide.pdf
Administrators_Guide.chm

Includes backup and recovery procedures.

Registry Values

Registry_Values.chm

A reference document listing registry values that can be used to modify many aspects of Enterprise Vault behavior.

Enterprise Vault Help

EV_Help.chm

Includes all the other documentation so it is possible to search across all files.
Available from within the Administration Console by clicking Help and then Help on Enterprise Vault.

Administration Console Help

Admin_Console_Help.chm

The Help for the Enterprise Vault Administration Console.

Utilities

Utilities.pdf
Utilities.chm

Describes Enterprise Vault tools and utilities.

For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).

Legal notices

Copyright © 2007 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, VERITAS, the VERITAS Logo, and Enterprise Vault are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

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 Symantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

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, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. 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.

Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
http://www.symantec.com