VERITAS Enterprise Vault (tm) 6.0 Service Pack 1 revision 6.0.0.7637

Document ID: 279962
http://support.veritas.com/docs/279962

E-Mail this document to a colleague

Details:

VERITAS Enterprise Vault (tm) 6.0 Service Pack 1

This document describes the changes introduced by Enterprise Vault 6.0 Service Pack 1 (SP1).

The download is comprised of the following:

Enterprise Vault for Microsoft Exchange 6.0 SP1
Enterprise Vault for File System Archiving 6.0 SP1
Enterprise Vault for Microsoft Sharepoint 6.0 SP1
Enterprise Vault for Lotus Domino 6.0 SP1
Enterprise Vault for SMTP Archiving 6.0 SP1

This document describes outstanding Enterprise Vault issues and the changes introduced by Enterprise Vault 6.0 Service Pack 1.

Symantec recommends all customers sign up for our Email Notification Service by clicking "Subscribe" in the top right corner of the Support site ( http://support.veritas.com ) and selecting the products you are running. To receive monthly updates on new or republished TechNotes select "Digest" updates. To receive notifications of critical technical issues select "Software Alerts".

Note that the following software is not yet certified for use with Enterprise Vault but is currently undergoing certification:

Microsoft Exchange Server 2003 SP2
Microsoft Outlook 2003 SP2
Microsoft SharePoint 2003 SP2
Microsoft SQL Server 2005
VERITAS NetBackup Server 6.0

Refer to TechNote 276547: http://support.veritas.com/docs/276547 for the full Enterprise Vault compatibility listings

This file contains the following topics:

Enterprise Vault for Domino Journaling
Prerequisite software
Installation
New features
Administration Console
PST migration
Client changes
File System Archiving
SharePoint
SMTP mail archiving
Lotus Domino
Other changes

Enterprise Vault for Domino Journaling

Enterprise Vault for Domino Journaling has been made available in Enterprise Vault 6.0 SP1. Due to an issue with font sizes in some environments, this functionality is disabled by default in Enterprise Vault 6.0 SP1. This issue has now been resolved. Customers wishing to deploy Lotus Domino journaling must apply the hotfix which can be downloaded from: http://support.veritas.com/docs/281247

Prerequisite software

Outlook 2003 required on Enterprise Vault servers [Ref 601131]

Outlook 2003 is required on every Enterprise Vault server if you archive from any of the following:

Exchange Server
File servers
SharePoint 2003
SharePoint 2001

The installation does not check for Outlook 2003, but if it is not installed, no task that archives from any of these targets will start.

Outlook 2003 is not a requirement if you perform Domino journal archiving only.

Installation

ISP/hosting support

Customers who use host Enterprise Vault 6.0 email archiving solutions should see document 279894: http://support.veritas.com/docs/279894 for updated information on our support of your deployment. Additional documentation and guidance for ISP/hosting customers will be available in a future Service Pack.

Server installation

When you upgrade to Enterprise Vault 6.0 SP1, it is mandatory that you upgrade all Enterprise Vault servers, including Outlook Web Access (OWA) front-end and back-end servers. In each case, load the Enterprise Vault CD-ROM in your CD-ROM drive, double-click SETUP.EXE to start the installation, and then choose the required components. For further information, see the "Upgrading to Enterprise Vault 6.0 SP1" chapter in Installing and Configuring: http://support.veritas.com/docs/279957

Configuration Program must run after installing Enterprise Vault 6.0 SP1 [Ref 601321]

After installing Enterprise Vault 6.0 SP1 you must run the Configuration Program, which ensures that a Directory Service is present on every Enterprise Vault server.

For details of the upgraded procedure, see the "Upgrading to Enterprise Vault 6.0 SP1" chapter in Installing and Configuring: http://support.veritas.com/docs/279957

Changes to DCOM security permissions [Ref 601472/601541]

In Microsoft Windows Server 2003, the Everyone group does not contain the security identifier (SID) "Anonymous." For more information, see the following Microsoft articles:

Microsoft Support article 278259, Everyone Group Does Not Include Anonymous Security Identifier: http://support.microsoft.com/default.aspx?scid=kb;en-us;278259
Microsoft TechCenter article, Changes to Functionality in Microsoft Windows Server 2003 Service Pack 1: DCOM Security Enhancements: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/BookofSP1/4c9a2873-2010-4dbb-b9dd-6a7d1e275f0f.mspx

This hardening of security caused various Enterprise Vault issues, so in Enterprise Vault 6.0 SP1 the Enterprise Vault Admin Service has been changed so that it automatically grants required permissions to various Enterprise Vault components, as described below.

If the relaxation in security does not meet with your corporate security requirements, it is possible to configure the Admin Service so that required permissions are not automatically granted.

The Enterprise Vault Admin Service now automatically grants Remote Activation permission to the Anonymous Logon security group for the following as part of its normal DCOM permissions configuration:

AgentClientBrokerServer
DirectoryService
IndexBroker
StorageOnlineOpns

Additionally, the Admin Service grants the Anonymous Logon security group Remote Access permission for COM Server applications.

If the Admin Service is not allowed to change the default security, the following problems may be seen:

If the Directory Service is on a different server from IIS, and both servers are running Windows 2003 SP1, it is not possible to perform manual archives using the Self-Installing User Extensions.
If the Enterprise Vault Indexing Service is running on a server running Windows 2003 SP1 and IIS is on a different server, it is not possible to perform searches using the Web Access application or Outlook Integrated Search.
Performing a search of SharePoint archives from a client computer results in the following error:

Your search encountered an error. If the problem persists, contact the site administrator.

Error details:

There is no archive selected. [0x80041c6b]

Registry settings

The registry values in this section are created as part of the upgrade to Enterprise Vault 6.0 SP1 and permissions are granted to the Anonymous Logon security group as described above.

When the Admin Service changes the default for Anonymous Logon for the first time, it also does the following:

Places a warning in the Enterprise Vault event log.
Prevents further such warnings being logged by creating a DWORD registry entry called AnonymousPermissionsChangeWarning under the following registry key, with a value of 1:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\AdminService

The Admin Service checks the default Anonymous Logon permissions each time it starts, modifying them if necessary. If your corporate security policy does not permit this automatic softening of security permissions, do the following:

1. Create a DWORD registry entry called DoNotChangeAnonymousPermissions under the following registry key and give it a value of 1:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\AdminService

2. Remove the existing Anonymous Logon permissions as described in the next section.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Removing Anonymous Logon permissions

If the Anonymous Logon permissions have already been set and you want to remove them, do the following:

1. Remove the remote Access Permission for COM Server applications from the Anonymous Logon security group:

a. Click Start, then Run, then enter dcomcnfg.exe and click OK.

b. In Component Services, expand Component Services and then expand Computers.

c. Right-click My Computer and, on the shortcut menu, click Properties.

d. In My Computer Properties, click the COM Security tab.

e. Under Access Permissions, click Edit Limits.

f. Under Launch and Activation Permissions, click Edit Limits.

g. Under Group or user name, click ANONYMOUS LOGON and then click Remove.

h. Click OK.

2. Remove the remote Launch and Activation permission for COM Server applications from the Anonymous Logon security group:

a. On the Com Security tab, under Launch and Activation Permissions, click Edit Limits.

b. Under Group or user name, click ANONYMOUS LOGON and then click Remove.

c. Click OK.

d. Click OK to close My Computer Properties.

3. Remove the Local Activation and Remote Activation permissions for DirectoryService, IndexBroker, StorageOnlineOpns, and AgentClientBrokerServer:

a. In the Component Services window, expand My Computer.

b. Expand DCOM Config.

c. Right-click DirectoryService and, on the shortcut menu, click Properties.

d. Click the Security tab.

e. Under Launch Permissions, click Edit.

f. Under Group or user name, click ANONYMOUS LOGON and then click Remove.

g. Click OK.

h. Repeat from Step 3c to remove the Anonymous Logon permissions from each of IndexBroker, StorageOnlineOpns, and AgentClientBrokerServer.

No support for Windows NT4 domains

Enterprise Vault is not supported on Windows NT4 domains. Note that it is also not possible to install Enterprise Vault on Windows 2000 or Windows 2003 servers that are in Windows NT4 domains.

Upgrading a failed-over server [Ref 32628]

It is possible for you to upgrade, from Enterprise Vault 5.0 to Enterprise Vault 6.0 SP1, a server that is hosting services for a failed server. In order to reinstate the failed server you must do the following:

Repair the failed server and upgrade it to Enterprise Vault 6.0 SP1.
Run Update Service Locations as documented in the "Failover in a Building Blocks configuration" chapter in the Administrator's Guide: http://support.veritas.com/docs/279959
Run Update Service Locations again. The first run of Update Service Locations does not completely reset the configuration; the second run does complete the reconfiguration.

Changes to the Enterprise Vault OWA Extensions setup scripts

The scripts for installing the Enterprise Vault OWA Extensions now set the Basic Authentication domain correctly by matching it with the NETBIOS domain configured on the Exchange virtual directory. Previously, the scripts would set the domain to "\", which could cause authentication issues. [Ref 601060]
The Enterprise Vault OWA Extensions setup scripts now run without error on non-English systems. [Ref 601094]
Uninstalling the Enterprise Vault OWA Extensions now removes all components, including the virtual directories and form registrations that were created as part of the installation process. [Ref 601113]

Client installation

In order to minimize the possibility of corruption of displayed text, and to achieve the best performance, you are recommended to upgrade all clients to Outlook 2003 and install the Enterprise Vault 6.0 SP1 User Extensions. This is particularly important especially in environments in which messages with a variety of characters sets are received. See Unicode storage for more details.

New features

Translated versions of Enterprise Vault [Ref 601119]

The User Extensions are now available in Danish, English, French, German, Italian, Japanese, Spanish (Castillian), and Swedish.

We are currently evaluating and scheduling our language support for SharePoint as the platform becomes accepted in countries around the world. Currently we support only English for display and search facilities and we are planning that future service packs will add local language support. Please contact your account representative if you are interested in local language support for SharePoint.

Internationalized English version of Enterprise Vault 6.0 SP1

Enterprise Vault 6.0 SP1 English version has passed Symantec's internal World Wide Certification Testing (WWCT) for the Simplified Chinese, Traditional Chinese, Japanese, and Korean Windows platforms.

The tables below summarizes the testing environments used. For more information, refer to the Symantec Support Web site: http://support.symantec.com

Software	Japanese	Simplified Chinese	Traditional Chinese	Korean
Exchange Server 2003	Microsoft Windows Server 2003 Enterprise Edition with SP1, Japanese	Microsoft Windows Server 2003 Enterprise Edition with SP1, Simplified Chinese	Microsoft Windows Server 2003 Enterprise Edition with SP1, Traditional Chinese	Microsoft Windows Server 2003 Enterprise Edition with SP1, Korean
	Microsoft Exchange Server 2003 Enterprise Edition with SP1, Japanese	Microsoft Exchange Server 2003 Enterprise Edition with SP1, Simplified Chinese	Microsoft Exchange Server 2003 Enterprise Edition with SP1, Traditional Chinese	Microsoft Exchange Server 2003 Enterprise Edition with SP1, Korean
Exchange Server 2000	Microsoft Windows 2000 Server Advanced Edition with SP4, Japanese
	Microsoft Exchange Server 2000 Enterprise Edition with SP3, Japanese
Enterprise Vault 6.0 SP1 Server	Microsoft Windows Server 2003 Enterprise Edition with SP1, English	Microsoft Windows Server 2003 Enterprise Edition with SP1, English	Microsoft Windows Server 2003 Enterprise Edition with SP1, English	Microsoft Windows Server 2003 Enterprise Edition with SP1, English
	Microsoft SQL Server 2000 with SP4, Japanese	Microsoft SQL Server 2000 with SP3a, Simplified Chinese	Microsoft SQL Server 2000 with SP3a, Traditional Chinese	Microsoft SQL Server 2000 with SP3a, Korean
	Microsoft Outlook 2003 with SP1, Japanese	Microsoft Outlook 2003 with SP1, Simplified Chinese	Microsoft Outlook 2003 with SP1, Traditional Chinese	Microsoft Outlook 2003 with SP1, Korean
Enterprise Vault User Extensions	Microsoft Windows XP with SP2, Japanese	Microsoft Windows XP with SP2, Simplified Chinese	Microsoft Windows XP with SP2	Microsoft Windows XP with SP2
	Microsoft Office Outlook 2003 with SP1, Japanese	Microsoft Office Outlook 2003 with SP1, Simplified Chinese	Traditional Chinese Microsoft Office Outlook 2003 with SP1, Traditional Chinese	Korean Microsoft Office Outlook 2003 with SP1, Korean
	Enterprise Vault User Extensions 6.0 SP1, Japanese	Enterprise Vault 6.0 SP1 User Extensions, English	Enterprise Vault 6.0 SP1 User Extensions, English	Enterprise Vault 6.0 SP1 User Extensions, English

Lotus Domino Journaling [Ref 601013]

Enterprise Vault 6.0 SP1 adds support for archiving from Lotus Domino Journaling databases. Domino Journaling databases can be added as archiving targets within the Administration Console.

The Domino Server versions supported are 6.0, 6.5 and 7.0. The Domino Server can be running any language version of Windows. Currently the Enterprise Vault server must be running English Windows.

The Enterprise Vault server that archives from the Domino Journaling database must have Lotus Notes Client 6.5.4.x installed.

See the Domino chapters in Introduction and Planning: http://support.veritas.com/docs/279956 and Installing and Configuring: http://support.veritas.com/docs/279957 for details of installing archiving for Domino Journaling archiving.

Increased maximum size of archives [Ref 601186]

The maximum size of archives has been increased from 2 gigabytes to 9223372 terabytes. Depending on the number of items in an archive, this maximum size may not be achievable.

Previously, if an archive reached the old size limit, the error produced was similar to the following:

Event Type: Error

Event Source: Enterprise Vault

Event Category: File Archive Server

Event ID: 13360

Date: 26/09/2005

Time: 12:49:34 PM

User: N/A

Computer: DEMO

Description:

An error was detected while accessing the Vault Database 'EVvs1'

(Internal reference: ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand)

[lines {1166,1168,1171,1213,1240}] built Jul 4 14:48:26 2005):

