Last updated: 12-Jul-2007

ReadMeFirst for Enterprise Vault™ 2007

This document describes the changes introduced by Enterprise Vault 2007. For the most up-to-date version of this document, see http://entsupport.symantec.com/docs/288394 on the Enterprise Vault support Web site.

IMPORTANT
If you are using Domino mailbox archiving, you must install the cumulative hotfix available from the Symantec support Web site at http://entsupport.symantec.com/docs/289577.

Before you install or upgrade to Enterprise Vault 2007, it is important to read Points to note and the issues sections.

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 2007 media.

If you are upgrading from an earlier version of Enterprise Vault, follow the instructions in Upgrading to Enterprise Vault 2007. The upgrade to Enterprise Vault 2007 applies changes to the Enterprise Vault Directory database schema, so it is particularly important that you follow the upgrade instructions carefully when upgrading multiple Enterprise Vault servers that access the same Enterprise Vault Directory.

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

For the latest information on Enterprise Vault 2007 sizing and performance, see the Enterprise Vault Performance Guide (http://entsupport.symantec.com/docs/288395).

The Enterprise Vault Administration Console and documentation are available in Japanese and Simplified Chinese. You can download a localized version of the ReadMeFirst document from the Symantec support Web site at http://entsupport.symantec.com/docs/288194 (Japanese) or http://entsupport.symantec.com/docs/288140 (Simplified Chinese).

Contents

New features and changes in Enterprise Vault 2007

This release provides the following new features:

Lotus Domino mailbox archiving

Domino mailbox archiving enables you to archive from users' mailboxes according to policies that you define.

For Domino mailbox archiving, you must first install Domino Server on the computer that is to host the Enterprise Vault server. This Domino Server is called the Enterprise Vault Domino Gateway and it enables Enterprise Vault to access target mail servers in the domain. In a production environment, the Enterprise Vault Domino gateway should not be used as a mail server.

Lotus Notes Client must also be installed on the Enterprise Vault Domino Gateway.

To enable archive search, you must configure Single Sign-On on the Enterprise Vault Domino Gateway.

You configure Domino mailbox archiving in the same way as you configure other types of archiving; using the Administration Console to add target Domino mail servers, archiving policies, and tasks to the Enterprise Vault Directory. You identify the mailboxes that are to be archived using provisioning groups.

Before items in a mailbox can be archived, the mailbox must be prepared using the Enterprise Vault Domino Provisioning task. This task does the following:

After mailboxes have been enabled for archiving, a Domino mailbox archiving task processes Domino mail servers to extract mail for archiving. A Domino mailbox archiving task has the following characteristics:

Enterprise Vault client templates enable users to do the following from their Lotus Notes and Domino Web Access clients. The new options appear under Tools on the menu bar:

The Enterprise Vault administrator can modify the functionality available in clients using settings on the Advanced tab of the Domino mailbox policy.

Lotus Domino Server and Lotus Notes Clients supported versions

For the latest information on Lotus Domino Server and Lotus Notes Clients supported versions, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).

Exchange Server 2007 support

Enterprise Vault 2007 supports archiving from Exchange Server 2007 with Mailbox Role installed. The following points summarize the main enhancements to Exchange Server archiving for Exchange Server 2007:

Note that Exchange Management Console (the management tool with Exchange Server 2007) is currently not supported on the Enterprise Vault server. To archive from Exchange Server 2007, install Exchange System Manager for Exchange Server 2003 on the Enterprise Vault server. Outlook 2003 is also still required on the Enterprise Vault server, even if all of your target Exchange servers are running Exchange Server 2007.

For detailed set up instructions see Installing and Configuring. For the latest information on supported software, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).

Office 2007 support

Enterprise Vault 2007 supports:

File System Archiving (FSA) enhancements

FSA Reporting

The new FSA Reporting feature enables the administrator to obtain summary reports on the active data on FSA file servers, and on the data that has been archived from them.

Note that FSA Reporting requires a SQL database that has been configured for mixed-mode authentication.

The reports include the following:

Many reports can provide either a summary for all file servers that have FSA Reporting configured, or a more detailed view for a specific file server. The reports include recommendations for improving your file lifecycle management policy.

The FSA Reporting Configuration wizard helps you to configure an FSA Reporting database and default data collection schedules. You can then configure individual file servers to specify non-default conditions. You can also specify whether data is to be collected on individual volumes. A facility is provided for starting and stopping data scans manually.

File Blocking

File Blocking enables you to do the following:

It is possible to select which folders to monitor and which to ignore. You have the option to scan the contents of compressed files, such as ZIP files.

You configure File Blocking by defining File Blocking rules in an FSA volume policy.

FSA Agent

The new FSA Agent provides the Enterprise Vault File Placeholder service, plus support for the File Blocking and FSA Reporting features.

FSAUtility enhancement

FSAUtility has a new command-line option, -o, with which you can delete orphaned placeholders - that is, placeholders for which no corresponding items exist in the archive. Deletion of orphaned placeholders from both NTFS and NetApp devices is supported. In addition there is now NetApp support for the existing command line options for bulk restore, move placeholders, recreate placeholders, and recreate archive points.

Retention Folders

The Retention Folder feature enables you to create folders automatically on file servers. The folders created are managed by Enterprise Vault and archived according to assigned policies. For example, you may want to create retention folders in users' home folders. Items placed in the retention folders will be archived by Enterprise Vault according to the policy assigned to each folder. Different folders in a retention folder hierarchy can have different policies assigned.

