This document is intended to give an overview of the changes introduced by Symantec Enterprise Vault 7.0 Service Pack 1 (SP1).
The installation media for Symantec Enterprise Vault 7.0 SP1 can be downloaded from the link at the end of this article.

Before installing or upgrading to Enterprise Vault 7.0 SP1, you must read this document which can be found in full as the file Updates.htm in the installation media, and also the ReadMeFirst (ReadMeFirst_EN.htm) for Enterprise Vault 7.0. For the most up-to-date version of the ReadMeFirst, see  http://support.veritas.com/docs/287448

For instructions on installing or upgrading to Enterprise Vault 7.0 SP1, see the Installing and Configuring manual, which is in the Documentation folder in the installation media.

For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at  http://support.veritas.com/docs/276547


High priority fixes


Changes to North America Daylight Saving Time [Ref 604106, 604108, 604109-1, 701083, 701087, 701092, E988772]

The 2005 Energy Policy Act passed by the U.S. Congress changed the dates of both the start and end of Daylight Saving Time (DST) for the U.S. and Canada. The DST changes will be applied in 2007. These changes may cause items to be indexed with an incorrect time stamp during the extended period of DST. This could result in the items being incorrectly excluded or included in searches using date-based criteria. In addition, the date and time properties of items with time stamps prior to 2007 may be presented as an hour later than the actual values.

For detailed information on this issue, see the following Enterprise Vault TechNote:  http://support.veritas.com/docs/286967

Note that the Enterprise Vault updates for this issue rely wholly on the deployment of the relevant Microsoft DST patches for Windows, Exchange Server, SharePoint, Outlook and any other applicable application. See the above TechNote for more information.

Symantec Corporation strongly recommends that you deploy the relevant Microsoft DST patches and Symantec Enterprise Vault Service Packs before March 11th 2007.

After installing this Service Pack, ensure that the following is done on all client machines on which users are performing Archive Explorer or Enterprise Vault browser searches:

ArchivePoints.exe may fail when creating a new Archive Point if Windows 2000 Server DST patch registry keys are not set correctly [Ref E988772]