Description:

Arithmetic overflow error converting expression to data type int.

Migration support extended to large files [Ref 601067]

Migration support was previously introduced for Enterprise Vault collection files. The migration feature has now been extended to include large files (.DVF files) using any of the following:

Enterprise Vault Migrator
VERITAS NetBackup Server Migrator
IBM TotalStorage DR550 Migrator

Increased capacity for archive indexes - "index volumes"

Enterprise Vault 6.0 SP1 introduces "index volumes" to increase the maximum number of items that can be stored in an archive.

Before Enterprise Vault 6.0 SP1, each archive's index was a single AltaVista index. The number of items that could be stored in the AltaVista index limited the number of items in the archive. The number varied, but was typically between 1.5 and 2.5 million items.

When an index, and hence an archive, became full, Enterprise Vault reacted in one of two ways:

For Journal and Shared archives, Enterprise Vault created a new "rollover archive" to store further items.
For all other archive types, Enterprise Vault rejected all attempts to add more items to the archive.

In Enterprise Vault 6.0 SP1, when an index volume becomes full, a new index volume is automatically created. In the Administration Console the Advanced tab of an archive's properties shows "Number of index volumes".

The new index volume does not have the same index root path as the previous index volume. The new location for the new index is a random selection from the Indexing Service's open index root paths.