The retention folders created can be single folders or a hierarchy of folders. You define the archives to use for the retention folders by specifying where archive points are to be created.

64-bit filter drivers

Enterprise Vault 2007 includes 64-bit filter drivers. These are for AMD64 and Intel EM64T. There is currently no support for Intel Itanium.

Placeholders on NetApp devices [Ref E1077396]

Placeholders on NetApp devices now show the original file size instead of zero size (0 KB).

Enterprise Vault Operations Manager and Reporting enhancements

Enterprise Vault Operations Manager

The Operations Manager Web application has been extended to include:

Usability enhancements include the hiding of displays for non-configured features, and improved descriptions for vault store performance counters. There is also support for viewing multiple sites sharing a Directory database, if Operations Manager is installed on at least one Enterprise Vault server per site.

A new Operations Manager Configuration utility provides easier configuration and reconfiguration. For more details, see the Installing and Configuring manual.

Enterprise Vault Reporting

Enterprise Vault Reporting includes a number or new and enhanced reports:

If you have configured FSA Reporting, you also have access to the new FSA Reporting reports.

On installation or upgrade, a new SQL role 'EVReportingRole' is created on all SQL databases, to provide enhanced security and easier configuration.

A new Enterprise Vault Reporting Configuration utility now provides easier configuration and reconfiguration. For more details, see the Installing and Configuring manual.

Installation enhancements

The following installation enhancements are new at this release:

Index enhancements

Administration Console indexing enhancements

The following Administration Console indexing enhancements are new at this release:

Single index relocation through the Administration Console

At Enterprise Vault 7.0, administrators had to shut down services and manually modify the directory database after moving an index (volume) to a new location. At this release, the Administration Console does this without stopping Storage or Indexing services, leaving other archives available for searching and updates.

Failed items repair functionality

The list of failed items in the log (generated by the Indexing service at indexing time or later by IndexCheck) can be used by the Indexing service to repair the index volume, for example to try to re-index the failed items.

Report status of a rebuilding index

If an index update (including rebuilds and repairs) is invoked by the administrator, the Indexing service will generate an event log entry every 10,000 items to mark progress. The event will include information such as the number of processed items, percentage completed and estimated remaining time to completion. The admin job entry associated with the operation is also updated.

Deleted item recovery

Enterprise Vault can now retain items that have been deleted by users. This means that you have some time in which to recover items that users have deleted accidentally. The default retention period is 14 days. At the end of the retention period the items are permanently deleted.

You can recover deleted items by using the Deleted Items tab of an archive's properties. You can recover all items that have not yet been permanently deleted. It is not possible to select individual items for recovery.

this functionality is disabled in both new and upgrade installations. If you want to enable deleted item recovery, you can do so in the Administration Console by editing the Archive Settings tab of Site Properties.

For more details, see the "Recovering deleted items" section in the Administrator's Guide.

Language versions available

The Enterprise Vault Administration Console and Operations Manager, their help, and the administration manuals are available in English, Japanese and Simplified Chinese.

The Enterprise Vault Outlook User Add-Ins, extensions for Lotus Notes clients, Archive Explorer, Enterprise Vault Search applications and SharePoint Archive Search Web Parts are available in:

Note: The help for the Lotus Notes clients is not available in Hebrew.

Points to note

Changed prerequisites for Enterprise Vault 2007

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.

Deployment Scanner

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

Before installing Enterprise Vault 2007, 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.

Domino mailbox archiving

Lotus Hotfix required for Domino Mailbox Archiving

If you are implementing Domino Mailbox Archiving, you will need Lotus Hotfix 702HF589. To obtain this hotfix, raise a Problem Management Record (PMR) with IBM Support and apply for the hotfix.

Apply the hotfix to both Lotus Notes 7.0.2 and Domino Server 7.0.2 binaries on the Enterprise Vault Domino Gateway computer. (The hotfix is not required for Lotus Notes 7.0.2 on user workstations.)

For details of any updates to this hotfix, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).

names.nsf must be replicated on the Enterprise Vault Domino Gateway [Ref 1034897]

Enterprise Vault uses the Domino Directory in your target Domino Domain to gather user and environment information. It is therefore necessary to ensure that the Domino Directory is replicated frequently to all Enterprise Vault Domino Gateways, so that Enterprise Vault can recognize and archive new users, for example.

We recommend that you configure regular replication using your existing strategy for replicating system databases (for example, hub and spoke, connection documents, and so on). Alternatively, to force a manual replication of the Domino Directory, you can issue the following command on the server console of the Enterprise Vault Domino Gateway:

   repl domino_server_name names.nsf

where domino_server_name is the name of a Domino server that has an up-to-date replica of the Domino Directory.

EVMessages.nsf must be signed [Ref E1066548]

When Enterprise Vault is enabled or disabled for a Domino mail file, Enterprise Vault sends a message automatically to the mail file user. Template messages that you can edit using Lotus Notes are included in the message database file, EVMessages.nsf, which is installed with Enterprise Vault. Localized versions of this file can be found on each Enterprise Vault server, in the language folders under Enterprise Vault\Languages\Mailbox Messages. You need to edit the required localized version of the file, as appropriate, and then place it in the Enterprise Vault folder (typically, C:\Program Files\Enterprise Vault) on each computer hosting an Enterprise Vault Domino Mailbox Archiving task.

