Last updated: 26-Mar-2012
|
To download the latest version of this document and the other Enterprise Vault release notes, and to obtain Japanese and Chinese versions of these documents, see: http://www.symantec.com/docs/TECH140373. For the latest news about this release, including any hotfixes, subscribe to http://www.symantec.com/docs/TECH140371. |
This document describes the changes introduced in Enterprise Vault 9.0.1 (service pack 1 for Enterprise Vault 9.0).
Before installing or upgrading to Enterprise Vault 9.0.1 you must read this document and also the ReadMeFirst for Enterprise Vault 9.0. The ReadMeFirst lists current known issues and describes new features in the original release of Enterprise Vault 9.0.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
Enterprise Vault 9.0.1 provides the following new features:
Enterprise Vault 9.0.1 supports Outlook 2010 on end users' computers. Outlook 2010 requires the Enterprise Vault HTTP-Only Outlook Add-In. There are some differences between HTTP-Only Outlook Add-In behavior in Outlook 2010 and in Outlook 2003/2007. The differences are described in the section HTTP-Only Outlook Add-In functionality in Outlook 2010 under "Enterprise Vault Outlook Add-Ins issues" in the ReadMeFirst for Enterprise Vault 9.0.
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.1 Outlook Add-In on Outlook 2003/2007 and later upgrade to Outlook 2010, you must then install the Enterprise Vault 9.0.1 HTTP-Only Outlook Add-In.
In Outlook 2010, the same Enterprise Vault options are available as in Outlook 2003/2007, but they have new icons and are in new locations.
The main Enterprise Vault features that a user sees in Outlook 2010 are as follows.
For information about how to control the availability and location of Enterprise Vault options, see the Enterprise Vault 9.0.1 Administration Console Help for the Exchange Desktop Policy: Options tab.
Enterprise Vault 9.0.1 supports Outlook 2010 conversation view. If an archived item exists in a Virtual Vault and also as a mailbox shortcut, Outlook controls whether the Virtual Vault item or the shortcut is shown in a conversation. The item that is shown depends on the folder in which the user views the conversation.
Enterprise Vault 9.0.1 includes a new command-line utility that enables you to manage the Enterprise Vault shortcuts that are in SharePoint. The new utility is EVSPShortcutManager.
You can use EVSPShortcutManager to replace HTML shortcuts with new shortcuts that behave exactly like SharePoint documents. The new shortcuts use the same icons as the corresponding original documents.
See the Utilities manual for details of EVSPShortcutManager.
Note that the Utilities manual does not describe the required permissions correctly.
For the correct permissions, see Permissions required for EVSPShortcutManager in the ReadMeFirst.
Four new alerts have been added to system status container in the Administration Console, as follows:
| Alert |
Threshold |
Frequency |
|---|---|---|
| Days since Exchange Journal
mailbox scanned for new items |
1 day |
Daily |
| Days since items archived from
Exchange Journal mailbox |
1 day |
Daily |
| Days since Exchange mailboxes
scanned for new items |
2 days |
Daily |
| Days since items archived from
Exchange mailboxes |
7 days |
Daily |
You may want to change the default thresholds and frequencies to match your own policies. To make changes, start the Administration Console and go to the Monitoring tab of Site Properties.
The Enterprise Vault SCOM management package is now provided as a sealed binary file. The file was sealed with the Symantec Enterprise Vault certificate.
See the Upgrade Instructions for details of how to apply the package.
In order to obtain the changes described in this section the Enterprise Vault 9.0.1 Outlook Add-ins must be installed.
In some circumstances, when you used the Outlook Calendar Overlay option to view items in the Virtual Vault calendar and items in the mailbox calendar, the Virtual Vault items were not visible.
If this issue occurred and the item was only in Virtual Vault, the appointment space was empty. If the Virtual Vault item had a corresponding mailbox item, only the mailbox item was shown.
This has been fixed.
Outlook contacts, calendar items, and tasks that had been archived and restored could not be archived again.
This has been fixed.
#%%%# within Virtual Vault caused Outlook to stop responding [Ref 9015376, E2146209]This issue occurred if a folder in Virtual Vault had a name that consisted of two hash (#) characters enclosing one or more percent (%) characters; for example, #%%%#. If you tried to copy the folder within Virtual Vault, the attempt caused Outlook to stop responding.
This has been fixed.
In rare circumstances the Enterprise Vault Add-Ins could cause Outlook to terminate unexpectedly.
This has been fixed.
The Enterprise Vault Outlook Add-In now adds a random element to the interval after which an unsuccessful scheduled Vault Cache synchronization is retried. In previous Enterprise Vault versions, the retry interval was fixed at 300 seconds (five minutes).
The random element is in the range one second to 300 seconds. So each retry is now performed after an interval that is between 301 seconds and 600 seconds.
This change means that when a number of users' scheduled Vault Cache synchronization requests occur simultaneously and are rejected, the requests are not retried simultaneously.
As in previous Enterprise Vault versions, the Vault Cache synchronization retry mechanism is invisible to users.
On Windows XP, if you upgraded the Enterprise Vault Outlook Add-Ins from Enterprise Vault 8.0 SP5 or earlier, folders could appear to be empty when viewed using offline Archive Explorer.
This issue is now very unlikely to occur. If you encounter this issue, see the section Offline Archive Explorer may not display contents of folders under "Enterprise Vault Outlook Add-Ins issues" in the ReadMeFirst for Enterprise Vault 9.0 for a solution.
In Enterprise Vault versions before 9.0.1, the search folders Could not archive and To archive were always visible in a Virtual Vault.
In Enterprise Vault 9.0.1, the folders are visible only if the Exchange Desktop policy allows the user to archive items in Virtual Vault, which depends on the Virtual Vault advanced setting Users can archive items.
If archiving is enabled and later disabled, then the Outlook Add-In hides the folders unless they contain results. If the folders contain results, the Outlook Add-In checks them at each Vault Cache synchronization and hides them when they are empty.
This section describes changes made since the October 2010 release of the Enterprise Vault Add-In for Outlook 2010. These changes are not relevant to any other previous release.
The October 2010 release of the Enterprise Vault Add-In for Outlook 2010 was supported in English only.
Enterprise Vault 9.0.1 supports the HTTP-Only Outlook Add-In in all the Enterprise Vault end user languages, with Outlook 2010 as well as Outlook 2003/2007.
This issue could occur when the Enterprise Vault Add-In for Outlook 2010 had been installed but Outlook 2010 did not have a connection to Exchange. There could be a delay, typically of 60 to 90 seconds, while Outlook added the Enterprise Vault Add-In.
This has been fixed.
The changes described in this section are obtained as a result of upgrading Enterprise Vault server software and so do not require the updated Enterprise Vault 9.0.1 Outlook Add-ins.
The Exchange desktop policy's Shortcut Deletion option controls the deletion of shortcuts in users' mailboxes, and the associated items in the archives. When this option was set to Both deleted or Ask User, and users deleted pending items from their mailboxes, Enterprise Vault's Outlook Add-Ins handled items pending deletion and restore differently from items pending archive.
On deletion of an item pending deletion or restore, Outlook Add-Ins treated the item as a shortcut and deleted both the pending item from the mailbox and any associated item from the archive.
On deletion of an item pending archive, Outlook Add-Ins allowed Outlook to delete the item from the mailbox.
Outlook Add-Ins now ignore all deletions of pending items from users' mailboxes, and the deletions are handled only by Outlook. Outlook Add-Ins do not delete any associated items from archives.
If an Outlook Add-In user used a shortcut to restore an item that was in a corrupt archive file, the restoration failed and the shortcut was deleted.
This has been fixed. If an item cannot be restored the shortcut is not deleted.
It was not possible to forward some archived items from Virtual Vault. The items had been migrated by third-party tools from Domino to Exchange Server and had then been archived from Exchange Server.
This has been fixed.
In OWA 2007, you could not view, reply to, or forward archived items that were encrypted or signed. When you attempted to open the shortcut to one of these items, the following warning was displayed:
The content cannot be displayed because the S/MIME control is not available. You may install the control by going to Email Security options page in the main window.
However, enabling the S/MIME control did not resolve the issue.
This has been fixed.
In some circumstances, users could not retrieve Domino 8.0 items from their archives. This happened in the following circumstances:
At this point, Lotus Notes displayed the following error:
The linked document cannot be found in the view
This has been fixed.
Lotus Notes users who tried to set a follow-up flag on shortcuts in their mail files saw the following error:
Object variable not set
This has been fixed.
When an iNotes user viewed an archived item that contained an embedded image, the image may not have been shown correctly, as follows:
This has been fixed.
Users could not log in to the Enterprise Vault client for Mac OS X if the Exchange server for their Entourage account had the Autodiscover service turned off. The Autodiscover service is turned on by default on Exchange 2007 and Exchange 2010 CAS servers.
This has been fixed.
If the email address that you specified in your Entourage account settings was not your primary SMTP address, you could not log in to the Enterprise Vault Client for Mac OS X.
This has been fixed.
If a user name in the Mailbox field in the Archive Explorer Settings dialog box contained an underscore (_) character, this issue occurred after the following actions:
The commands incorrectly remained disabled, even though the default setting applied.
This has been fixed.
The first time a user tried to use Archive Explorer to restore an item to a mailbox the restoration failed with the following error:
Failed to copy item Reason :- Creation of the basket by the Shopping Service failed. Ask the Enterprise Vault Administrator to check the Shopping Service configuration.
The failure affected only users who had never restored an item to a mailbox before, so an individual user never saw this problem more than once.
This has been fixed.
Changes introduced in Exchange Server 2010 prevented Enterprise Vault from accessing information about hidden Exchange 2010 mailboxes. This had the following effects:
This has been fixed, and Enterprise Vault handles hidden Exchange 2010 mailboxes the same as those in earlier versions of Exchange with one limitation. Custom filtering does not match recipients in distribution lists that are hidden from the address book.
The Exchange public folder policy's two Lock options (Archiving Actions tab) were ignored by Enterprise Vault. Even when these locks were cleared, users were unable to change the associated Delete original item after archiving and Create shortcut to archived item after archiving options in Outlook.
This has been fixed.
It was possible for some items imported from a PST to be archived but not to show the Enterprise Vault shortcut icons.
The PST import generated the following event log entry:
Event Type: Error Event Source: Enterprise Vault Event Category: Migrator Server Event ID: 6469 Description: An exception has occurred. [Internal reference CMigrator/PI/e]
This problem appeared in the following circumstances:
This has been fixed.
When the 'Name' field in the properties of a PST file was blank, importing from that PST could product a series of mail folders with names such as PST35_1.db, PST35_2.db, and so on.
This has been fixed. If the 'Name' field is blank, Enterprise Vault creates a folder name from the original PST file name.
The underlying functionality of Domino item retrieval has been changed.
Previously, when a user retrieved a Domino item from the archive, Enterprise Vault retrieved it to a temporary database on the Enterprise Vault Domino Gateway.
Enterprise Vault now retrieves Domino items to users' mail files.
Note that Enterprise Vault always retrieves items to users' mail files on the server, and not to users' local replicas. This might cause a discernible change to resource utilization patterns on the Domino servers.
Domino custom filtering rules with the action MARK_DO_NOT_ARCHIVE left matching items unencrypted in the journal mailbox.
This has been fixed.
When running the NSF migrator wizard on a 64-bit system, the wizard stopped working after you selected the NSF file that you wanted to migrate to Enterprise Vault. A Windows error was displayed.
This has been fixed.
A Notes user who tried to restore an archived calendar or task item received the error message 'Please select at least one archived message and try again'.
This has been fixed. It is now possible to restore archived calendar and task items.
When a user tried to restore an item to an over-quota mail file, Lotus Notes displayed the following error:
Notes error: Unknown OS error
This has been fixed and Lotus Notes now displays the following error:
Notes error: Unable to write to database because database would exceed its disk quota
When custom filtering was configured for Domino journaling, addresses for mail-in databases that were included in distribution lists were not recognized. If a filter rule included the <DL> tag, and the specified distribution list included the address of a mail-in database, then the rule action was not applied to messages sent to the mail-in database.
This has been fixed.
In Exchange mailbox policies configured to archive based on age and quota, it was possible to clear the Delete original item after archiving option (Archiving Actions tab).
This option is required for Exchange mailbox policies configured to archive based on age and quota, and clearing the option in the Administration Console had no effect.
This has been fixed and it is no longer possible to clear the Delete original item after archiving option on any Exchange mailbox policies configured to archive based on age and quota.
During upgrade, this option is set automatically on all Exchange mailbox policies configured to archive based on age and quota.
It was not possible to use the following syntax to set Domino organization-level wildcard permissions on archives:
*/myorg
The workaround was to use the following longer format to set wildcard permissions:
*/O=myorg
This has been fixed.
In the Administration Console it was not possible to select the 'Restoring and Retrieval issues' trace.
This has been fixed.
You can now create vault store partitions on iTernity Compliant Archive Solution devices. Enterprise Vault supports WORM volumes only, and accesses the device using CIFS protocol.
For essential information about using iTernity Compliant Archive Solution with Enterprise Vault, see the following page on the iTernity Web site: http://www.iternity.com/faq-details/items/how-do-i-configure-ifsg-when-integrating-symantec-enterprise-vault-version-80.html
For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts: http://entsupport.symantec.com/docs/276547
In some circumstances, the retrieval of file items directly archived into mailbox archives created by older versions of Enterprise Vault could fail.
This has been fixed.
The New Partitions wizard now includes EMC Celerra Unified Storage Platforms in the list of supported devices.
A problem could occur if Enterprise Vault single instance storage applied fingerprints to an item which it subsequently failed to store. In some circumstances this condition resulted in orphaned fingerprints that were incorrectly left in the fingerprint database.
When this issue occurred, an error including the text in the following example was written to the event log:
Event ID: 13360 Description: An error was detected while accessing the Vault Database ... Violation of PRIMARY KEY constraint 'PK_MemberTable_nnn'. Cannot insert duplicate key in object 'dbo.MemberTable_nnn'. SQL Command: uspi_10Fingerprints
This issue did not result in any data loss.
This has been fixed.
In some rare circumstances, users could not restore certain archived emails. They could open these emails, and they could restore other emails in the mailbox.
This has been fixed.
The location for temporary collection files for an EMC Centera partition could continue to fill up during archiving. This problem was due to inefficient SQL queries to the JournalArchive table in the vault store database.
This has been fixed. Modifications to the design of the JournalArchive table have greatly improved the query performance.
On upgrade to Enterprise Vault 9.0.1, Enterprise Vault updates the JournalArchive table of each vault store database. This contributes to the upgrade time for each vault store database, depending on JournalArchive table size. For more information, see the Upgrading to Enterprise Vault 9.0.1 document.
In certain circumstances, the Storage service failed when partitions were hosted on a Centera device that was configured without a replica. This happened when the vault stores to which the partitions belonged were configured to remove safety copies immediately after archiving.
When the Storage service tried to connect to a non-existent replica, error messages with the event ID 6759 were repeatedly reported in the event log.
This has been fixed.
The format of internet shortcut file names has changed.
Enterprise Vault now appends the .url suffix to the file's original suffix, instead of replacing the
original suffix. The new format
lets you identify the original file type from the internet shortcut name.
The following table gives examples of internet shortcut names before and after the format change.
| File name | Previous shortcut name | New shortcut name |
|---|---|---|
document1.docx |
document1.url |
document1.docx.url |
graphic.gif |
graphic.url |
graphic.gif.url |
file.txt |
file.url |
file.txt.url |
If you upgrade to Enterprise Vault 9.0.1, internet shortcuts that are created after the upgrade use the new name format.
Note that if you choose the Windows Explorer option "Hide known
file types", Windows displays the original file types for the new format internet shortcuts.
For example, the internet shortcut document1.docx.url appears as document1.docx.
The FSA Agent failed to install on a Windows Server 2008 read-only domain controller (RODC) with the following error:
Unable to add the user 'USERACCOUNT' to the local 'Administrators' group
on computer 'COMPUTERNAME'. The function failed with error 50
This problem occurred with both an installation from the Administration Console, or when running the MSI file locally on the file server. The problem occurred because the read-only status of an RODC prevents the installation from making the local changes for the user account.
To install the FSA Agent on a domain controller the following conditions are required:
These privileges must be set on the primary domain controller operations master.
If you perform the FSA Agent installation from the Administration Console, Enterprise Vault is able to set these privileges for the Vault Service account, provided that the account is a local administrator. For a local installation using the MSI file, you must grant these privileges before the installation can succeed.
Enterprise Vault's FSA Agent installation error handling has now been enhanced to provide more useful dialogs and error messages if the installation is unable to make local changes:
Under certain circumstances FSA allocated the same saveset ID to two or more files. The result was that the data for some of the files was lost. On placeholder recall, all of the related placeholders recalled just one of the files.
The problem could occur when all of the following conditions applied:
_ % [ ] ^ (underscore, percent symbol, square brackets,
or circumflex accent)
For example, the problem occurred with the following pairs of files:
| file a | file b | Notes |
|---|---|---|
abc-1.txt |
abc_1.txt |
The hyphen in file a could instead be any single character, for example d, or 9. |
abcnnn1.txt
|
abc%1.txt |
nnn in file a is any number of characters. |
abcn.txt |
abc[123].txt |
n in file a is any one of the characters
that is enclosed by square brackets in file b (1, 2, or 3, in
this example). |
abcn.txt |
abc[^123].txt |
n in file a is any one character that is not enclosed by square brackets in file b
(for example, 4 or y). |
This has been fixed.
A number of changes have been made to the FSAUtility placeholder migration
(-pm) option, to prevent some conditions that can result in unsuccessful migrations.
FSAUtility does not proceed with a placeholder migration and quits with an explanatory message unless it can confirm that the following conditions are met:
The utility now records in the Enterprise Vault event log the start and the completion of a migration. The completion message indicates whether the migration was successful.
If you attempt to repeat a failed migration, the utility indicates that a migration previously failed, and asks if you want to continue. Note that If a migration fails you should not archive from the destination folder. Retry the placeholder migration to see whether it can complete successfully.
For more information, see the updated description of the FSAUtility placeholder migration option in the Utilities guide.
An FSAUtility -b operation to recall items had a handle leak if
the recall was to an EMC Celerra device. The handle leak could cause performance
problems.
This has been fixed.
File Blocking's file content checking failed to recognize and block some MP3, MOV, and WMV media files if the file type extension was renamed.
This has been fixed.
File Blocking could stop unexpectedly if either of the following applied:
This has been fixed.
If you enabled File Blocking for media files, Enterprise Vault also blocked JPEG files.
This has been fixed.
Archived Outlook .MSG files sometimes failed to recall successfully from their placeholder shortcuts.
This has been fixed.
On Chinese and Japanese Enterprise Vault systems, the FSA New Folder wizard failed with the following error if you used an unedited copy of the Default FSA Volume Policy:
Failed to update the details for this folder in Directory Services. Access is denied.
This has been fixed.
In some circumstances, it was not possible to restore an archived version from SharePoint's version history.
This has been fixed.
In certain circumstances the footer of FSA Reporting's Summary reports displayed the text #Error, even though there was no error.
This has been fixed.
The following operation reports failed to run successfully on a 64-bit version of Microsoft SQL Server Reporting Services:
The reports displayed the message "An error occurred during report processing".
This has been fixed.
In some circumstances, in Enterprise Vault environments with more than one SQL server and no mixed collations, the Deployment Scanner's SQL collation test failed with the following connectivity error:
Unable to connect to at least one of the SQL servers listed. <SQL Server>: Database: EnterpriseVaultMonitoring - no mixed collations found.
This has been fixed.
The Deployment Scanner report now provides a warning for local disks that have less than 1 GB of free space.
Index repair operations failed after the IndexCheck tool was run. Index repair operations generated entries such as the following in the event log:
Event Type: Warning Event Source: Enterprise Vault Event Category: Index Server Event ID: 7309 Description: The sequence number read from the failed items log does not correspond to the Saveset ID specified in the file. The item will not be repaired.
This has been fixed. The IndexCheck tool has been corrected. If you have seen this problem, run the IndexCheck tool on the out-of-date indexes again and then index repairs will work.
This release includes Outside In® Technology version 8.3.5 content converters from Oracle® Corporation.
Improvements to authentication performance and SQL Server resource utilization have resulted in the following:
in some circumstances, after an upgrade from Enterprise Vault 2007 to Enterprise Vault 8.0 and then to Enterprise Vault 9.0, it was possible to receive event log errors from Storage File Watch. The errors relate to items that had not been fully processed before the upgrade to Enterprise Vault 8.0.
This has been fixed. The items' processing is now completed in Enterprise Vault 9.0.1.
In certain circumstances, the number of file types associated with archived items exceeded the maximum number of entries in the file specification table in the Enterprise Vault directory database. When this happened, archiving failed and Event ID 13345 and 13360 error messages were reported in the event log during an archiving run.
This issue occurred in the following situations:
File extension management has been enhanced. Enterprise Vault now normalizes file extensions where possible, to reduce the number of additional entries created in the file specification table.
This issue occurred in the following configuration:
overridearchivelocks=true.
Behavior has now been changed. If the default options are configured on the Moved Items tab of the Exchange Mailbox policy, and the destination folder was created with the Policy Manager [Folder] option, overridearchivelocks=true, then the following action is taken:
Note that when a folder is moved into another folder, only the items with shortcuts have their retention category updated.
When a message with an HTML body part was archived and retrieved using the Enterprise Vault Content Management API, the HTML body part was sometimes missing. This issue occurred if the message was archived using the Symantec Backup Exec Archiving Option (BEAO), and Outlook 2007 SP2 with security update KB980376 or KB2288953 was installed on the Enterprise Vault server.
This has been fixed.
Copyright © 2010 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