Some users may see changes in the Outlook integrated search application, the Browser Search, and Archive Explorer.

If an archive has more than one index volume, the initial search is performed on the current index volume. To view search results from earlier index volumes, the user must choose a date range from a list. The date ranges correspond to the archived date range of items in the index volumes.

The initial search is performed against the current index volume, which is the one containing the most recently-archived items.

Most users will not see any change because rollover is unlikely to occur for normal mailbox archives. The archives that are likely to rollover are FSA archives, Journal archives, and Public Folder archives. When these archives roll over, users with access to them will be able to select a date range to search.

Rollover archives created before Enterprise Vault 6.0 SP1 are not merged back into the master archive. Archiving continues to the current rollover archive and that archive's index will expand to multiple index volumes as necessary. Rollover archives will not be created after Enterprise Vault 6.0 SP1.

Unicode storage

In earlier versions of Enterprise Vault, archived items were stored using ANSI streams to hold some header information, such as message subject. Corruption could occur when the header information contained characters that could not be expressed in a single codepage, or when a codepage was not explicitly identified.

In Enterprise Vault 6.0 SP1, Unicode items are stored in Unicode savesets, and ANSI items are stored in ANSI savesets, thus avoiding possible corruption. All items archived from Exchange Server are Unicode, so are stored in Unicode savesets.