Before you can edit the message file, you must sign it using an appropriate Domino user ID. This signing user ID must be in the Execution Control List (ECL) on the workstation or server on which the message file will be edited. If your configuration has an existing ID set up for such purposes, you can use this.

Exchange Server 2007

Selective Journaling and Group Journaling with Exchange Server 2007[Ref E1038338]

Enterprise Vault Selective Journaling and Group Journaling are currently not supported with Exchange Server 2007.

SharePoint

Archiving from SharePoint 2007 Record Centers

When archiving from Record Centers on SharePoint 2007 servers (MOSS 2007), content is not deleted. This means that:

File System Archiving

Placeholder sizes

Placeholders created on Windows with Enterprise Vault versions before Enterprise Vault 6.0 SP2 will now show as having a zero size (0KB). This is a result of efficiency improvements in the filter driver.

For details of a conversion utility for legacy placeholders, see http://entsupport.symantec.com/docs/289557.

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:

·  Windows Server 2003
or Windows Storage Server 2003
or Windows Server 2003 R2
or Windows 2000 Server (SP3)

·  Windows Installer 3.1

·  Internet Explorer 6.0 or later

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.

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.

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.  HKEY_LOCAL_MACHINE
d.   \SOFTWARE
e.    \KVS
f.     \Enterprise Vault
g.      \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.

FAT32 volumes no longer supported [Ref E1024827]

You can no longer add FAT32 volumes as targets for File System Archiving at Enterprise Vault 2007.

If you added a FAT32 volume in Enterprise Vault 7.0 and applied a policy to it, the policy will still work when you upgrade to Enterprise Vault 2007. You can modify existing policies and add File Blocking, but you cannot apply new policies.

OWA and RPC over HTTP

EVServers.txt file is saved as a Unicode file

Enterprise Vault 2007 requires the EVServers.txt file on OWA 2000 and 2003 back-end Exchange Servers to be a Unicode file. When you upgrade the Enterprise Vault OWA Extensions, the installer will automatically save the existing EVServers.txt file as Unicode. The original file is saved as EVServers_ANSI.txt.

EVServers.txt file is located on back-end OWA 2000 and 2003 servers, in the Enterprise Vault\OWA folder (typically, C:\Program Files\Enterprise Vault\OWA).

Browser search availability in OWA and Outlook in RPC over HTTP mode [Ref E925460]

In previous releases, Enterprise Vault browser search was not available in OWA clients or Outlook in RPC over HTTP mode.

At this release, browser search is available, by default, in OWA 2007 clients. In OWA 2003 clients, browser search is available if Client Connection is set to Direct in the Exchange Mailbox Policy.

With Outlook in RPC over HTTP mode (Exchange Server 2003 and 2007), browser search is available when RPC over HTTP Connection is set to Direct in the Exchange Mailbox Policy.

Outlook Add-Ins and User Extensions

User Extensions renamed Outlook Add-Ins

The User Extensions and Self-Installing User Extensions have been renamed as follows:

Enterprise Vault 7.0

Enterprise Vault 2007

User Extensions

Outlook Add-In

Self-Installing User Extensions

HTTP-only Outlook Add-In

Self-Installing User Extensions

HTTP-only Self-Installing Outlook Add-In

The client files are now distributed on the Enterprise Vault distribution media under Enterprise Vault 2007\Outlook Add-Ins. The client files can be found in the following locations:

Changing from one type of Outlook Add-In to another

If you have installed one type of  Enterprise Vault Outlook Add-In, and want to change to another, you must first uninstall the current Outlook Add-In on user desktop computers.

Package Definition File (PDF) for deploying user extensions no longer included

In earlier releases, the Package Definition File, EVClient.PDF, was included in the kit to assist in deploying the Enterprise Vault User Extensions executable (.exe) using System Management Server (SMS). As the Enterprise Vault Outlook Add-Ins are now supplied as Microsoft Installer (.msi) files, the Package Definition File is not required, and is no longer included in the Enterprise Vault release.

Software no longer supported after Enterprise Vault 2007

The prerequisite software will change at the next version of Enterprise Vault after Enterprise Vault 2007; for example Internet Explorer 5.0 will no longer be supported and Internet Explorer 6.0 or later will be the new prerequisite version for both client and server. For full details of the changes, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).

Installation issues

Version 1.0.0.0 of Authorization Manager Runtime required for Roles-Based Administration [Ref 1010961]

If you are installing Enterprise Vault 2007 on Windows Server 2003 x64 or Windows 2000, and plan to use Roles-Based Administration, then you must ensure that version 1.0.0.0 of Authorization Manager Runtime (Microsoft.Interop.Security.AzRoles.dll) is installed and registered in the Global Assembly Cache.

This is also a requirement if you are upgrading to Enterprise Vault 2007 on one of these operating systems, and have implemented Roles-Based Administration on your existing Enterprise Vault system.

Instructions on how to register Microsoft.Interop.Security.AzRoles.dll in the Global Assembly Cache are included in the file, RUNTIME_REQUIREMENTS.txt, which is included in the Windows 2000 Authorization Manager Runtime download.

Alternatively, you can use the Microsoft .NET Framework 1.1 Configuration utility:

After registering Authorization Manager Runtime in the Global Assembly Cache, restart the Enterprise Vault Directory service.

MSMQ required for all archiving [Ref E1059843]

MSMQ is still a requirement for all types of archiving, including Domino.

