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

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

For instructions on installing or upgrading to Enterprise Vault 6.0 SP4, 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


This is an overview of the changes contained in Symantec Enterprise Vault 6.0 SP4.  Full details can be found in the file updates.htm in the installation media.

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, see the updates.htm file.

Resetting restore-pending and delete-pending items [604009-1, CAP388, E638080]


Changes affecting users and requiring new User Extensions

In order to obtain the changes described in this section the Enterprise Vault 6.0 SP4 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.

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 6.0 SP4 User Extensions.

Users should delete their temporary Internet files [Ref 604091-2, 604095-2, 604109-2, 603205-2]

After this Service Pack has been installed, we recommend that users of Archive Explorer or Enterprise Vault browser search delete their Internet Explorer temporary Internet files, in particular those for the EnterpriseVault IIS virtual directory. This virtual directory is configured by default to cache its Web page content files in Internet Explorer for up to 30 days. If you do not delete your temporary Internet files, you will not benefit from the changes for Internet Explorer until these cached files expire.

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.

Directory service out of memory error [Ref 604043, CAP0625, E582284]

In some circumstances it was possible for a user's search of a folder archive to fail, and for the Directory service on the Enterprise Vault server to return an out of memory error. An event with id 8390 was logged to the Enterprise Vault event log.

Delegation and Associated External Accounts [Ref 604047, E831988]

Folder synchronization did not synchronize Associated External Accounts when a user had been granted delegate access to a folder in another user's mailbox.

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

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

Archive Explorer problem after installing Microsoft security update KB924191 [Ref 603205-1, 604053, CAP961, E832762]

After users installed Microsoft security update KB924191, they were unable to view items in Enterprise Vault Archive Explorer when Archive Explorer was running in Outlook. The problem did not occur when Archive Explorer was running in Internet Explorer.

Retention categories applied incorrectly when deleting items [604028, CAP626, E779897]

In previous releases, a retention category could in some circumstances be applied incorrectly when you tried to delete an archived item.

Search may not find a word [603221, 604084, 604124, CAP042, E896791]

In previous releases it was possible to search for a word in an archived message, but to get no results even though the word was present. This issue occurred when the word was written partly in one font and partly in another.

Servers did not respond to client requests [604009-2, CAP474, E637914]

In earlier versions of Enterprise Vault 6.0, when the Directory service on the server identified by the Vault Site alias was unavailable, all other servers in the Vault Site stopped responding to archiving requests from Enterprise Vault HTTP clients, and to search requests from all Enterprise Vault clients.


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 .

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

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

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


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.

Memory leak when re-indexing large indexes [Ref 604055, E780858]

A memory leak that could occur when creating or rebuilding large indexes (millions of items) has been fixed. The leak could cause the StorageCrawler process to fail with an out-of-memory error.


Changes to Exchange Server archiving

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

External filters could count retried messages as new messages [Ref 604025, CAP039, 603194]

With Envelope Journaling enabled, all messages given message type of Exchange [Ref 604024, E784638]

Fix for problem with archiving complex items in the journal mailbox [Ref 604052, E764472]

Enterprise Vault can now archive journal mailbox items that it previously considered to be too complex to archive. Examples of such items are those with a very large number of attachments and multiple levels of nested messages.


Changes to Domino journal archiving

Could not archive messages containing stored forms [Ref 604036, 604064, E803359]


Changes to File System Archiving

Change to default for new FSA archiving policy [Ref 604060, E854305]

When you create a new FSA archiving policy and choose to leave placeholder shortcuts, Delete archived file when placeholder is deleted is no longer selected by default.


Changes to PST migration

Excluding specific network shares from PST migration [Ref 604054-1]

It is now possible to exclude specific network shares when searching for PST files.

PST Locator task: now skips inaccessible shares on NetApp Filer [Ref 604054-2, CAP819]

PST Locator task: PSTs in multiple volumes on NetApp Filer [Ref 603186, 604020, 604088, CAP531, E765870]

In earlier releases, when a NetApp Filer had more than one volume and PSTs were located on a volume other than the root volume, the PST Locator task failed to find all PSTs. The Locator task now finds PSTs on other volumes.

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

Migrating empty PST folders [Ref 604022, 604031]

When you migrate the contents of PST files, empty folders in the PST files are not migrated. There are now two registry values you can use to make Enterprise Vault recreate empty PST folders in the mailbox.

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.

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

Addressing error with multiple Centera IP address ranges [Ref 604046, E619573.htm]

Improved performance when retrieving or deleting items stored on Centera [Ref 604051, E814883]

Improvements to StorageFileWatch [Ref 604017, E768316, E768803]


Other changes

Export Archive wizard search failed to resolve partial entries [Ref 604039, CAP840, E819933, E830046]

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.


Documentation changes

Updates to user manuals

The Enterprise Vault user manuals are unchanged from Service Pack 3, except for the Installing and Configuring manual, in which the chapter Upgrading to Enterprise Vault has been updated.

The manuals are located in the Documentation folder on the SP4 distribution media.