Items stored as ANSI are returned to clients as ANSI, using the codepage stored in the saveset file, even if Unicode is specified. This improves performance and removes the need for conversion.

Items stored as Unicode can be returned as either Unicode or as ANSI, as required.

The Enterprise Vault 6.0 SP1 User Extensions automatically detect the version of Outlook installed on the user's computer and request a suitable message format from the server.

User Extensions from earlier versions of Enterprise Vault, and clients without the Enterprise Vault User Extensions, cannot detect the Outlook version and so cannot specify the format needed. Because of this there are two new settings you can add to the WebApp.ini file to specify the default delivery format, as follows:

DefaultFormatType

Specifies whether to provide Unicode messages as Unicode or ANSI. The possible values are "Unicode" and "ANSI".

If DefaultFormatType is not used, messages are sent to the client using ANSI.

If all clients are running Outlook 2003 or later, set DefaultFormatType to "Unicode". This means that clients are always given Unicode when it is available. This prevents unnecessary conversions and possible character-viewing problems.

DefaultFormatCodepage

Specifies the codepage to use when DefaultFormatType is "ANSI".

If DefaultFormatType is "ANSI" but DefaultFormatCodepage is not set then messages are sent to the client in the codepage in which they are stored.

See the Microsoft MSDN Web site for a listing of codepage values: http://msdn.microsoft.com/library/default.asp?url=/workshop/author/dhtml/reference/charsets/charset4.asp