If you install Enterprise Vault without MSMQ being present, it is not sufficient to install MSMQ later; you must install MSMQ and then re-install Enterprise Vault.

Failure to update DCOM on x64-based versions of Microsoft Windows Server 2003 [Ref 1009451, 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. 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.

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.

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

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.

Installing MSI packages from a remote location [Ref E989888]

There is a Windows 2000 Installer limitation that may prevent you from installing the Deployment Scanner or Enterprise Vault Outlook Add-Ins 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 2000 Installer to authenticate during the installation.

Domino installation issues

Domino Server license type for Enterprise Vault Domino Gateway [Ref E1038117]

You can use any of the IBM Lotus Domino Server types for the Domino Server installed on the Enterprise Vault Domino Gateway. The IBM Lotus Domino Messaging Server satisfies the minimum requirements in terms of application features.

EVInstall.nsf does not back up Forms6.nsf and Forms7.nsf [Ref E1072048, E1072049]

When you run EVInstall.nsf to install the Enterprise Vault client functionality, the installation modifies Forms6.nsf and Forms7.nsf but does not keep copies of the original versions.

You are recommended to make your own copies of these files before you run EVInstall.nsf. You will need the copies if there is a problem when running the installation.

To copy Forms6.nsf and Forms7.nsf, do the following:

  1. On the Enterprise Vault Domino Gateway, shut down Domino Server and then copy Forms7.nsf and Forms6.nsf from the iNotes folder to a safe location.

By default, the folder is C:\Program Files\Lotus\Domino\Data\iNotes

  1. On the Domino mail server, shut down Domino Server and then copy Forms7.nsf and Forms6.nsf from the iNotes folder to a safe location.

By default, the folder is C:\Program Files\Lotus\Domino\Data\iNotes

What to do if EVInstall.nsf fails [Ref E1070747]

If EVInstall.nsf fails, do the following:

b.      evdg_mail7.ntf
    evdg_dwa7.ntf
d.      Forms7.nsf
    Forms6.nsf
b.      ev_mail7.ntf
c.      ev_dwa7.ntf
d.      ev_mail6.ntf
    ev_inotes6.ntf
f.      Forms7.nsf
    Forms6.nsf

You can now run EVInstall.nsf again, as described in Installing and Configuring.

Names of template files on Domino Gateway server [Ref E1072696]

In Installing and Configuring, the names of the template files on the Enterprise Vault Domino Gateway server are incorrectly shown as ev_mail7.ntf and ev_dwa7.ntf.

The actual names are as follows:

    evdg_mail7.ntf
    evdg_dwa7.ntf

Console messages installing EVInstall.nsf [Ref E1046510]

When you run EVInstall.nsf to install the Enterprise Vault extensions, you may see messages such as the following in the Domino Server Console window. The messages are normal and can be ignored:

10/05/2007 10:36:22   Attempt by CN=administrator SYSTEM/O=MyDomain to create dupl
icate template StdR7Mail in database C:\Program Files\Lotus\Domino\data\ev_Mail7
.ntf - rejected.
10/05/2007 10:36:22   Attempt by CN=administrator SYSTEM/O=MyDomain to create dupl
icate template StdR7Mail in database C:\Program Files\Lotus\Domino\data\ev_Mail7
.ntf - rejected.
10/05/2007 10:36:42   Database ev_dwa7.ntf created by administrator SYSTEM/MyDomain
10/05/2007 10:37:07   Attempt by CN=administrator SYSTEM/O=MyDomain to create dupl
icate template dwa7 in database C:\Program Files\Lotus\Domino\data\ev_dwa7.ntf -
 rejected.

Removing Enterprise Vault from a Domino environment [Ref E1074455]

For details of the procedure for removing Enterprise Vault from a Domino mail server and an Enterprise Vault Domino Gateway server, see TechNote 289556 at http://entsupport.symantec.com/docs/289556.

Other Domino issues

Domino provisioning group defaults to 'Brief' indexing level [Ref E1074638]

When you create a Domino provisioning group the indexing level is always set to "Brief". The default setting in Site Properties is ignored and there is no option in the New Provisioning Group wizard to change the indexing level.

If you want to use an indexing level other than "Brief" you must edit the properties of the provisioning group and, on the General tab, select the required level.

New Domino user or group is not always visible [Ref E1003700]

If you create a new Domino user or group and then try to add that user or group as a provisioning target or assign permissions, you may find that the list shown in the Administration Console does not contain the new user or group. This is the result of out-of-date indexes on the Domino server.

To update the Domino indexes immediately, enter the following command in the Domino Server Console:

load updall names.nsf -V

When you have updated the Domino indexes you can see the new user in Administration Console lists.

Domino Archive Usage Limits [Ref E1013755, E1013793]

For most Enterprise Vault archiving you can set an Archive Usage Limit in Site Properties by editing the properties of the following:

In the case of Domino archiving, there is no setting available for individual archives. Additionally, the usage limit notification settings are ignored for Domino archives. You cannot configure Enterprise Vault to send usage limit notifications for Domino archives.

Email address lookup [Ref E1070731]

By default, Domino mailbox archiving does not look up SMTP addresses using the Domino Directory. If you are using Discovery Accelerator you are recommended to change this setting so that SMTP addresses are resolved when archiving.

This feature is controlled by the setting Lookup e-mail addresses, which is in the Archiving General section on the Advanced tab of the Domino Mailbox policy properties.

Archiving encrypted items [Ref E1067019]

The following issues can occur when archiving encrypted items to which a Notes user has the decrypt key:

Both these issues can be avoided if the Store in Vault policy setting is set to Hide Option.

DWA users do not see these issues.

Domino integrated search in two-domain configuration [Ref E1070830]

If Domino mailbox archiving is configured with the Enterprise Vault Domino Gateway in a different DNS domain from the Enterprise Vault server, the Enterprise Vault integrated search page is not displayed correctly from Lotus Notes.

The following procedure provides a workaround that enables users to display the integrated search page.

  1. Open a browser window.
  2. In the browser Address field, enter http://EV_Server_Name/EnterpriseVaultDomino/search.asp, where EV_Server_Name is the name of the Enterprise Vault server where the archive is located.
  3. Press Enter. A login dialog is displayed.
  4. In the login dialog, enter your usual Domino user name and Internet password, and the Domino domain of the Enterprise Vault server.
  5. Press Enter.

Forward and reply options do not always recall original message [Ref E1048646, E1073660, E1074683]

In Lotus Notes 6.5 and 7.0 clients, some of the forwarding and reply options do not work correctly with Enterprise Vault shortcuts. When you use these options, the original message is not recalled. Instead, a new message including a copy of the shortcut is opened.

This problem affects the following:

The corresponding options on the Forward menu and the Actions menu all work correctly.

Cutting and pasting shortcuts is not supported [Ref E1073744]

Cutting and pasting Enterprise Vault shortcuts using the Notes client is not supported.

There are various issues with cutting and pasting shortcuts, including the following:

Notes client printing limitation

When a Lotus Notes user selects a shortcut document and then clicks the print icon, the shortcut document is printed, rather than the archived item. In order to print the item, the user must open the shortcut and view the item before clicking print.

This behavior results from a limitation of the Lotus Notes client extensions.

Cannot print archived item from DWA [Ref E1018924]

If you select an archived item in the Domino Web Access (DWA) client and click Print, the restore action fails and an error message is displayed.

If you view the item first, then you can print it successfully.

DWA users cannot log in to Enterprise Vault [Ref 1069873]

Domino mail users require an Internet password in order to access Enterprise Vault using the Domino Web Access (DWA) client. If you modify existing Domino mail users, for example to add an Internet password, the users will not be able to log in to Enterprise Vault until the names.nsf system database is updated on the Enterprise Vault Domino Gateway. You may also need to restart the Domino HTTP server on the Enterprise Vault Domino Gateway, to refresh the cache.

To force an update of names.nsf, run the following command on the Enterprise Vault Domino Gateway:

   repl domino_server_name names.nsf

where domino_server_name is the name of a Domino server that has an up to date version of the database.

To force the Domino HTTP server to refresh its cache, run the following command:

   tell http restart

DWA user not prompted after session has expired [Ref E1027977]

When DWA user's session has expired and the user clicks an Enterprise Vault Action button, there is no login prompt and the user is not informed that the session has expired.

The user can click any standard Notes button to get a login prompt.

Forwarding multiple shortcut messages with DWA fails to retrieve the original message content [Ref 1018760]

In the Domino Web Access (DWA) client, if you select multiple shortcut messages and then click Forward to send them all in a single message, the client fails to retrieve the original content of the messages. The forwarded message contains the shortcut banner but not the content of the messages, and any attachments to the messages appear as hyperlinks.

Domino Journal Health Report uses same name for multiple servers [Ref E1073427]

The Enterprise Vault documentation recommends that you use 'Symantec' as the name for the Domino journal location. The Domino Journal Health Report uses this name to identify the server. If you have multiple Domino servers, each server is listed with the same name, making it impossible to determine which is which.

Domino archiving limitations [Ref E1048970]

Enterprise Vault does not support archiving from Domino when users have mail files that share the same replica ID.

For example, the following are not supported:

DWA retrievals do not show encrypted content [Ref E1073778]

Retrieved encrypted items cannot be viewed when using DWA.

A user who attempts to use DWA to view an encrypted archived item is presented with standard Domino error text:

The body of this message is encrypted and cannot be decrypted.
1. You must import your Notes ID (which contains your certificates).
2. Import your internet certificate(X5.09) into your Notes ID for S/MIME.

Neither of the solutions suggested in the help text will fix the problem. The retrieved encrypted item cannot be viewed using DWA.

The user can restore the item and then view the restored item.

Support for clustered Domino mail servers

Enterprise Vault supports archiving from Domino mail servers in a clustered environment. In the Enterprise Vault Administration Console, when you add a Domino cluster server as an archiving target, Enterprise Vault lets you select a preferred server in the cluster from which to archive. When you double-click the target Domino server in the Administration Console, the Cluster page in the properties window enables you to change the preferred server.

Enterprise Vault archives mailboxes from the preferred server in a cluster. If a mailbox is not available on the preferred server, Enterprise Vault archives that mailbox from the server specified in the user's personal document.

Corrupt characters in Domino Traditional Chinese Welcome message [Ref E1069476]

When a mailbox is enabled for archiving the user receives a Welcome message. The Traditional Chinese message that is sent to Domino users contains some corrupt characters in the subject.

When you edit the Traditional Chinese Welcome message, as described in Installing and Configuring, delete the existing subject text and type a new subject. This fixes the corruption.

Exchange journal archiving issues

Duplicates created when archiving Exchange Server 2007 journaled messages [Ref DOR1357]

Microsoft Exchange Server 2007 has introduced a new process for dealing with journaled messages that are sent to a combination of recipient types (internal, external and distribution lists). In these situations, a message is duplicated in the journal inbox; for example, one contains details of the distribution list recipients and the other contains details of individual recipients.

Currently, to ensure that recipient information is not lost, the Enterprise Vault Journaling task archives each of the message duplicates, using the information provided in the P1 part of the message to index the item.

As a result, duplicate messages may be returned by searches performed using any of the Enterprise Vault search applications (Outlook Integrated Search, Browser Search, Compliance Accelerator and Discovery Accelerator). Duplicate data may also be captured by the Compliance Accelerator Journal Connector.

A hotfix will be issued at a later date to fix this.

SharePoint issues

SharePoint URLs and SSL [Ref E1042015]

If an existing SharePoint installation is later changed in a manner that affects the SharePoint URLs, you must ensure that SharePoint Alternate Access Mappings are configured correctly. This is the case when, for example, you change an existing SharePoint installation to use SSL or add an alias.

If the SharePoint Alternate Access Mappings are not correctly configured then you may receive the following error when attempting to add a SharePoint Web application target:

SharePoint Virtual Server cannot be found
Check that you entered the correct URL

For information on managing internal and public URLs, see the following article from the SharePoint Product Group:
http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

Shortcuts not created when document publishing enabled in SharePoint 2007 [Ref E1033222]

When archiving from SharePoint 2007 servers (WSS 3.0 or MOSS 2007), shortcuts are not created in document libraries where either Minor versions or Content Approval is enabled.

TCP/IP port exhaustion when archiving from MOSS 2007 servers [Ref E1045610]

When archiving items from Microsoft Office SharePoint Server 2007 (MOSS 2007), under certain conditions, the default number of ephemeral ports for TCP/IP client connections may be inadequate. If this happens, some items will not be archived from the SharePoint server and you may see error messages similar to the following in Enterprise Vault SharePoint archiving reports:

   System.Net.WebException: The underlying connection was closed:
   An unexpected error occurred on a send.

or

   Unable to connect to the remote server
   System.Net.Sockets.SocketException: Only one usage of each socket
   address (protocol/network address/port) is normally permitted.

You can increase the upper range of ephemeral ports that are dynamically allocated to client TCP/IP socket connections using the following registry entry:

HKEY_LOCAL_MACHINE
  \SYSTEM\CurrentControlSet
   \Services
    \Tcpip
     \Parameters
      \MaxUserPort

The default value of MaxUserPort is 5000. (Be aware that increasing this value significantly may cause high consumption of kernel memory).

You can also reduce the client TCP/IP socket connection timeout value using the following registry entry:

HKEY_LOCAL_MACHINE
  \SYSTEM\CurrentControlSet
   \Services
    \Tcpip
     \Parameters
      \TcpTimedWaitDelay

The default value of TcpTimedWaitDelay is 240 seconds.

For more information on troubleshooting ephemeral TCP/IP ports, see the Microsoft article http://msdn2.microsoft.com/en-us/library/aa560610.aspx.

Administration Console issues

Tasks may show 'Error' status after upgrade [Ref E1024939]

The first time you start the Administration Console after upgrading to Enterprise Vault 2007 you may find that the Tasks container shows that every task has a status of Error.

To fix the problem, restart the Task Controller Service on the Enterprise Vault server that hosts the tasks.

DTrace log files not generated if folder path contains double-byte characters [Ref E1074518, E1017764, E1069958]

On an English system, the Administration Console does not generate DTrace log files if the folder path name for the log files contains double-byte characters.

PST migration issues

Hard disk searches fail on NetApp MultiStore (Vfiler) devices [Ref E837476]

The PST Locator task cannot perform hard disk searches for PST files on NetApp MultiStore (Vfiler) devices.

Client-driven PST migration fails with RPC over HTTP [Ref E806946]

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.

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

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 support document http://entsupport.symantec.com/docs/281568.

File System Archiving issues

File Blocking incorrectly prevents file rename [Ref E1070603]

The Vault Service account and users who are on the exempt blocking list cannot rename files to file types that are blocked by the policy.

File Blocking in a clustered environment [Ref E1055044]

Prerequisites

Before adding a volume share to a virtual server:

Additionally, a volume share (disk group) that is managed by a virtual server must not be added as a volume target to any other virtual server.

Limitations

The following settings must be the same for all virtual servers in a cluster:

You can edit these settings on the File Blocking tab of each file server's properties.

Configuring the File Collector Service [Ref 1050048]

The Enterprise Vault File Collector Service uses the following parameters while collecting file summary. Currently, the only way to modify these parameters is to modify the SQL table 'Properties' in the EnterpriseVaultFSAReporting database. Any changes to these parameters are used in the next scan.

The parameters are as follows:

The default value of this parameter is as follows:

30,60,90,180,365,730,1095

You can, however, modify this list as required. The list must be in ascending order and has a maximum of 10 values.

The default value of this parameter is 10 MB. Thus, the 'Top N files' report list only those files whose size is not less than 10 MB. Because of this, the report may contain fewer than 100 entries. You can change this parameter as required. To see the top 100 files on a volume irrespective of their sizes, set MBLARGE to 0.

Set CheckDuplicates to False if you do not want to see the duplicate summary report after the current reporting scan. There will be a slight performance improvement in the File Collector Service if you set CheckDuplicates to False.

When you have changed any of these values you must restart every Enterprise Vault File Collector Service in order to implement the changes. For Netapp and Celerra devices, you must restart the Enterprise Vault Admin Service on every Enterprise Vault server that runs FSA services on behalf of the devices.

FSA Agent requirements on Windows 2000 [Ref E1070562]

If you are installing the FSA Agent on a file server running Windows 2000, note that the minimum requirement is Windows 2000 SP4 plus Update rollup package 1 for SP4.

NetApp Filer placeholder shortcuts appear to be 0 KB [Ref E1029910, E1017992, DOR1006]

Placeholder shortcuts created on NetApp Filers fail to reflect the original file size, appearing instead to be 0 KB, if either of the following conditions applies:

To avoid the second condition, you can append .UTF-8 to the language setting on the NetApp Filer. To do this, enter the following command from the NetApp Filer's administration console:

vol lang volume_name language_code.UTF-8

where volume_name specifies the volume, and language_code is the code for the language setting.

For example:

vol lang vol0 en.UTF-8

Note: You can view a list of the language settings the NetApp Filer supports by entering the following command:

vol lang

Placeholder service must be restarted if you manually reload the evfilter driver [Ref: DOR223]

If you manually unload and reload the Enterprise Vault evfilter driver when troubleshooting problems with FSA, you must restart the Placeholder service. You can do this using the Services snap-in (services.msc).

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

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.

New Volume wizard does not list all hidden shares [Ref E849772, E848955]

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.

FSA shortcut deletion [Ref DOR338]

FSA shortcut deletion now takes place at the time of the next Synchronization run following the scheduled time for shortcut deletion.

For example, if shortcut deletion is set for 2.00 am on Mondays, and the next Synchronization run is at 5.00 am on Monday, shortcut deletion will take place at 5.00 am.

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.

FSA Agent may conflict with Symantec AntiVirus [Ref E1066686]

When running on Windows Server 2003, the Enterprise Vault 2007 FSA Agent is incompatible with the email scanning features of some versions of Symantec AntiVirus. If this issue is encountered, the server may become unstable and may not restart correctly. Also, you may not be able to uninstall the FSA Agent.

Before installing the FSA Agent, you are recommended to make sure that you have Symantec AntiVirus 10.0 or later.

For complete advice on this issue, see the following TechNote on the Symantec Support Web site: http://entsupport.symantec.com/docs/289487.

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.

Creating an fpolicy on Network Appliance MultiStore (Vfiler) systems [Ref E700551]

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.

Enterprise Vault Outlook Add-Ins issues

Upgrading HTTP-only Self-Installing Outlook Add-Ins [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.

Archived items not opened in Outlook [Ref E1069895, E1055515, DOR-1755]

This issue applies only to the following combination:

If Archive Explorer is launched in a browser window, it may display an item as an HTML preview, even if you have selected Microsoft Outlook as the viewing option in Archive Explorer Settings.

This issue does not apply when Archive Explorer is launched within Outlook.

Archive Explorer menu options may not work correctly [Ref E1069893]

This issue applies when you are using either Enterprise Vault 7.5 Server or Enterprise Vault 7.5 Outlook Add-Ins (client extensions), or both. The issue applies only to clients on Windows Vista used with Internet Explorer 7 in protected mode.

If Archive Explorer is launched in a browser window, the following context menu options for an item in the results pane simply open the item as if you had clicked Open:

You can perform the operation you require from the opened item.

This issue does not apply when Archive Explorer is launched within Outlook.

Users may be unable to search archives after upgrade [Ref E1070698]

Immediately after upgrading to Enterprise Vault 2007, you may find that archive searches fail.

To fix the problem, restart the Indexing service on the Enterprise Vault server.

Outlook 2003 in Exchange Cached Mode

When the Add-Ins are used with Outlook 2003 in Exchange Cached Mode, manual archive and restore behave as though the Self-Installing Add-Ins are 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 E858792]

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 E917484]

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.

