Last updated: 02-Jul-2012
|
To download the latest version of this document and the other Enterprise Vault release notes, or to obtain Japanese or Simplified Chinese versions, see article TECH147785 on the Symantec Enterprise Support site. For the latest news about this release, including any hotfixes, subscribe to http://www.symantec.com/docs/TECH147786. Note: If you downloaded the original version of Enterprise Vault 9.0.4 on or before 28 June 2012 (version 9.0.4.1095), you must download the updated version that fixes the issue described in http://www.symantec.com/docs/TECH192064. The updated version of Enterprise Vault 9.0.4 was released on 06 July 2012. |
This document describes Enterprise Vault 9.0. Before you install or upgrade to Enterprise Vault 9.0.4, it is important to read the Points to note and issues sections of this document.
For information about changes in Enterprise Vault 9.0.4, see the Enterprise Vault 9.0.4 document, which is included as Updates_en.htm on the Enterprise Vault media.
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 media.
If you are upgrading from an earlier version of Enterprise Vault, follow the instructions in
Upgrading to Enterprise Vault 9.0.4, included as Upgrade_Instructions.pdf and Upgrade_Instructions.chm in the Symantec Enterprise Vault 9.0.4 folder on the Enterprise Vault media.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
For the latest information on Enterprise Vault 9.0 sizing and performance, see the Enterprise Vault Performance Guide at http://www.symantec.com/docs/TECH125795.
Enterprise Vault 9.0 provides the following new features:
The Enterprise Vault 9.0.4 document describes the changes included in Enterprise Vault 9.0.4. New features and changes in earlier Enterprise Vault 9.0 service packs are described in the Previous Updates document.
Enterprise Vault 9.0 supports mailbox, journal, and public folder archiving from Exchange Server 2010 SP1. In addition to the Enterprise Vault functionality provided for earlier versions of Exchange Server, Enterprise Vault provides support for the new features in Exchange Server 2010, as outlined in this section.
A PowerShell script is provided to configure permissions for the account under which you want Enterprise Vault tasks to run. You can use this script to configure the account permissions for Exchange Server 2010 and 2007 archiving. You can also use the script to configure the account permissions for Exchange Server 2003 archiving, but only in a domain that includes either Exchange Server 2007 or Exchange Server 2010.
The icons in OWA have been refreshed to match UI changes in OWA 2010.
As OWA 2010 Premium client does not include a toolbar, Enterprise Vault buttons are not displayed in the top right area of the client window. Instead, the available options are on the context (right-click) menu. In conversation view, the available options for selected items also appear on the Actions menu in the reading pane. In the OWA 2010 Light client, the available Enterprise Vault options are on the toolbar, as in earlier versions of OWA.
Shortcuts are supported in OWA 2010 conversation view.
In Microsoft Exchange Server 2010, Information Rights Management allows Microsoft Outlook and Microsoft Office Outlook Web App users to protect their messages. The journal report decryption feature allows you to save a clear text copy of RMS-protected messages in journal reports, together with the original RMS-protected message. Note that Exchange Server does not decrypt attachments that are individually RMS-protected.
If journal report decryption is configured on Exchange Server 2010, then two messages are attached to the journal report – a protected message and a clear text message. Enterprise Vault archives both messages. A new advanced setting in the Exchange Journal policy, ClearText copies of RMS Protected items, lets you select whether Enterprise Vault uses the clear text message or the RMS-protected message as the primary message during archiving. By default, Enterprise Vault uses the clear text message as the primary message.
Important If you have custom filters configured for Exchange Server journal archiving, check that the filters work as expected.
The following table describes the effect of using the different option values:
| Option value | Effect | Notes |
|---|---|---|
| Treat as Primary | The clear text message is returned in response to retrieval requests from Enterprise Vault clients and Symantec Discovery Accelerator. | As Exchange Server does not decrypt any RMS-protected attachments, Enterprise Vault cannot preview these attachments. |
| Enterprise Vault indexes the content and properties of the clear text message, and any attachments that are not encrypted. | With this option, single instance sharing between Exchange mailbox and journal archiving is not possible. As Exchange Server does not decrypt any RMS-protected attachments, Enterprise Vault cannot index these attachments. |
|
| Existing Enterprise Vault Exchange journal filters work with clear text messages. | Filters that process RMS-protected messages must explicitly retrieve the RMS-protected message from the attachments to the journal report message (P1 message). | |
| Treat as Secondary | The RMS-protected message is returned in response to retrieval requests from Enterprise Vault clients and Symantec Discovery Accelerator. | Enterprise Vault cannot preview these messages unless an application, such as the Enterprise Vault Adapter for Secure Messaging and Rights Management (SMRM), is used to decrypt the messages. |
| Information available for indexing is restricted to Subject, Recipients and other message metadata. | The item can be shared between Exchange mailbox and journal archiving. The message content and attachments are not indexed, unless an application, such as the Enterprise Vault Adapter for Secure Messaging and Rights Management (SMRM), is used to decrypt the messages. |
|
| Existing Enterprise Vault Exchange journal filters that process RMS-protected messages should work without adjustment. | Filters that do not decrypt RMS-protected messages cannot read the message content. |
When the Virtual Vault policy is set to allow users to move or copy items from their mailboxes into Virtual Vault to archive them, the items exist only on the user's computer until they are archived by Vault Cache synchronization. Two new Virtual Vault advanced settings in the Exchange desktop policy let you control when Vault Cache synchronization occurs, so you can minimize the risk of data loss.
The settings are Threshold number of items to trigger synchronization and Threshold total size of items to trigger synchronization. They specify thresholds for the number and total size of pending archive items in Virtual Vault. Each setting triggers an automatic Vault Cache synchronization if it is reached or exceeded. By default, the threshold settings are not active.
For more information, see the Setting up Vault Cache and Virtual Vault chapter in the Setting up Exchange Server Archiving manual.
The following SharePoint Server archiving features are new for Enterprise Vault 9.0:
Enterprise Vault 9.0 includes the following new Domino archiving features:
FSAUtility includes a new -b option to
perform bulk recall of files corresponding to placeholders in a folder or volume. This
option also allows you perform a bulk recall of files recursively from subfolders.
FSAUtility now includes a -pm option to migrate placeholders and archive points from a source folder structure to a destination folder structure. The option is intended for file server consolidations and migrations. Placeholders are moved between volumes or file servers. The option does not move any archived data. This allows for efficient migrations.
Do not use the -pm option when the movement of archived data is required. Use the existing -m option if you want to move archives, consolidate vault stores, or align archives with file servers.
For more information, see the description of FSAUtility in the Utilities guide.
FSAUndelete is a new command line utility that cancels the permanent deletion of the archived items for specified placeholders, or for all of the placeholders in a specified folder of a file server.
For more information, see the chapter on FSAUndelete in the Utilities guide.
Support is now provided for the coexistence of non-Enterprise Vault reports with Enterprise Vault Reporting on the same Microsoft SQL Server Reporting Services server.
FSA Reporting includes several changes to improve scalability and performance. The changes include:
New and updated wizards provide guided workflow for the configuration of FSA Reporting, including the assignment of FSA Reporting databases and proxy servers to file server targets.
A new Operation report named Items Archival Rate replaces the Items Archived per Hour report. The new report shows the number of items that Enterprise Vault archives per hour, day, month, or year.
For more information, see the Reporting guide.
You can now use the Enterprise Vault Client for Mac OS X with the following versions of Mac OS X:
Enterprise Vault 9.0 includes client access for Microsoft Entourage 2008 Web Services Edition. Users can now access archived information and search using the Enterprise Vault Client for Mac OS X.
Enterprise Vault 9.0 supports Enterprise Vault Discovery Collector, an add-on for Enterprise Vault that addresses your eDiscovery needs during the identification, collection, and preservation phases of eDiscovery. Discovery Collector extends indexing and classification of data beyond the archive, enabling targeted collection and preservation of active content from laptops and desktops, network servers, storage systems, and application repositories. Discovery Collector allows active content collected from unmanaged content stores to be stored for preservation in Enterprise Vault, leveraging the storage benefits of Enterprise Vault and the discovery analysis and review capabilities of Discovery Accelerator.
Full documentation for Discovery Collector is included with the product.
It is important that you check the prerequisites in Installing and Configuring for the types of archiving and Enterprise Vault features that you plan to implement.
To archive from Exchange Server 2010, you must install the following on the Enterprise Vault server:
To archive from Exchange Server versions prior to Exchange Server 2010, you must install one of the following on the Enterprise Vault server:
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
If an end user's computer is running Outlook 2010, it is only possible to install the Enterprise Vault HTTP-Only Outlook Add-In. The Enterprise Vault installer prevents the installation of the Enterprise Vault Outlook Add-In.
If you install the Enterprise Vault 9.0.4 Outlook Add-In on Outlook 2003/2007 and later upgrade to Outlook 2010, you must then install the Enterprise Vault 9.0.4 HTTP-Only Outlook Add-In.
When targeting an Exchange 2010 journal mailbox, the Enterprise Vault journal archiving task can fail during the expansion of distribution lists that contain hidden users or hidden distribution lists.
If you target Exchange 2010 servers, and any of the messages that you archive contain hidden users or distribution lists, see http://www.symantec.com/docs/TECH154813 on the Symantec Support Web site for additional configuration information.
The minimum version of SCOM 2007 is SCOM 2007 R2. You cannot import the Enterprise Vault SCOM management pack into the SCOM 2007 original release.
Before installing Enterprise Vault 9.0.4, or upgrading, we strongly recommend that you run the Deployment Scanner to check prerequisite software and settings.
The Deployment Scanner is included in the Symantec Enterprise Vault 9.0.4\Deployment Scanner folder on the Enterprise Vault media.
Use the Vault Service account when running the Deployment Scanner.
To install the 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.
If you specify a SQL Server in the Deployment Scanner's configuration options, the scanner first checks for the presence of Microsoft SQL Server Reporting Services, which is a prerequisite for Enterprise Vault Reporting and FSA Reporting.
If the appropriate version of Reporting Services is not installed, the Deployment Scanner reports that Enterprise Vault Reporting and FSA Reporting cannot be configured on the SQL server.
The Deployment Scanner also checks for versions of ASP.NET that are installed on the Enterprise Vault server.
On Windows Server 2003 it also determines whether the status of ASP.NET is set to "Allowed" in IIS Manager:
To ensure that the status of ASP.NET is set to "Allowed" on Windows Server 2003, do as follows:
The installation of the Enterprise Vault Deployment Scanner on a Windows domain controller is not supported.
If you have applied Federal Desktop Core Configuration (FDCC) group policy objects (GPO) to Windows XP and Vista computers, then all user-based settings in the local intranet zone in Internet Explorer are removed. Users cannot change these settings on FDCC-compliant computers. Also, if you have enabled the advanced Exchange desktop policy setting, Add server to intranet zone, then this setting will no longer work.
If Enterprise Vault servers are not added to the local intranet zone in Internet Explorer on desktop computers, then users need to enter authentication credentials each time they access Enterprise Vault. You can add the Enterprise Vault server details to FDCC-compliant computers by modifying the FDCC Internet Explorer GPO. How to do this is described in the section "Publishing Enterprise Vault server details to FDCC-compliant computers" in the Installing and Configuring manual.
If you use the option to browse for a list of available SQL Servers in the Getting Started wizard or the Administration Console, Enterprise Vault may not always display a complete list.
If necessary, use the option to enter the name of the required SQL Server manually.
Some Vault Cache advanced settings and Outlook Add-Ins registry values have been removed from Enterprise Vault 9.0.
These advanced settings and registry values were present in Enterprise Vault 8.0, including service packs, but they only applied to Outlook Add-In versions earlier than Enterprise Vault 8.0.
For details, see Upgrading to Enterprise Vault 9.0.4.
When Vault Cache is enabled for a user, Enterprise Vault always creates shortcuts in that user's mail file. This behavior ignores the setting of 'Create shortcut to archived item after archiving' on the 'Archiving Actions' tab of Domino Mailbox Policy Properties.
Before Enterprise Vault 9.0, Enterprise Vault could fail to create shortcuts for recalled FSA items that were originally archived prior to Enterprise Vault 7.0. The following errors could appear in the File System Archiving task report for the archiving run:
The problem occurred because of an error when Enterprise Vault attempted to determine the size of the legacy item to show in the properties of the shortcut.
This has been fixed. Now, on the first occasion that Enterprise Vault recreates a shortcut for the recalled legacy item, it obtains the size of the item from the saveset and updates the vault store database with this information. Enterprise Vault only has to obtain this information on the first occasion that it recreates the shortcut. On subsequent recalls, Enterprise Vault uses the saved database value when it recreates the shortcut.
Note that obtaining the legacy item sizes may prolong a File System Archiving run. However, a run is only likely to take significantly longer than usual if both of the following apply:
For this fix to work with a Windows file server, you must install the Enterprise Vault 9.0 FSA Agent or later on the file server.
To improve the efficiency of report generation, Enterprise Vault now maintains tables of consolidated metadata in each vault store database about the archived items.
Before it fetches information from the consolidated metadata tables, Enterprise Vault Reporting forces an update of the tables with the latest archive information. Note that if Items are archived to a vault store after the update is done, then information on those archived items may not be included in the current report.
For important guidelines on the deployment of FSA Reporting, see the following Enterprise Vault technical note: http://www.symantec.com/docs/TECH72062.
You cannot add the Enterprise Vault Domino Gateway software to a Domino 64-bit installation. The setup program does not give you the option to install Enterprise Vault Domino Gateway software to a Domino 64-bit installation.
You can add the Enterprise Vault Domino Gateway software to a Domino 32-bit installation that is running on a 64-bit version of Windows.
You can specify that Enterprise Vault must perform a local address lookup for specific Notes domains. The local lookup enables Enterprise Vault to identify the Lotus Notes user name for messages that are addressed to alternate email addresses. The local lookup results can aid searching in the Web applications and in Compliance Accelerator and Discovery Accelerator.
In order to specify the domains that require local address lookup you must make some changes to the registry on the Enterprise Vault servers that run the journaling and archiving tasks.
To specify local lookup domains
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\Agents
exampledomain1.com;exampledomain2.com
The following table shows how Enterprise Vault behaves, depending on what you have set for the registry keys and values.
| NotesDomains key is missing | Full address lookup and a warning in the event log. |
| NotesDomain key is present but has no key for the current Notes domain | Original address is recorded. No lookup. |
| NotesDomain key is present and has a key for the current Notes domain |
|
When you add NSF files for migration in NSF migrator, you must use full UNC paths to access them, rather than mapped or local drive letters.
This is because the NSF migrator server that processes the NSF files may be on a different computer from the NSF migrator wizard, and may use a different user context than the one under which NSF migrator is running. In both these cases, only full UNC paths provide a reliable way for the NSF migrator server to access the files.
Enterprise Vault menu options and buttons do not appear in Outlook until the user's mailbox has been enabled and the user has restarted Outlook. Similarly, Enterprise Vault menu options do not appear in Lotus Notes until the user's mailbox has been enabled and the user has reopened their mailbox.
You can therefore roll out the Enterprise Vault Outlook Add-Ins, or the Enterprise Vault extensions for Lotus Notes, before users' mailboxes are enabled.
For information on enabling mailboxes, see Setting up Exchange Server Archiving and Setting up Domino Server Archiving.
If you want to retain archived items forever on a WORM, SnapLock or Compliance device, you must configure infinite retention on the device volume. For instructions, see the documentation that is provided with your device. You must also use an Enterprise Vault retention category that specifies a retention period of "Retain items forever".
Name Service Provider Interface (NSPI) connections from Outlook to Windows Server 2008 domain controllers can fail with error MAPI_E_LOGON_FAILED.
This happens because Windows Server 2008 domain controllers restrict NSPI connections to 50 concurrent connections per user. There was no restriction on concurrent NSPI connections in earlier versions of Windows Server operating systems. You must remove this restriction to prevent the failure of Enterprise Vault tasks.
To remove the restriction on concurrent NSPI connections to a Windows Server 2008 domain controller:
On the Windows Server 2008 domain controller, create a new registry DWORD value called NSPI max sessions per user under the following registry key:
HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \NTDS
This sets NSPI max sessions per user to its maximum value. In effect, this removes the restriction on concurrent NSPI connections by each user.
For more information about this issue, see the following technical note on the Symantec Support web site: http://www.symantec.com/docs/TECH73507.
Enterprise Vault 9.0 does not support SharePoint Portal Server 2003 or Windows SharePoint Services 2.0. If you use SharePoint Portal Server 2003 or Windows SharePoint Services 2.0, you must upgrade SharePoint before you can upgrade Enterprise Vault.
See Upgrading to Enterprise Vault 9.0.4 for more details.
If you attempt to archive from a SharePoint Portal Server 2003 or Windows SharePoint Services 2.0 site, the following warning is logged in the Enterprise Vault event log:
Event Type: Warning Event Source: Enterprise Vault Event Category: SharePoint Task Event ID: 41025 Description: The EVCustom web service on SharePoint server 'http://myserver' version 21 does not match the archiving task version 25. Check that the Enterprise Vault components have been installed correctly on this SharePoint server.
There are changes to the prerequisite software at Enterprise Vault 10.0, the next major release after Enterprise Vault 9.0. For example, Windows Server 2003 is no longer supported as the operating system on the Enterprise Vault server. For details of the changes, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
When you install Enterprise Vault 8.0 SP2 or later on a cluster, event 10016 is logged repeatedly in the System event log. This event is logged on both VERITAS and Microsoft clusters, and for both new installations and upgrades.
The event is logged repeatedly until shortly after you start the Directory service.
The event in the System log is similar to the following:
Event Type: Error Event Source: DCOM Event Category: None Event ID: 10016 Date: 6/24/2009 Time: 10:16:31 AM User: DEMO\evvsa Computer: EV1 Description: The application-specific permission settings do not grant Remote Launch permission...
You can ignore this event.
Some storage devices that were certified for use with Enterprise Vault 8.0 have not yet been certified for Enterprise Vault 9.0.
Before you upgrade, check the Compatibility Charts for details of the supported devices:
http://www.symantec.com/docs/TECH38537
If your storage device is not certified, contact Symantec support.
IBM hotfixes may remove the version number from two Lotus Domino files, nserver.exe and nservice.exe. If the version information is absent on both these files, the Deployment Scanner cannot determine the Lotus Domino version number.
When this happens, the Deployment Scanner reports that the version of Domino could not be determined, but allows the installation to continue.
When you run EVInstall.nsf to install the Enterprise Vault client functionality, the installation modifies the following files 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 the Forms databases:
Forms85.nsf, Forms8.nsf, Forms6.nsf,
Forms7.nsf, Forms8.nsf.
By default, the folder is C:\Program Files\Lotus\Domino\Data\iNotes
Forms85.nsf, Forms8.nsf, 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
EVInstall.nsf creates non-replicating database. If you use EVInstall.nsf on multiple Domino mail servers, EVInstall.nsf creates a non-replicating database on each mail server.
If necessary, you can use EVInstall.nsf on one mail server and then manually replicate the Enterprise Vault mail databases to your other mail servers as appropriate.
When you run EVInstall.nsf it generates new Enterprise Vault mail template files, overwriting all existing Enterprise Vault mail template files. The new files do not have the same replica IDs as the overwritten files.
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 duplicate 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 duplicate 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 duplicate template dwa7 in database C:\Program Files\Lotus\Domino\data\ev_dwa7.ntf - rejected.
For details of the procedure for removing Enterprise Vault from a Domino mail server and an Enterprise Vault Domino Gateway server, see the following technical note on the Symantec Enterprise Support site: http://www.symantec.com/docs/TECH52347.
This note applies if you have installed Terminal Services on a computer on which you want to install Enterprise Vault. (From Windows Server 2008 R2, Terminal Services is known as 'Remote Desktop Services'.)
If Terminal Services is installed, you must switch the terminal server to install mode before you perform the installation of Enterprise Vault. Otherwise the installation may fail.
To switch the terminal server to install mode, open a command prompt window on the computer and enter the command change user /install.
When you have finished the installation of Enterprise Vault, return the terminal server to its normal 'execute' mode. To do this, open a command prompt window on the computer and enter the command change user /execute.
For more information about installing programs on a terminal server, see the following Microsoft knowledge base article:
http://technet.microsoft.com/en-us/library/cc742815(WS.10).aspx
For the latest information on any known vulnerabilities in the third-party components that are provided on the Enterprise Vault media, see the following technical note on the Symantec support web site:
http://www.symantec.com/docs/DOC2264
Connections to Exchange Server may fail when you use Outlook 2007 on a busy Enterprise Vault server.
If this issue occurs, various errors may be logged, including errors in the following event categories:
The issue can occur because it is possible to exceed the size of the Outlook 2007 credential cache, as the cache can hold details of a maximum of 32 objects (MAPI connections).
If you encounter this issue, we recommend that you apply the Outlook 2007 hotfix described in the following Microsoft article:
http://support.microsoft.com/kb/2475891
With this hotfix applied, the cache limit is increased to 100 objects or MAPI connections.
Using Outlook 2007 on the Enterprise Vault server creates a large number of registry entries under the registry key \HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Catalog, which may affect performance on the server.
For more information and a workaround, see the following technical note on the Symantec Enterprise Support site: http://www.symantec.com/docs/TECH128684.
This issue relates to the way that Enterprise Vault archives calendar items, and task and task request items.
If a user changes both the reminder and the content (that is, the item subject or body content) of a calendar or task item that has been archived on a previous archiving run, then the item will not be archived again when the Exchange Mailbox task next runs. The item will only be re-archived at a later date if the user changes only the content again.
It is possible to misconfigure Exchange Desktop policy settings in the Administration Console so that Outlook users working in Cached Exchange Mode can only access Offline Archive Explorer, but cannot enable Vault Cache.
This issue occurs if you configure Exchange Desktop policy settings as follows:
If you use OWA 2010 Light client with forms-based authentication, then you must also add the following line to the <appSettings> section of the Web.Config file
(in Exchange Server installation path\V14\ClientAccess\Owa\):
<add key="EnterpriseVault_EnableExtensionsInOwaAuthClient" value="true"/>
Note Enterprise Vault supports the OWA client in Internet Explorer browsers only. Enterprise Vault features may be visible when using other browsers with this setting, but they may not work as expected.
The Browser search link on the Search Archives page may be hidden from OWA 2003 users even though the option Show 'Browser Search' link in Integrated Search is checked. This option is on the Exchange Desktop Policy Web Applications page.
The link remains hidden if the OWA advanced setting Client connection in the Exchange Desktop Policy is set to Use proxy.
For any other type of connection, the option Show 'Browser Search' link in Integrated Search is respected for OWA 2003 users.
The following issue can occur in OWA Premium client:
This occurs if the following conditions are met:
To fix the problem, ensure that the Enable Protected Mode setting is the same for the Internet Explorer security zones that contain the OWA URL and the Enterprise Vault integrated search URL.
The following steps describe how to determine the URLs and check the Enable Protected Mode setting:
http(s)://Enterprise_Vault_server/EnterpriseVault/searcho2k.aspEnterprise_Vault_server is
the name of the Enterprise Vault server to access. This issue affects archived encrypted items with one or more attachments, when the item has been retrieved and is open. In iNotes 8.5.1, you cannot reply to or forward the open item if the reply or forward option does not include the attachments.
For example, the issue occurs with Reply and Reply With History Only. It does not occur with Reply With History & Attachments.
If the issue occurs, you see the following error message:
The encrypted data has been modified or the wrong key was used to decrypt it.
As a workaround, you can do one of the following:
In iNotes, you can open Notes encrypted messages but you cannot open Secure/MIME (S/MIME) encrypted messages.
A new feature in Enterprise Vault 9.0 is the automatic deletion of shortcuts in Domino mail files. If you have shortcuts that were created by an earlier Enterprise Vault release we recommend that you implement shortcut deletion gradually.
If you implement shortcut deletion for all mailboxes immediately, the effect of deleting old shortcuts from thousands of mailboxes can have an impact on Domino server and network performance. In particular, the shortcut deletion can affect compaction, replication, and index updates.
To minimize these effects, you can use either of the following methods to introduce shortcut deletion gradually:
You must grant Execution Control List (ECL) permissions to Vault Cache users so that they do not receive ECL alerts.
You must grant the following ECL permissions to Vault Cache users:
Access to current database Access to environment variables Ability to read other databases Ability to modify other databases Access to external code
This issue may occur when you are using a Domino 8 mail server and a Lotus Notes user replies to an archived message using one of the following options:
If the user then chooses the Send and File option, the user's folder list in the Folders dialog may be incorrect.
The IBM mail template for Domino 8 includes split buttons for Reply, Forward, and a number of other Notes buttons. The new split buttons are not available in the Enterprise Vault mail template for Domino 8 (ev_mail8.ntf).
This issue results from a Notes API limitation that is being assessed by IBM.
It is possible to restore the functionality using a manual workaround. For assistance, contact Symantec support and quote Etrack number 1414916.
Due to a Lotus Notes issue, Enterprise Vault servers that run any of the following Lotus Notes versions do not archive Domino MIME format messages with Mac BinHex attachments:
There is a workaround to this issue, as follows:
DominoArchiveMacBinHexOnNotes8 in the following
location on the server that runs the archiving task:
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\Agents
Give DominoArchiveMacBinHexOnNotes8 a value of 1 to make the task archive BinHex
attachments. Give DominoArchiveMacBinHexOnNotes8 a value of 0 to make the task ignore
BinHex attachments.
Domino users must be hierarchically named. Enterprise Vault cannot provision users who are not hierarchically named.
The Domino Web Access Lite client supplied with Lotus Domino 8.0.1 is not supported by Enterprise Vault.
Attempting a cut and paste of an Enterprise Vault shortcut triggers an item delete to occur. Depending on your desktop policy, this can also delete the item from the Enterprise Vault archive.
This issue arises because the Lotus Notes client handles cut operations and delete operations in exactly the same way. So, cutting a shortcut deletes the associated item from the Enterprise Vault archive and turns the shortcut into an orphaned shortcut. Symantec has submitted an enhancement request to IBM to address this issue in future versions of the Lotus Notes client.
In the Notes preview pane, a link to an attachment does not work when there is no associated application for the attachment's file type.
To obtain the attachment, the user must first open the whole item and then open the attachment.
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.
In Lotus Notes 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.
When you select a shortcut in either an online mail database or a local mail replica and then click the Print icon, the shortcut is printed rather than the archived item. To print the item, you must open the shortcut and view the item before you click Print.
If you select an archived item in the Domino Web Access (DWA) client and then click Print, the restore action fails and an error message is displayed. If you view the item first, you can print it successfully.
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
When a 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.
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 person document.
Enterprise Vault actions appear on the Tools menu in Lotus Domino WebMail, but cause errors when users click them.
Note: This issue occurs only with Enterprise Vault actions in Lotus Domino WebMail, not in Domino Web Access (DWA). If a user's mail database uses the template named Domino Web Access (Rn) w/ Enterprise Vault, the webmail view is DWA. If it uses the template named Mail (Rn) w/ Enterprise Vault, the webmail view is Lotus Domino WebMail.
When you configure Enterprise Vault on Windows 2003 or Windows 2008 you may see performance counter warnings in the Application log.
You can ignore these warnings.
For more information, see the following Microsoft support article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;928384
Under very rare circumstances, the Enterprise Vault Administration Console could fail on multi-processor systems if left open for a very long time, typically a number of hours.
If you experience this problem:
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.
When you add a new Enterprise Vault server to an existing site, a Task controller service is not added to the server. This can cause Move Archive operations to fail.
When you add a new server, you should manually create a Task controller service if you plan to use Move Archive.
To add a Task controller service:
Move Archive operations can fail for archives whose associated destination mailboxes have reached or exceeded their quotas. This is because Move Archive cannot complete shortcut processing when these mailboxes are full.
You should temporarily disable Exchange mailbox quotas on associated destination mailboxes until the Move Archive operations have completed.
By default, the Enterprise Vault Configuration Wizard adds a domain suffix to the computer alias you provide for each storage service computer, to create a fully qualified domain name.
However, it is possible to configure storage service computers without a fully qualified domain name. This can cause Move Archive to fail if it cannot resolve computer names only by their aliases.
If you have configured your storage service computers using only aliases, you must add the list of storage service computer aliases, and their fully qualified domain names to the hosts file on each storage service computer.
During a Move Archive operation, users can delete items from the destination archive before the Move Archive verification takes place. Under normal circumstances, the Move Archive log file includes these items in the count of items deleted by the user. However, under some circumstances these items can be reported in the count of items deleted by storage expiry, even when storage expiry does not run in your environment.
This happens when the Enable recovery of user deleted items option is set, and the Number of days until items are permanently deleted is set to a low value. In this case, when a user deletes an item and it is permanently deleted before Move Archive verification takes place, the item is reported as expired, not as a user deletion.
When you use Move Archive, unsynchronized items in users' Virtual Vaults can become inaccessible following the move.
To avoid this situation, before you run Move Archive:
Once you have moved archives, you can enable the Users can archive items setting again.
The PST locator task needs the Remote Registry service to be running on the client computers it searches. By default, the Remote Registry service is set to Automatic on versions of Windows up to Windows XP. However, its default setting on Windows Vista is Manual.
In support of the PST locator task's requirements, ensure the Remote Registry service is configured to start automatically on Windows Vista clients.
Client-side PST migration may expose an Outlook 2003 handle leak.
See the following Microsoft article for more information: http://support.microsoft.com/kb/893420
Microsoft has fixed this issue in Outlook 2007.
If users experience this issue, they should close Outlook to release the open file handles.
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.
There is a risk of a substantial memory leak when running Microsoft Outlook 2003 SP2 with the Enterprise Vault server or client software. The leak occurs when Enterprise Vault accesses or creates PST files.
For details of the problem and a link to the Outlook 2003 update that removes the risk of the memory leak, see the following technical note on the Symantec Enterprise Support site: http://www.symantec.com/docs/TECH46028.
In environments where Enterprise Vault servers have no Internet access, NSF migration fails and writes the following error to the event log:
Unable to initialize the Notes runtime system
This happens when Windows tries to check for revocation of the digital signatures that are used to sign the Enterprise Vault executables used by NSF migration.
If your Enterprise Vault servers have no Internet access and you experience this issue, you can prevent Windows from checking for certificate revocation by using an application configuration file for each of the following Enterprise Vault executables:
AdminService.exeDirectoryService.exeNSFMigratorServer.exeStorageCrawler.exeStorageRestore.exeNote: The following procedure describes the creation of an application configuration file for each of these executables. If you have already created an application configuration file for any of these executables, you must add the XML described in Step 1 to the existing file, rather than create a new file.
To create an application configuration file:
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>
Save the file in the Enterprise Vault installation folder (normally C:\Program Files\Enterprise Vault) using the name of the executable with ".config" appended.
For example, for AdminService.exe, save the application configuration file as AdminService.exe.config.
NSF migrator does not make allowance for duplicate user names in a Domino organization. These can occur in a multi-domain organization when Directory Assistance is configured.
When NSF migrator is configured to match archives to mail files automatically, in each case it uses the first match. When duplicate names exist in the Domino organization, you should manually match archives to mail files.
NSF migrator cannot create a shortcut in the mail file when its Universal Note ID (UNID) is the same as the UNID of an item already in the mail file. For example, this can occur when the source NSF file is a replica of a user's mail file, and the items NSF migrator is processing are duplicates of the items already in the mail file.
In this case, the items in the NSF file are archived, but no shortcuts are created in the mail file.
In Microsoft SharePoint 2010, default security for browser handling of HTML files has been increased. This change affects Internet (HTML) shortcuts that were created on Microsoft Office SharePoint Server 2007 (MOSS 2007) or Microsoft Windows SharePoint Services 3.0 (WSS 3.0) using Enterprise Vault 8.0 SP2 or earlier.
If you attempt to open one of these Internet shortcuts after upgrading to SharePoint 2010, you can save the file but not open it. To be able to open these Internet shortcuts, you need to perform the additional configuration described in this section.
Note Shortcuts that were created by Enterprise Vault 8.0 SP3 or later work as expected, and no additional configuration is necessary.
To be able to open affected Internet shortcuts, perform the following configuration change in SharePoint:
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
When archiving items from SharePoint servers, 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.
On EMC Celerra devices FSAUtility fails to process files and folders if the target path exceeds 1024 characters. An event viewer message on the Enterprise Vault server states that the input string was not in a correct format.
This is due to a limitation with Celerra.
Note the following points when specifying paths to archive point shares:
Under some circumstances, a change in behavior on Windows Server 2008 and later versions generates errors during shortcut creation, even though the operation is successful.
For each file that was archived previously and whose shortcut is created in the current run, the following error is written to the event log:
Validation for placeholders <file name> failed. Reason: file is not a placeholder.
This happens when both Enterprise Vault and the file server are running Windows Server 2008 or later versions.
This note applies if you configure File System Archiving for a Windows file server that runs Windows Server 2003 or 2008, and on which Windows Firewall is enabled.
You must perform some additional FSA configuration steps to enable the Enterprise Vault server to establish contact with the file server. Otherwise the File System Archiving task fails, and you may receive either of the following messages from DTrace or in a File System Archiving task report:
For details of the additional configuration tasks, see the following technical note on the Symantec Enterprise Support site:
http://www.symantec.com/docs/TECH76080.
The Install FSA Agent wizard fails to install the FSA Agent on the file server if the Administration Console installation path contains any double-byte characters.
To work around this issue, install the FSA Agent manually, as described in the Setting up File System Archiving manual.
Symantec Endpoint Protection (SEP) v11 intermittently recalls placeholders on the host server when file properties are viewed through a mapped drive on a different server.
In certain file system configurations, Enterprise Vault may fail to create placeholder shortcuts for files in an archiving target share, and the FSA archiving report contains the following message for each file in the share:
*** Error *** - There is duplicate of this item in the archive.
This can happen when the sub-folder of a volume share is also shared, but from a different location, and both shares are added as FSA archiving targets in the Enterprise Vault Administration Console. As the paths to the shares are different, FSA does not identify the target overlap and attempts to archive the files in the sub-folder twice.
For more information on this issue, see the following technical note on the Symantec Enterprise Support site:
http://www.symantec.com/docs/TECH75775
There is a known issue with Microsoft Office files and pass-through recall when a file server client is configured for offline working.
When the client synchronizes with the file server in preparation for offline working, placeholders remain on the file server as expected. However, when the client resynchronizes its edited offline files on reconnection, any Microsoft Office file that replaces a placeholder retains the placeholder's offline attribute.
Enterprise Vault therefore ignores these updated Microsoft Office files on subsequent archiving runs.
This issue does not affect EMC Celerra file servers.
The archiving policy option "Delete archived file when placeholder is deleted" can sometimes fail to take effect for a NetApp device. If the client application passes "read/write/append" access rights in addition to "delete" rights in its delete request, then the placeholder is deleted but the archived file is not deleted.
A problem can occur if you use the xcopy command to copy placeholders on a Windows file server that is configured for pass-through recall. The problem can occur if you run the xcopy command locally on the file server, and if the source and target folders are on the file server. The files are copied to the destination folder as expected, but some of the files are restored to the source folder, despite the pass-through recall setting.
If you synchronize folders for offline working on a Windows file server client that runs Windows 2003 or Windows XP, then offline Microsoft Word, PowerPoint or Excel files fail to open from their placeholders. A message may state that an error occurred when opening the file, or that the file cannot be accessed.
Microsoft has provided a hotfix for this issue for Windows XP-based clients. See the Microsoft Knowledge Base article When you use HSM software to manage files on a network, you cannot open a network-shared file that was created on a Windows XP-based computer when you work offline at http://support.microsoft.com/kb/936071.
A different problem occurs if you synchronize folders for offline working on a client that runs Windows Vista. If you open an offline Microsoft Word, PowerPoint or Excel file from its placeholder, you cannot save changes to the file except by saving the file with a new name. This issue is under investigation with Microsoft.
If you attempt to recall a file that is larger than 4 GB from an internet shortcut using Internet Explorer 7.0, the file is inaccessible. Enterprise Vault displays a message stating that files larger than 4 GB cannot be opened.
This is due to a limitation in Microsoft Internet Explorer. Note that placeholder shortcuts are not affected.
To work around the restriction you can restore the file by using the Copy to File System or Move to File System option in Archive Explorer.
Recall from internet shortcuts succeeds for all file sizes using Internet Explorer 8.0.
On a Windows 2008 file server file blocking custom commands can fail for no obvious reason. The problem occurs because the Windows task scheduler does not correctly parse quotation marks in a command line.
Install Microsoft hotfix KB951246 to fix this problem.
See http://support.microsoft.com/kb/951246 for more information and to obtain the hotfix.
On a Windows 2008 file server, programs that you run using the file blocking custom command cannot interact with the Windows desktop. This restriction is because of the Windows User Account Control (UAC).
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).
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 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
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.
The Administration Console displays FSA targets incorrectly if you add them using an IP address in the UNC path.
For example, when you create a target using \\192.168.10.10, the Administration Console displays the target as \\192.
Despite this, archiving against this target proceeds as normal. To avoid this issue, do not use IP addresses when you configure FSA targets.
Enterprise Vault Reporting supports English, Japanese, and Simplified Chinese only. If you configure the Enterprise Vault Reporting language as Chinese on a Traditional Chinese system, the reports may not display correctly or may display in Simplified Chinese. You should configure the language as English (US) on Traditional Chinese systems.
If you previously installed the Enterprise Vault 8.0 original release, the FSA Reporting Web service locations may be incorrect in the Directory database.
The locations are incorrect in the Directory database if either of the following applies:
The Enterprise Vault Directory database lists the same FSA Reporting Web service location multiple times, instead of listing multiple locations.
If you use, or intend to use, Enterprise Vault FSA Reporting, see the following technical note on the Symantec Enterprise Support site for details of how to correct the problem:
http://www.symantec.com/docs/TECH71384
In versions earlier than Enterprise Vault 9.0.4, Vault Cache database files could grow very large, causing slow Vault Cache performance for users. Although this issue has been fixed in Enterprise Vault 9.0.4, any existing large database files are not automatically resized.
Timeouts during uploading as part of Vault Cache synchronization can result in the same items being archived two or three times. There are cases where the upload results in the item being archived, but the upload still fails because of a timeout, for example when conversion times out.
In such cases, an error occurs and the upload of the item can be retried twice before the item is moved to the Could Not Archive folder in Virtual Vault. If the item is archived on each upload attempt, it can be archived up to three times before the Enterprise Vault Outlook Add-In stops trying to upload it.
This issue applies to Outlook 2003 and Outlook 2010. It affects the Outlook Add-In (not the HTTP-Only Outlook Add-In) when the Exchange desktop policy setting Shortcut Deletion on the Options tab is set to Ask User. When the user right-clicks a folder containing shortcuts and chooses the Delete option on the context menu, Enterprise Vault should always ask the user whether to delete the shortcuts only, or the shortcuts and the archived items.
However, if the focus is on a different folder when the user right-clicks, the correct prompt is not displayed. The following Outlook prompt is displayed instead:
Are you sure you want to delete the folder folder_name and move all of its contents into the Deleted Items folder?
This issue affects Outlook 2010 users, and not Outlook 2003/2007 users. It occurs when users are not allowed to copy Enterprise Vault shortcuts. That is, the Outlook advanced setting Allow shortcut copy in the Exchange desktop policy is set to its default value of Off. The expected behavior is that users are prevented from copying shortcuts, but they should still be able to move shortcuts.
The effect of this issue is that the Outlook Add-In incorrectly prevents users from moving a shortcut by dragging it to another folder. The reason is that Outlook performs this type of move as a cut and paste, which includes a copy.
Users can still move shortcuts with the Move option, which is on the Outlook Home tab and on the right-click menu.
Enterprise Vault Outlook Add-In functionality in Outlook 2010 is always HTTP-Only. There are some differences from the HTTP-Only functionality in Outlook 2003/2007, as follows:
If you select multiple items including some shortcuts and select Outlook Delete, the Outlook Add-In prompts you to delete the archived item and the shortcut, or the shortcut only. This prompt is expected behavior in all versions of Outlook, depending on the site and policy settings that control deletion of archived items and shortcuts.
In Outlook 2010, the Outlook Ignore Conversation option (Ctrl + Delete) moves the current and future items in a conversation to the Deleted Items folder. With Ignore Conversation, you do not get the prompt. Outlook moves shortcuts to the Deleted Items folder. The archived items remain in the archive. This behavior is currently outside the control of the Enterprise Vault Outlook Add-In.
On the Outlook 2010 Enterprise Vault tab, Outlook adds the following text to each tooltip:
Enterprise Vault Add-in. Press F1 for add-in help.
F1 actually launches Outlook help, not Enterprise Vault help as the user might expect. The Enterprise Vault Outlook Add-In cannot prevent this text from appearing.
Enterprise Vault 9.0.1 changed Virtual Vault so that the Could not archive and To archive search folders are visible only if the Exchange Desktop policy allows the user to archive items in Virtual Vault.
The following issues affect the display of the folders:
On Windows XP, if you upgrade the Enterprise Vault Outlook Add-Ins from Enterprise Vault 8.0 SP5 or earlier, folders may in some rare circumstances appear to be empty when viewed using offline Archive Explorer.
If this issue occurs, run the following command after upgrading to the Enterprise Vault 9.0.1 Outlook Add-Ins.
Note: You do not need to run the command unless the issue occurs.
%windir%\system32\regsvr32 %windir%\system32\msxml3.dll
When synchronization of an existing Vault Cache requires a content download, the Outlook Add-In sends a request to the Enterprise Vault server. If the size of the content download request exceeds the maximum request size allowed by the Enterprise Vault Web server (IIS), the results are as follows:
An error is written to the application log. The error includes the following text:
Exception: Maximum request length exceeded.
This issue may occur if the Outlook Add-In does not use preemptive caching. Preemptive caching reduces the need for content download. To ensure that preemptive caching is in use, check that the Vault Cache advanced setting Offline store required in the Exchange Desktop policy is set to its default value of Yes. Then check that the Outlook users who are affected by the issue are working in Cached Exchange Mode. If a user does not have an OST file, Enterprise Vault cannot perform preemptive caching.
The issue may occur for delegate and shared mailboxes, irrespective of the user's Cached Exchange Mode setting.
If preemptive caching is in use and the issue still occurs, you may be able to work around it by increasing the maximum request size.
On the Enterprise Vault server, open the Enterprise Vault Web application configuration file web.config in a text editor. The file is in the \WebApp subfolder of the Enterprise Vault program folder, typically C:\Program Files\Enterprise Vault\WebApp.
Find the line that reads:
<httpRuntime maxRequestLength="10000" />
(The value is in kilobytes, and 10000 is the default.)
Enter a new value for maxRequestLength. We recommend doubling the value to begin with, and increasing it further if the issue persists.
Save the file. You do not need to take any further action for the changed value to take effect.
Enterprise Vault administrators and Outlook users should be aware of the following limitations that apply after a Domino mail file has been migrated to an Exchange mailbox:
Virtual Vault may respond in different ways when users try to modify items.
If an item in Virtual Vault is marked as unread and a user tries to mark it as read, Virtual Vault does not display a warning message. The item correctly remains marked as unread.
If a user tries to modify other properties of an item, for example its Category or Follow Up flag, then where possible Virtual Vault immediately prevents the attempted modification and displays a warning message. However, in some cases, the way in which Outlook works means that Virtual Vault only detects a change and displays a warning message when the user tries to save the item.
This issue occurs after you upgrade Outlook Add-Ins to Enterprise Vault 9.0 or later from Enterprise Vault 8.0, 8.0 SP1, or 8.0 SP2. When a user already has Vault Cache enabled, Virtual Vault does not display the ampersand (&) character in folder names correctly.
The first Vault Cache synchronization following the upgrade corrects the folder names, and Virtual Vault displays the ampersands correctly.
Virtual Vault error or warning messages may differ between Outlook 2003 and Outlook 2007/2010, because these versions of Outlook process messages differently.
For example, when a user tries to move an Enterprise Vault shortcut into Virtual Vault in Outlook 2003, the following message is displayed:
Can't move the items. You don't have appropriate permission to perform this operation.
The same action in Outlook 2007/2010 results in the following message:
Cannot move the items. You cannot copy or move the selected item into Virtual Vault.
You have selected a type of item that your organization's archiving policy does not allow you to archive.
This issue only affects calendar items that were archived in any version of Enterprise Vault before Enterprise Vault 8.0 SP2. Virtual Vault displays these items in the Calendar view on the date when they were archived, rather than on the date of the actual appointment.
The issue occurs because Enterprise Vault did not store the calendar item start and end dates before Enterprise Vault 8.0 SP2. When a user opens the archived calendar item, the correct dates are shown in the open item.
Virtual Vault displays calendar items that were archived in Enterprise Vault 8.0 SP2 or later on the date of the appointment.
Certain embedded attachments may cause Virtual Vault to show the paperclip icon next to items when it should not be there.
This issue does not affect Enterprise Vault shortcuts in the mailbox.
Unread archived items appear as Read in Virtual Vault. The exact behavior depends on how the item was added to Virtual Vault:
When the Virtual Vault advanced setting Users can reorganize items in the Exchange Desktop policy is set to No, users can still use the Outlook option Run Rules Now to move items between folders in Virtual Vault. The setting should prevent users from moving items within Virtual Vault by any method.
This issue only applies to use of Run Rules Now. Setting Users can reorganize items to No correctly prevents users from moving items manually between folders, and prevents actions on folders.
The case described here is expected behavior, but is included here for information.
It occurs if the following conditions apply:
Vault Cache cannot now be enabled automatically for the user. To enable Vault Cache, the user must click the Enterprise Vault option Enable Vault Cache in Outlook.
When a user runs a rule on a Virtual Vault folder using Run Rules Now, the rule may try to move items from one Virtual Vault folder to another. If the Virtual Vault advanced setting Users can reorganize items in the Exchange Desktop policy is set to Yes, the rule can run successfully.
However, the behavior of the rule may change if Vault Cache header synchronization is running at the same time as the rule is run.
During Vault Cache header synchronization, the only modification allowed in the Virtual Vault is the addition of new items. This type of modification is possible if the Virtual Vault advanced setting Users can archive items in the Exchange Desktop policy is set to Yes. This setting allows normal rule processing from the mailbox into Virtual Vault, and user actions in Outlook, to add items during synchronization.
Virtual Vault prevents movement of items during a Vault Cache header synchronization. However, when Outlook is unsuccessful in moving the items, it may create copies of them in the destination folder. This result is not what the user expects.
To avoid duplication of items as a result of using Run Rules Now, we recommend that users do one of the following:
If the registry value PSTDisableGrow is enabled, you experience the following limitations in the use of Enterprise Vault:
This has been fixed but depends on the appropriate Microsoft hotfix (for Outlook 2003/2007) and further configuration (for Outlook 2003/2007/2010). For more information, see the section "Overriding PSTDisableGrow" in Setting up Exchange Server Archiving.
The Enterprise Vault Integrated Search feature does not return any results if the search term that you enter contains both double-byte characters and one or more question mark (?) wildcard characters. This issue arises because of the way that the Indexing service treats double-byte characters (as words rather than individual characters), and the requirement to enter at least three characters of the search term before you use a ? wildcard.
The issue does not arise when you use the asterisk (*) wildcard character in a search term that contains double-byte characters.
If there have been no items archived from a newly-created mailbox, Archive Explorer shows the mailbox name but 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.
You may experience the following issues when you use the Enterprise Vault Client for Mac OS X with Entourage 2004 or Entourage 2008:
When the body or subject line of an Enterprise Vault shortcut contains certain Japanese characters, an Entourage user who chooses to view or reply to the original item may receive an error message. You may be able to resolve this issue by doing one or both of the following on the Enterprise Vault server:
In Exchange Server 2003 environments, nothing happens when Entourage users try manually to archive mail items that have Japanese characters in their subject lines. However, these items can be archived without problem in Exchange Server 2007 environments or whenever background archiving occurs.
Users who encounter this issue can work around it by emptying their mailbox folder caches before they undertake manual archiving. For instructions on how to do this, see the Entourage documentation. After users have synchronized the items in their mailbox folders with the Exchange server, they can manually archive any items that this issue affects.
Symantec is working with Microsoft to resolve this issue. For more information, see the following article on the Symantec Web site:
http://www.symantec.com/docs/TECH72156 [Ref E1702806]
The following additional issues may affect users of Entourage 2008 Web Services Edition as well as users of Entourage 2004 and Entourage 2008:
.rge) files into Enterprise Vault archives.If an Entourage mailbox folder contains a shortcut to a non-mail item, such as a Word document or Excel spreadsheet, the following error message appears when you try to perform any Enterprise Vault operation on the shortcut:
Error in download... Operation could not be completed
This issue typically arises when an Entourage mailbox contains shortcuts to items that Enterprise Vault originally archived from Outlook. Unlike Entourage, Outlook permits users to drag and drop non-mail items into a mailbox folder. [Ref E1723146]
Users of some mobile devices have to scroll across the browser page to see the input fields on the Mobile Search Log On and Search pages.
You cannot use the column width settings in the Mobile Search configuration file Web.Config to work around this issue, because these settings only affect the search results display.
In previous releases, the WDS integration included the option to add a search button to the WDS user interface so that users could search their online archive. The addition of the button was controlled by the Advanced Exchange Mailbox Policy setting, WDS integration, which was listed in the advanced Outlook settings. The button's label could be set using WDS button and menu name in the same location. In addition, an archive search option could be added to the MSN toolbar using the policy setting, WDS search application.
As a result of a design change by Microsoft, WDS 3.x and WS do not support this integration with Enterprise Vault, and so these options are no longer available.
WDS and WS do not index password protected files in a user's Vault Cache.
WDS and WS do not find media files, for example .jpg, .bmp and .mp3 files, in a Vault Cache on Windows 2003 and Windows XP.
Searching works correctly on Windows Vista.
It is possible for WDS and WS to show duplicate search results in either of the following circumstances:
If you select Vault Cache instead of All Locations, WDS fails to find attachments by file name unless you enclose the file name in quotation marks. For example, WDS finds
"test.doc" but not test.doc. Searches with wildcard characters, for example t*.doc, work as expected.
This is a known issue with WDS 3.x which is fixed in WS 4.0.
When you upgrade an Enterprise Vault 9.0 server from the 64-bit edition of Windows Server 2003 to Windows Server 2008 R2, the path to Enterprise Vault license files changes. Before the upgrade, Enterprise Vault places installed license files in:
C:\Program Files (x86)\Common Files\Symantec Shared\Licenses
Following the upgrade, Enterprise Vault expects to find installed license files in:
C:\ProgramData\Symantec Shared\Licenses
Enterprise Vault cannot find installed licenses in this location and the Administration Console displays the following error:
Required license not installed
To correct this issue, you must reinstall the license files:
Copy the installed license files (*.slf) from their existing location to the Enterprise Vault folder, for example C:\Program Files (x86)\Enterprise Vault.
When you run Enterprise Vault in a pure IPv6 environment, you cannot use Symantec Backup Exec to migrate collection files to secondary storage.
Enterprise Vault fails to archive an item to a WORM storage device if both of the following conditions apply:
The following message appears for each affected item in the archiving task report:
*** Error *** - Catastrophic failure (Exception from
HRESULT: 0x8000FFFF (E_UNEXPECTED))
If you use Outlook 2007 on a busy Enterprise Vault server, it is possible to exceed the size of the Outlook 2007 credential cache. Various errors may be logged as a result, including errors in the following event categories:
The current workaround to this problem is to do one of the following:
Symantec will address this problem further in a future release.
The following error message may appear in the EVSVR log file when you process a large amount of data with the EVSVR Repair operation DatabaseReferences:
**** EVSVR ERROR: Failed to process Partition '<partition_name>': Error: The system cannot find the file specified. [0x80070002]
This error message indicates that processing ended prematurely. However, the data that EVSVR repaired before the error arose was correctly repaired.
To complete the processing of all the data, follow the steps below for each partition that EVSVR failed to process:
EVSVR> prompt, type start to begin processing.You may need to repeat this procedure several times if you have a very large partition.
When multiple users are updating the Vault Cache, you may see the following warning in the Event log on the Storage service server:
Event Type: Warning Event Source: ASP.NET 2.0.50727.0 Event Category: Web Event Event ID: 1309 Date: 26/06/2009 Time: 09:46:52 User: N/A Computer: DEMO Description: Event code: 3001 Event message: The request has been aborted.
The warning is an indication that there were insufficient simultaneous download slots available to update the Vault Caches.
If this event occurs only occasionally, you can safely ignore it. The downloads are retried automatically.
If this event occurs frequently, do one of the following to increase the number of download slots:
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\Admin
Make sure that the value you specify is larger than is set for Maximum number of concurrent updates in the Administration Console properties of the Storage server.
After a Vault Cache is enabled, Enterprise Vault creates a number of registry values under the following key:
HKEY_CURRENT_USER
\Software
\KVS
\Enterprise Vault
\Client
\VaultCacheStoreID
If you reset the Vault Cache, Enterprise Vault deletes these registry values and discards any changes that you have made. For example, if you previously set the options Maximum disk space to use and Start checking after in the Vault Cache properties, you must set the options again after you perform the reset.
This issue may affect any Enterprise Vault application that uses Internet Explorer to access the Enterprise Vault server.
Internet Explorer displays a message saying that the Enterprise Vault service is not available. The exact wording of the message may vary, depending on the application.
The issue occurs only if all of the following conditions apply:
The applications that the issue may affect include:
If this issue occurs, you can avoid it in one of the following ways:
Enterprise Vault uses a trigger file mechanism to determine whether the files in vault store partitions have been backed up. For more information, see the Administrator's Guide.
Whether you use an XML trigger file, or a text trigger file, Enterprise Vault must be allowed to rename the file with the extension OLD during processing.
On WORM devices, you must ensure that the trigger file is not created as a read-only file, or subsequently set to read-only. When this happens, Enterprise Vault cannot rename the file.
If you migrate archived data to secondary storage using a migrator other than the Enterprise Vault migrator, the following actions can result in the temporary recall of large numbers of migrated CAB files:
The recalled files occupy a large amount of partition space, and can potentially cause a partition to become full.
Enterprise Vault deletes these temporary files according to the setting "Recalled file cache period" on the Advanced tab of the partition properties. This setting has a default value of 7 days.
Before you perform any of the actions indicated above, ensure that there is sufficient free space on the device on which the related Enterprise Vault partitions are located. To reduce the time that Enterprise Vault retains the recalled files, you can reduce the value of the "Recalled file cache period" setting.
The collection process performs the deletion of the recalled files when the recalled file cache period has elapsed. You can trigger the collection process manually by using the "Run Now" option on the Collections tab of the partition properties.
Note that this issue does not arise if you use the Enterprise Vault migrator.
When you add an Indexing Service or a Task Controller Service to Enterprise Vault running on Windows Server 2008, you must then restart the Enterprise Vault Admin service.
Whether you add and configure these services during installation, or subsequently add them in the Administration Console, they fail when they are run for the first time.
You must restart the Enterprise Vault Admin service to rectify this situation.
If you do not use the Getting Started wizard to set up archiving, you must set up the data locations for the Indexing service manually.
To define the data locations for the Indexing service:
You must use the Administration Console to specify a new password for the Vault Service account or to change the Vault Service account itself. You cannot use the Windows Services applet to edit the Log On details of an Enterprise Vault service.
The account that is used to configure Monitoring (database) must have the following rights on the SQL Server where the Enterprise Vault Monitoring database will be created:
sysjobs
sysjobservers
sysjobschedules
sysjobsteps
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).
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://www.symantec.com/docs/TECH52247.
A search on a text field that contains certain Hong Kong Supplementary Character Set (HKSCS) characters may not return the correct results. Not all HKSCS characters cause this issue to occur.
Also, a message that uses the HKSCS is archived correctly and a shortcut to it is correct. However, when the item is found by Browser Search, Integrated Search, or Archive Explorer, the summary text is shown as a series of question marks (?? ?? ?? ??).
Users may still be able to delete mailbox folders, even after you set the NonDeletable option with Enterprise Vault Policy Manager (EVPM) to prevent their deletion. For more information on this issue, see the following technical notes on the Symantec Enterprise Support site:
The Enterprise Vault 9.0.4 administration documentation is available in English, Japanese, and Simplified Chinese from the following locations:
Symantec Enterprise Vault 9.0.4\Documentation folder
on the Enterprise Vault media.The following table lists the documents in the documentation set.
| Document | Comments |
|---|---|
| Enterprise Vault Help | Includes all the following documentation so that you can search across all files. You can access the help from the Start menu (click Start > Programs > Enterprise Vault > Documentation) or from within the Administration Console (click Help > Help on Enterprise Vault). |
| Introduction and Planning | Provides an overview of Enterprise Vault functionality. |
| Deployment Scanner | Describes how to check the prerequisite software and settings before you install Enterprise Vault. |
| Installing and Configuring | Provides detailed information on setting up Enterprise Vault. |
| Upgrading to Enterprise Vault 9.0.4 | Describes how to upgrade an existing Enterprise Vault installation to the latest version. |
| Setting up Exchange Server Archiving | Describes how to archive items from Microsoft Exchange user mailboxes, journal mailboxes, and public folders. |
| Setting up Domino Server Archiving | Describes how to archive items from Domino mail files and journal databases. |
| Setting up File System Archiving | Describes how to archive files that are held on network file servers. |
| Setting up SharePoint Server Archiving | Describes how to archive content from Microsoft SharePoint servers. |
| Setting up SMTP Archiving | Describes how to archive SMTP messages from other messaging servers. |
| Administrator's Guide | Describes how to perform day-to-day administration, backup, and recovery procedures. |
| Reporting | Describes how to implement Enterprise Vault Reporting, which provides reports on the status of Enterprise Vault servers, archives, and archived items. If you configure FSA Reporting, additional reports are available for file servers and their volumes. |
| Utilities | Describes Enterprise Vault tools and utilities. |
| Registry Values | A reference document that lists the registry values with which you can modify many aspects of Enterprise Vault behavior. |
| Help for Administration Console | The online Help for the Enterprise Vault Administration Console. |
| Help for Enterprise Vault Operations Manager | The online Help for Enterprise Vault Operations Manager. |
The document Upgrading to Enterprise Vault 9.0.4 is provided
in both .CHM and .PDF formats on the Enterprise Vault media, in the folder
Symantec Enterprise Vault 9.0.4.
The following guides for end users are provided in .PDF format on the Enterprise
Vault media, in the folder Symantec Enterprise Vault 9.0.4\Documentation\language\Client
User Guides:
Most of the information in the Enterprise Vault administration manuals is also available online as articles on the Symantec Enterprise Support site. You can access these articles by searching the Internet with any popular search engine, such as Google, or by following the procedure below.
To access the "How To" articles on the Symantec Enterprise Support site
The Enterprise Vault Tech Center (http://go.symantec.com/education_evtc) provides free, publicly available training modules for Enterprise Vault. Modules are added regularly and currently include the following:
More advanced instructor-led training, virtual training, and on-demand classes are also available. For information about them, see http://go.symantec.com/education_enterprisevault.
Copyright © 2012 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Veritas, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator 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.
This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (“Third Party Programs”). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Software file accompanying this Symantec product for more information on the Third Party Programs.
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
350 Ellis Street
Mountain View, CA 94043