If these WebApp.ini settings are not used, and the client does not specify the information, then the format type will be ANSI and the codepage will be the codepage in the saveset. The following table summarizes the rules use when choosing the format to deliver to clients:

File type delivered to client	Rules for choosing Unicode or ANSI
Enterprise Vault saveset (.DVS file)	Always deliver savesets as ANSI. Unicode savesets are delivered in the format specified by the client, if any. If no format is specified the setting of DefaultFormatType is used.
Outlook (.MSG file)	Deliver .MSG in the format specified by the client, if any. ANSI messages are converted to Unicode if necessary. If no format is specified the setting of DefaultFormatType is used.

Note that additional processing is required when viewing new Unicode Savesets on ANSI versions of Outlook (Outlook XP, Outlook 2000 and earlier). Since these versions of Outlook cannot open Unicode items, the items must be converted to ANSI on the server before being sent to the client. This additional processing is not required for Outlook 2003 and later clients.

Failures when restoring PST files [Ref 601390]

When restoring items found by a search to a PST file, the restoration failed unless the destination folder already existed.

This has been fixed. If the destination folder does not already exist, it is created.

The option to restore to a PST file is not available unless RestoreToPSTOption is set in WebApp.ini. See the "Customizing the Web Access application" chapter in the Administrator's Guide for information about RestoreToPSTOption.

Change to mailbox synchronization behavior [Ref 601387]

When using quota-based archiving, mailboxes that were within quota were not processed and the mailbox permissions were not synchronized to their vaults. This has changed so that mailbox permissions are now always synchronized, regardless of whether the mailbox is within quota.

Incorrect icons for "Out of Office" items [Ref 601245]

Archive Explorer did not show the correct icon for "Out of Office" items.

This has been fixed. The message class IPM.NOTE.RULES.OOFTEMPLATE.MICROSOFT has been associated with the icon for "Out of Office" items.

Occasional failure to process a mailbox [Ref 601142]

If an Archiving Task was configured to exclude deleted items then it could occasionally fail to process a mailbox, logging the following error:

Event Type: Error

Event Source: Enterprise Vault

Event Category: Archive Task

Event ID: 2236

Date: 02/06/2005

Time: 5:33:19 AM

User: N/A

Computer: DEMO1

Description:

Could not scan user mailbox

/o=First Organization/ou=First Administrative Group /cn=Recipients/cn=SmithJ,

unable to get the entry id of the Deleted Items folder

Reason: <0x8004010f>

Since the occurrence was random, the mailbox would probably be processed correctly the next time the Archiving Task ran.

This has been fixed.

Auto-enabling public folders [Ref 601100]

The following changes have been made to public folder auto-enabling:

When a new public folder is auto-enabled, archiving happens immediately. Previously, archiving did not take place until the next run of the Exchange Public Folder task.
It was not possible to add a public folder auto-enabler to the root public folder. This has been fixed.
The performance of the public folder auto-enabler has been significantly improved.

Improved stability of Exchange Server archiving tasks [Ref 601035]

Exchange Server archiving and journaling tasks now shut down and restart more reliably.