Archive Explorer issues

Archive Explorer may not show old items [Ref E29572]

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 E29509]

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 E29233]

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) issues

Administrator privileges required for WDS search of online archive

Searching offline archives using WDS is supported in both the Enterprise Vault Outlook Add-In and the HTTP-only Self-Installing Outlook Add-In. 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 Outlook Add-Ins [Ref 849115]

The Enterprise Vault WDS plug-in is installed, but not enabled by default, when you install the Outlook Add-Ins or HTTP-Only Outlook Add-Ins.

When you enable the WDS plug-in, the evoffline:// search location becomes available in the WDS Locations list. If you uninstall the Add-Ins, 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 Add-Ins 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 Add-Ins, you need to re-enable the WDS plug-in.

The recommended way to enable offline archive searching is to use the WDS search auto-enable setting in the Exchange Mailbox Policy. Alternatively, you can enable the plug-in during installation by including the command line parameter ACTIVATE_WDS_PLUGIN=1. Note that this command line switch is case sensitive. For example:

msiexec /I path_to_installer ACTIVATE_WDS_PLUGIN=1 /qn

where path_to_installer is the path to the required language version of the Enterprise Vault Add-Ins .msi file.

For further details on enabling WDS integration, 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:

Other issues

Index management requires Vault Service account [Ref E1073887]