After applying the Microsoft Windows 2000 Server DST hotfix (see  http://support.microsoft.com/kb/914387/en-us ) to an Enterprise Vault Server, you may find that you are no longer able to create Archive Points using ArchivePoints.exe, with the following error being reported:

This is indicative of a problem with the registry key settings that are added when the Microsoft Windows 2000 DST patch .reg file is applied. Please refer to the Microsoft knowledge base article referenced above, and confirm the validity of the registry key settings.


New features and fixes

Support for the Backup Exec 12 for Windows Servers Enterprise Vault Agent

Support for Internet Explorer 7 [Ref 604091-1, 604095-1, 604098, 701051, 701082, 701102, E861321, E900700, E851642]

Internet Explorer 7.0 is now supported for use with Enterprise Vault, including Archive Explorer, browser search, and Outlook Integrated Search.

Support for Outlook 2007 on users' workstations [Ref 604115, 604121, 701085, 701094]

Enterprise Vault now supports Microsoft Outlook 2007 on users' workstations.

Note:

Support for Exchange Server 2007

At this release Enterprise Vault can archive items from user and journal mailboxes on Exchange Server 2007 with Mailbox Role installed.
For further information, prerequisites and configuration steps please see the Updates_EN.htm file.

SQL stored procedure for backing up Enterprise Vault databases [Ref 701006]

This release includes the new SQL stored procedure, aspa_BackupEVDatabases, which enables you to back up all the Enterprise Vault databases managed by an SQL Server or SQL Server instance.


Changes affecting users and requiring new User Extensions

In order to obtain the changes described in this section the Enterprise Vault 7.0 SP1 User Extensions must be installed.

Change to RPC over HTTP behavior [Ref 604077-1, 701035-1, E864192]

Previously, if the Enterprise Vault client was configured to use RPC over HTTP, the client always connected to the Front End server. This behavior has been changed so that, if the Enterprise Vault Web server is available a direct connection is made, instead of connecting to the Front End server.

Improvement to Offline Vault [Ref 604077-2, 701035-2, E864192]

The behavior of Offline Vault has been modified so that the performance impact on Outlook sessions is less than before.

Enterprise Vault 6.0 client downloading large documents from 7.0 server [Ref 701029 E860133]

When using an Enterprise Vault 6.0 client to access the Outlook integrated search (searcho2k.asp) on an Enterprise Vault 7.0 server, it was not possible to download large documents (tens of megabytes).

Pre-emptive offline archiving would sometimes archive the same items twice [Ref 604081 701034 E864086]

When an offline user starts Microsoft Outlook, the Enterprise Vault client scans the user's mailbox folders for items that are due to be archived soon and pre-emptively copies them to the offline archive. If an item had a non-ASCII character in its address or Subject fields then the client would sometimes attempt to archive it twice. This has been fixed.


Changes affecting users and not requiring new User Extensions

The changes described in this section are obtained as a result of upgrading Enterprise Vault server software and so do not require the updated Enterprise Vault 7.0 SP1 User Extensions.

Mailbox owners in groups unable to write to shared archive [Ref 604061, 701004, E821038]

In some circumstances, during an archiving run (performed by the Run Now command or scheduled), a user in an Active Directory group with full rights to a shared archive could be denied write access to the archive. An error with event id 2777 was logged to the Enterprise Vault event log.

Changes to settings in WebApp.ini file [Ref 701047, 604090, 603225, E898921, E898923]

The Settings button in Archive Explorer and customized shortcuts enables users to select the application to use when viewing archived items; Outlook or a Web browser. When the user clicks OK in this dialog, the values in the dialog are saved in a cookie. If required, the administrator can set the default application for viewing items (Outlook or Web browser), using the ViewMessage_Format setting in the WebApp.ini file.

In previous releases, if the ViewMessage_Format setting existed in the WebApp.ini file, and the cookie was not available, the ViewMessage_Format setting was not effective, resulting in some right-click options in Archive Explorer becoming unavailable. To enable the right-click options, users had to recreate the cookie by opening the Settings dialog, selecting the required value and clicking OK.

In this release, the ViewMessage_Format setting in the WebApp.ini file is effective, even if the cookie is no longer available.

If you do not want users to change values in the Settings dialog, you can specify the required settings using the ViewMessage_Format setting in the WebApp.ini file, and hide the Settings button by including the following entry in WebApp.ini:

ArchiveExplorerSettings = 0
(This setting existed in earlier releases of Enterprise Vault, but was then removed. It has now been reinstated).

Complete removal of Offline Vault [Ref 701039, E773570]

There is a new registry value that enables you to remove Offline Vault completely from a user's computer.


Changes to OWA support

OWA Extensions support for Exchange Server 2003 updates [Ref 701042,CAP1161,604086,603223,E895179]

This release provides updated Enterprise Vault OWA Extensions to support Microsoft updates to Exchange Server 2003 SP2 up to KB 924334 v2 (6.5.7651.60).

Earlier control file versions are also supported. For a list of the OWA control file versions supported by Enterprise Vault, see the Compatibility Charts  http://support.veritas.com/docs/276547 .

Inability to view items when using Archive Explorer from OWA on some non-English systems [Ref 604103, 701074, E840024]

OWA security issue fixed [Ref 604097, 701068, E917512, E917516]

An OWA cross-site scripting vulnerability on Windows 2003 has been fixed.


Enhancements to Indexing

Indexing service logs archived items that are not indexed [Ref 604082, 701048]

The Indexing service previously logged errors for items that were archived but not indexed to the Event Log. It can now log details about these errors to the IndexMissing.log file in the index volume folder.

Checksum validation for index files [Ref 604080, 701033]

The Indexing service now validates archive index files before opening the index. The validation is done using a checksum, which is held in a Checksum.dat file in each index volume folder.

Validation of Index Sequence Numbers [Ref 604096,701037]

Each time an index is loaded, for example to search or update, indexing now compares the highest Index Sequence Number in the vault store database with the highest Item Sequence Number in the index volume.
If the value in the vault store database is greater than the value in the index volume, then indexing is prompted to start indexing items. Users attempting to search an index that is being updated will see a warning that search results may be incomplete.
If the value in the index volume is greater than the value in the vault store, then the index volume is marked as failed, in order to avoid inconsistent or invalid search results. An error is also written to the event log. This situation may arise if you restore an old vault store database from backup.

Improvements to the way that the Indexing service handles items that it previously failed to index [Ref 604099, 701069]


Enhancements to IndexCheck utility

Generating and validating index file checksums [Ref 701041, 604085]

The Indexing service can now generate a checksum for an index volume, and use the checksum to perform index validation before opening the index volume.

Logging items missing from indexes [Ref 701049, 604087]

The Indexing service can now log details about archived items that were not indexed, and archived items that were only partially indexed because some content was missing.

Verifying the number of indexed items in index volumes [Ref 701019, 604070, 603207, E791582]

Options have been added to the IndexCheck tool to compare the number of items in an archive with the number of items indexed for that archive.


Changes to Exchange Server archiving

Access violation from Exchange Mailbox archiving task [Ref 701011 E852746 E849522 E838623 E808775 E827908]

It was possible for an access violation to be logged by the Exchange Mailbox archiving task. This could occur when the task was actively archiving or synchronizing.

Corrupt items in Journal Mailbox not handled correctly [701072, E917361]

In Enterprise Vault 7.0, Exchange Journal Archiving did not handle corrupt messages in the Journal Mailbox correctly. If this issue occurred, an error with event id 3007 was logged to the Enterprise Vault event log.
In this release, the item is moved to the Failed to copy folder, which is under the Exchange Journaling Task folder in the Administration Console.

Changed behavior when a distribution list fails to expand during archiving of journal mailbox items [Ref 603218, 604076, 701022, E850230, E867489, E864736]


Changes to Domino journal archiving

Domino Web Access mail not indexed [Ref 701001-1, E857850]

The bodies of messages sent from Domino Web Access were not indexed when the messages were archived. Thus, the messages could not be found by searching for message content.

Memory leak fixed in Domino Journaling [Ref 701001-2, E863965]

A memory leak that could eventually cause the Domino Journaling task to fail.


Changes to PST migration

'Adjust Exchange quotas' option failed to work during PST migration [Ref 604035, 701009, E803748]

Mailbox shortcuts not updated during PST export/import  [Ref 604075, 701021, E834200, E864190]

Client-driven PST migration could fail [604071, 701007, E833511]

In previous releases, when client-driven PST migration was enabled, it was possible for Enterprise Vault to migrate the same chunk of a PST file twice. When this happened, the migration failed with event log error 8567.


Changes for Centera

Processing of corrupted attachments on Centera [Ref 604072, 701008, E856324]

Using Enterprise Vault 5.0, it was possible for a message with a corrupt attachment to be archived on Centera. It was not possible to restore the message.

Cannot access 'EMC Centera tab' in Retention Category properties [Ref 604105, 701075 E918077]

If you specified a pool entry authorization (PEA) file for access to Centera when a replica is present, the Class Name list on the EMC Centera tab in Retention Category Properties was always empty.

Improved error checking for Centera collections [Ref 604042, 604089, 701077, E898968]


Other changes

Archiving of large HTML or text files [Ref 604104, 701064, E925288]

In previous releases, Enterprise Vault handled the archiving of very large HTML or text files incorrectly. These files could be attachments to a message or files being archived from a file server. Out of memory warnings were written to the Event log.

Reported original size of files was incorrect [Ref 701101, E967444]

Files archived using FSA or SMTP Archiving, posted documents in Outlook, and Domino Server messages were reported as larger than they were.


Documentation changes

Japanese manuals and help files [Ref 701090]

The Enterprise Vault administration documentation was only available for download in Japanese for Enterprise Vault 7.0. This documentation is now included in Enterprise Vault 7.0 Service Pack 1 media.