New Enterprise Vault Management Pack for Microsoft Operations Manager (MOM) [Ref: 601347]

Enterprise Vault 6.0 SP1 comes with a new MOM management pack with which you can monitor Enterprise Vault operations and performance. See the Administrator's Guide: http://support.veritas.com/docs/279959 for instructions on how to install and configure this pack.

Option to remove embedded images when archiving messages [Ref: 601168/1]

If you have chosen to make Enterprise Vault generate shortcuts that contain all the original message body, but you want it to remove embedded images from the messages that it is archiving, you can create a DWORD value called RemoveEmbeddedAttachments under the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Agents

Give RemoveEmbeddedAttachments a value of 1 to remove embedded images, or 0 to retain the images. The default is 0 (embedded images are not removed).

Message direction now set for all types of messages [Ref: 601421]

In previous versions of Enterprise Vault, only Exchange Server messages were marked with their direction (internal, external inbound, or external outbound). Now the message direction is set for all types of messages and can be accessed using the Indexing API and Journal Filtering.

Additional languages available when migrating PST files [Ref 601476]

The languages from which you can choose when migrating PST files have been extended. As well as Western European, Arabic, Hebrew, and Japanese, you can now choose from these languages:

Baltic
Central European
Cyrillic
Greek
Korean
Simplified Chinese
Thai
Traditional Chinese
Turkish
Vietnamese

Administration Console

For changes to the Administration Console please refer to TechNote 279965: http://support.veritas.com/docs/279965

PST migration

For changes to PST Migration please refer to TechNote 279966: http://support.veritas.com/docs/279966

Client changes

For changes to the Client please refer to TechNote 279967: http://support.veritas.com/docs/279967

File System Archiving

For changes to File System Archiving please refer to TechNote 279968: http://support.veritas.com/docs/279968

SharePoint Archiving

For changes to SharePoint Archiving please refer to TechNote 279969: http://support.veritas.com/docs/279969

SMTP Mail Archiving

For changes to SMTP Mail Archiving please refer to TechNote 279974: http://support.veritas.com/docs/279974

Lotus Domino

For details of Lotus Domino Archiving please refer to TechNote 279970: http://support.veritas.com/docs/279970

Other changes

Updated Centera SDK [Ref 601205]

Enterprise Vault 6.0 SP1 includes Centera SDK version 3.0 Patch 1 (3.0.388.0), released by EMC on July 12, 2005.

Unable to access the properties of File Server archiving target after upgrading to Windows Server 2003 SP1 [Ref: 601446]

After upgrading an Enterprise Vault server to Windows Server 2003 SP1, it may not have been possible to view the properties of a file server in the Vault Administration Console, and the event log may have contained messages with event id 40974 ("Unable to access the Directory Service").

This problem has now been fixed.

Policy Manager notification messages when enabling or disabling mailboxes [Ref 601487]

If you used Policy Manager to enable a mailbox that had already been enabled for archiving, or to disable one that had already been disabled, then Policy Manager would still send a Welcome or Goodbye message to the mailbox.

This problem has now been fixed.

Windows resource problems when deleting a large number of placeholder shortcuts [Ref 601489]

Deleting more than 10,000 placeholder shortcuts at a time could impact system performance and lead to warnings about insufficient system resources.

This problem has now been fixed.

Archiving tasks stopping unexpectedly [Ref 601189]

Archiving, Journaling, and Public Folder tasks could sometimes stop unexpectedly, with no information in the event log other than the stop event itself. For example:

Event Type: Information

Event Source: Enterprise Vault

Event Category: Archive Task

Event ID: 3296

Date: 01/08/2005

Time: 19:36:03

User: N/A

Computer: DEMO2

Description:

The Archiving Task 'Mailbox Archiving Task for DEMO1' against DEMO1 has stopped

This has been fixed.

"Task" and "Service" terminology in event log messages [Ref 601155]

Some event log messages were incorrectly referring to tasks as "services".

This has been fixed.

Reduction in TCP port usage [Ref 601112]

The number of TCP ports required for connections to Active Directory has been significantly reduced.

Distribution lists in custom filters [Ref 601198]

When checking distribution lists, custom rules were matching users' display names rather than mail addresses. In some cases, this could cause a match to fail when it should not have done.

This has been fixed.

Excessive StorageFileWatch errors when trying to archive to unavailable storage devices [Ref 601210]