In order to manage an archive's index you must be logged in as the Vault Service account. The functionality to rebuild indexes is then available as follows:

Manage Index Volumes gives you the same functionality of the IndexVolumeReplay.exe tool that was used to rebuild indexes in earlier releases. Note that the IndexVolumeReplay.exe tool is no longer available.

Outlook must be default email client [Ref E1028234]

If Outlook is installed on the Enterprise Vault server, it must be configured as the default email client even if you do not use Exchange mailbox archiving.

Cannot search for display names in Exchange 2007 journal archives

When Exchange Server 2007 journaled messages are archived, Enterprise Vault currently populates both the Email Address and Display Name attributes with the SMTP address. For this reason, any searches of Exchange Server journal archives for specific display names may not return the expected results. Similarly, any custom filters for Exchange Journal Archiving that filter on display names may not work as expected.

This problem only affects messages journaled by Exchange Server 2007. A hotfix will be issued for this at a later date.

File Groups Summary report does not reflect recalled files [Ref E1070546]

The Enterprise Vault Reporting "File Groups Summary" report does not take into account any archived files that are recalled to the file server. The report data indicates the numbers of archived files, and the space occupied and saved, as if the files had not been recalled.

'Largest Files' report is not available from 'Inactive Files per Server by File Group' report [Ref E1062451]

The Administrator's Guide chapter "Using Enterprise Vault Reporting" wrongly states that you can access the "Largest Files of a Specified File Type in a Volume" report from the "Inactive Files per Server by File Group" report.

Files are not archived or are recalled immediately [Ref E1064566, E1047492]

On computers that are monitored by Symantec Antivirus Corporate Edition versions earlier than 10.0.2.2000 you may find either of the following:

If this happens, you can either upgrade to Symantec Antivirus Corporate Edition version 10.0.2.2000 or later, or add EvPlaceholderService.exe to the ExcludedExes registry value, which lists programs that are prohibited from recalling archived items.

See the Registry Values manual and the File System Archiving chapter in the Administrator's Guide for information about the ExcludedExes registry value.

Port and protocol settings for the Web Access application URL [Ref E1074604]

You set the URL for the Web Access application on the General tab of Site Properties in the Administration Console.

The default URL is /EnterpriseVault.

The complete list of supported port and protocol settings is as follows:

URL

Description

/EnterpriseVault

The default URL. Suitable for use with building blocks. This uses the appropriate Storage service computer as required.

http://_server_/EnterpriseVault

A specific server. Not recommended if you are using building blocks.

For example:
http://MyServer/EnterpriseVault

https://_server_/EnterpriseVault

A specific server, using HTTPS. Not recommended if you are using building blocks.