The StorageFileWatch component no longer logs an excessive number of error messages in cases where you are trying to archive to an unavailable NetApp device or remote network share, and you have chosen to remove safety copies of archived items after backup.

Enterprise Vault services now try to re-establish connection to SQL database when it is lost temporarily [Ref 601277]

When the connection to the SQL database is lost, the Enterprise Vault services now try to re-establish it at intervals of up to 30 seconds until they are shut down. Previously, these services did not detect when the database was available again and so would continue to log errors.

Message identifier not being indexed [Ref 601355]

Enterprise Vault now populates the "iden" indexing attribute on archived saveset files correctly. This attribute is part of the indexable item data that is stored within the archived saveset file.

ExchangePermissions settings in Enterprise Vault Policy Manager can now contain non-Western-European characters [Ref 601362]

When setting the permissions for a folder with the ExchangePermissions option in Policy Manager, you can now include non-Western-European characters in the value.

Wrongly-categorized Journal items following archive rollover [Ref: 601396]

If you used Selective Journaling with different Journal archives and vault stores set up for each of the different filter rules, then, when archive rollover occurred, the Journal items were incorrectly categorized. All the Journal items in a particular pass were categorized according to the filter category of the first item to be archived.

This problem has now been fixed.

Prevention of duplicate mailbox entries [Ref 601391]

When it performs mailbox synchronization, Enterprise Vault now checks for duplicate mailbox entries and prevents them from proliferating.

Enhancement to Custom Archiving Filters feature to remove message attachments [Ref 601194]

You can now include rules in your ruleset files that instruct Enterprise Vault to delete message attachments of a certain type or size. For example, you can use this feature to delete all MP3 message attachments, or to delete any attachments larger than 10 KB.

The following are examples of the possible use of rules to match attachments.



<RULE NAME="Attachment Match" ATTACHMENT_ACTION="REPLACE">
<FILES INCLUDES="ANY">
<FILE FILENAME="*.MP3" SIZE_GREATER_THAN_KB="2000" />
<FILE FILENAME="*Washington*.*" SIZE_GREATER_THAN_KB="1000" />
<FILE FILENAME="*.MPG" />
<FILE SIZE_GREATER_THAN_KB="12000" />
</FILES>
</RULE>



<RULE NAME="Attachment Match" ATTACHMENT_ACTION="REPLACE">
<FILES INCLUDES="NONE">
<FILE FILENAME="Symantec.JPG" />
<FILE FILENAME="VERITAS.JPG" />
<FILE FILENAME="Voicemail_*.MPG" />
</FILES>
<FILES INCLUDES="ANY">
<FILE FILENAME="*.MP3" SIZE_GREATER_THAN_KB="2000" />
<FILE FILENAME="*.JPG" SIZE_GREATER_THAN_KB="1000" />
<FILE FILENAME="*.MPG" SIZE_GREATER_THAN_KB="5000" />
<FILE FILENAME="*Debt*.txt" />
</FILES>
</RULE>



<RULE NAME="Unwanted Attachments Non directors" ATTACHMENT_ACTION="REPLACE">
<RECIPIENTS INCLUDES="NONE" ALLOWOTHERS="N">
<EA>John.Smith@symantec.com</EA>
<EA>Jane.Doe@symantec.com</EA>
</RECIPIENTS>
<FILES INCLUDES="ANY">
<FILE FILENAME="*.MP3" SIZE_GREATER_THAN_KB="2000" />
<FILE FILENAME="*.JPG" SIZE_GREATER_THAN_KB="1000" />
<FILE FILENAME="*.MPG" SIZE_GREATER_THAN_KB="5000" />
</FILES>
</RULE>



<RULE NAME="Junk Mail" ACTION="MARK_DO_NOT_ARCHIVE" ATTACHMENT_ACTION="REMOVE">
<AUTHOR INCLUDES="ANY" ALLOWOTHERS="Y">
<DOMAIN>spam.com</DOMAIN>
<DOMAIN>medical-usa.net</DOMAIN>
</AUTHOR>
<SUBJECTS INCLUDES="ANY">
<SUBJ MATCH="CONTAINS">washington</SUBJ>
<SUBJ MATCH="CONTAINS">weight loss</SUBJ>
</SUBJECTS>
<SUBJECTS INCLUDES="ALL">
<SUBJ MATCH="CONTAINS">debt</SUBJ>
<SUBJ MATCH="CONTAINS">loan</SUBJ>
</SUBJECTS>
<FILES INCLUDES="ANY">
<FILE FILENAME="*.MP3" SIZE_GREATER_THAN_KB="2000" />
<FILE FILENAME="*.JPG" SIZE_GREATER_THAN_KB="1000" />
<FILE FILENAME="*.MPG" SIZE_GREATER_THAN_KB="5000" />
</FILES>
</RULE>



<RULE NAME="Selected Files" ATTACHMENT_ACTION="REMOVE">
<FILES INCLUDES="NONE">
<FILE FILENAME="*.TXT" />
<FILE FILENAME="*.DOC" />
</FILES>
</RULE>

Unable to access the properties of File Server archiving target after upgrading to Windows Server 2003 SP1 [Ref: 601446]

After you upgraded the Enterprise Vault server to Windows Server 2003 SP1, you may have been unable to view the properties of a file server in the Vault Administration Console, and the event log may have contained 40974 messages ("Unable to access the Directory Service"). This problem occurred only if you had previously configured the Enterprise Vault using vault and site aliases.

This problem has now been fixed.

Mailbox synchronize handles changes to cross-domain trusts [Ref 601373]

Where an Enterprise Vault server processed mailboxes in different domains, the synchronize process could stop responding when attempting to synchronize the folder hierarchy and permissions on the user mailboxes. This happened when the following criteria were met:

The Enterprise Vault server was installed on Windows Server 2000
A user in one domain had access to the mailbox of a user in another domain
The trust between the domains broke

This has been fixed.

Required message property not archived [Ref 601535]

A required message property (ptagInetMessageID) was deleted upon archiving. If the message contained Unicode characters, this could results in some of those characters being corrupted.

This has been fixed.

Original items can now be opened in OWA [Ref 601303]

When you opened a shortcut in an OWA client, you could not view the original, archived item. The following message was displayed in the message banner:

The archived item is currently unavailable

This has been fixed. When you view an archived item by double-clicking the shortcut or clicking the banner link in the shortcut, the original item is now displayed.

Journaling Task correctly handles messages from Active Directory Contacts [Ref 601434]

If a message was sent from an external SMTP address that had been added to Active Directory as a Contact, the Exchange Journaling Task incorrectly assigned a message direction of 'internal'. In a few circumstances, this could result in a Compliance Accelerator search for inbound messages not returning the message.

This has been fixed.

Improved event message for failed Centera Collections [Ref 601497]

If Centera Collection data could not be written to a Centera Clip or to a temporary collection area, the following general event was logged:

Error storing saveset in EMC Centera

Reason:

The event logged now specifies whether the error occurred when attempting to write to a Centera Clip or to a Centera Collection temporary file location.

Download Now - 98475 K
File Name: ev60_sp1_279962.zip
File Type: Patch

Click Below to Browse the FTP files by Product:
ftp.support.veritas.com/pub/support/products

Products Applied:
Enterprise Vault for File System Archiving 6.0 SP1
Enterprise Vault for Lotus Domino 6.0 SP1
Enterprise Vault for Microsoft Exchange 6.0 SP1
Enterprise Vault for Microsoft Sharepoint 6.0 SP1
Enterprise Vault for SMTP 6.0 SP1

Last Updated: February 27 2006 04:59 PM GMT
Expires on: 365 days from publish date

Subscribe to receive critical updates about this document

Subjects:
Enterprise Vault for File System Archiving
   Application: Patch
   Documentation: Configuration
Enterprise Vault for Lotus Domino
   Application: Patch
   Documentation: Configuration, Installation
Enterprise Vault for Microsoft Exchange
   Application: Patch
   Documentation: Configuration, Installation
Enterprise Vault for Microsoft Sharepoint
   Application: Patch
   Documentation: Configuration
Enterprise Vault for SMTP
   Application: Patch
   Documentation: Configuration, Installation

Languages:
English (US)

Operating Systems:
Windows 2000

Advanced Server SP1, Advanced Server SP2, Advanced Server SP3, Advanced Server SP4, Datacenter Server SP1, Datacenter Server SP2, Datacenter Server SP3, Datacenter Server SP4, Server SP1, Server SP2, Server SP3, Server SP4

Windows Server 2003

DataCenter, DataCenter SP1, Enterprise Server, Enterprise ServerSP1, Standard Server, Standard Server SP1

Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.