For example:
https://MyServer/EnterpriseVault

:_port_/EnterpriseVault

Suitable for use with building blocks. Uses the specified port. This uses appropriate Storage computer as required.

For example:
:8080/EnterpriseVault

<https>:_port_/EnterpriseVault

Uses HTTPS and the specified port. Suitable for use with building blocks. This uses appropriate Storage computer as required.

For example <https>:8080/EnterpriseVault

For example, if you configure Domino to use SSL you probably also want to configure SSL for the Web Access application and so would use the following:
<https>/EnterpriseVault

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).

Third party file managers not supported

Enterprise Vault does not support third party file managers because they could cause placeholder corruptions and potential data loss for modified files. For more information, see http://entsupport.symantec.com/docs/289435

Operation Reports exported PDF files display incorrectly in Japanese [Ref E1060552, E1061364]

The Enterprise Vault Reporting Operation Reports do not display correctly when saved in PDF format on Japanese systems using SQL Server2000.

Enterprise Vault program group missing from Start menu [Ref E1069598]

If you change the locale from Japanese, Simplified Chinese or Traditional Chinese to English before installing Enterprise Vault, the Enterprise Vault program group will not appear when you click Start > Programs.

eLearning courses

Complimentary eLearning classes (a free one year subscription to the Enterprise Vault Tech Center for two logins) are included with your purchase of Enterprise Vault.

Enterprise Vault Tech Center features a collection of concise subject-specific on-demand modules that addresses key features, common questions, and advanced topics that you will encounter when using Enterprise Vault in your data center. The Enterprise Vault Tech Center features detailed information on the topics at hand and many modules include self-running demonstrations.

For each login:

  1. Go to http://www.symantec.com/ecampus/enterprise?siteName=vena&partNo=DP6002.
  2. Click Register and follow the directions.
  3. Check out and enter promo code EVTC75 during check out process. You are prompted with series of directions and sent an email with further registration instructions.

Instructor Led Training (ILT) and Virtual Training (VA) classes also available for more advanced training:

For more information on Symantec courses, see http://www.symantec.com/enterprise/training/training_by_country/index.jsp

Documentation

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

Document

File names

Comments

Introduction and Planning

Introduction_and_Planning.pdf
Introduction_and_Planning.chm

Provides an overview of Enterprise Vault functionality.

Deployment Scanner

Deployment_Scanner.pdf
Deployment_Scanner.chm

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

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 included in Upgrading to Enterprise Vault 2007.

Administrator's Guide

Administrators_Guide.pdf
Administrators_Guide.chm

Includes backup and recovery procedures.

Registry Values

Registry_Values.pdf
Registry_Values.chm

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

Utilities

Utilities.pdf
Utilities.chm

Describes Enterprise Vault tools and utilities.

Administration Console Help

Admin_Console_Help.chm

The Help for the Enterprise Vault Administration Console.

Enterprise Vault Operations Manager Help

EVOM.chm

The Help for the Enterprise Vault Operations Manager

Enterprise Vault Help

EV_Help.chm

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

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

Legal notice

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