Last updated: 21-Jan-2013
|
The latest version of this document and the other Enterprise Vault release notes are available from the Symantec Enterprise Support site in the following languages: For the latest news about this release, including any hotfixes, subscribe to http://www.symantec.com/docs/TECH193299. IMPORTANT: Enterprise Vault 10.0.3 introduces support for Exchange Server 2013. Before you archive from Exchange 2013, you must apply a hotfix to Enterprise Vault 10.0.3. The hotfix is available at http://www.symantec.com/docs/TECH201489. |
This document describes the changes introduced in Enterprise Vault 10.0.3 (service pack 3 for Enterprise Vault 10.0).
Before installing or upgrading to Enterprise Vault 10.0.3, you must read this document and also the ReadMeFirst for Enterprise Vault 10.0. The ReadMeFirst lists current known issues and describes new features in the original release of Enterprise Vault 10.0.
For changes introduced to Enterprise Vault 10.0 by earlier service packs, see the Previous Updates document.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
Enterprise Vault 10.0.3 provides the following new features:
Enterprise Vault 10.0.3 introduces support for Exchange Server 2013, including:
For the latest information on the minimum requirements for Exchange 2013 archiving, including the supported versions of Outlook on the Enterprise Vault server, see the Enterprise Vault Compatibility Charts at: http://www.symantec.com/docs/TECH38537.
For more information about Exchange 2013 archiving, including details of a mandatory hotfix for Enterprise Vault 10.0.3, see the following article on the Symantec Enterprise Support site:
http://www.symantec.com/docs/HOWTO82293.
The Enterprise Vault Outlook Add-In that is included with this release supports Outlook 2013 (32-bit and 64-bit) as well as earlier versions of Outlook.
In Outlook Web App (OWA) 2013, a new Enterprise Vault Office Mail App provides access to archived items. You can also enable the Office Mail App for Outlook 2013 users, as an alternative to the Outlook Add-In or in addition to it. Depending on how you configure the Office Mail App, it can make the following Enterprise Vault functions available to users:
For more information on the Office Mail App, see the Setting up Exchange Server Archiving guide.
Enterprise Vault now supports archiving from SharePoint 2013. For more information, see Changes to SharePoint support.
In addition to event log monitoring, the SCOM pack now provides monitoring of Enterprise Vault components and the layout of information in the pack has been improved.
SCOM packs from Enterprise Vault 9.0 to 10.0.2 can be used together on the SCOM server; you can use both old and new SCOM packs if required.
You can use the new SCOM pack to monitor all versions of Enterprise Vault 9 and Enterprise Vault 10.
The SCOM Management Pack is available from the Enterprise Vault media. You do not need to copy it from the Enterprise Vault program folder as in previous releases.
For information about configuring the SCOM Management Pack, see the "Automatic monitoring" chapter in the Administrator's Guide
For Management Pack release notes, see the ReadMeFirst.
Enterprise Vault event log filtering is a mechanism that reduces the number of event log entries that Enterprise Vault creates.
By default, event log filtering is enabled, so Enterprise Vault suppresses error and warning events that are repeats of events that have already been logged recently.
You can configure event filtering as required. For example, you can configure it so that specific events are never filtered.
For more information, see the "Filtering event logs automatically" chapter in the Administrator's Guide.
Enterprise Vault databases now contain a set of roles that let you revoke the Vault Service account's ownership of the databases, and assign only the minimum permissions it needs to run Enterprise Vault.
For more information, see the following document on the Symantec Enterprise Support site:
http://www.symantec.com/docs/HOWTO80670
Enterprise Vault now supports the 64-bit version of Domino on the Enterprise Vault Domino Gateway (EVDG). This is in addition to the existing support for 32-bit Domino on the EVDG.
For the latest information on the supported versions of Domino and Lotus Notes on the EVDG, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
In addition to Enterprise Vault's existing Domino language support, the Enterprise Vault 10.0.3 extensions for Lotus Domino introduce English-only support for the following languages:
When EVInstall.nsf detects any of these languages on the Domino server, it installs US English (en-US) extensions.
The following table lists the language of the Enterprise Vault extensions that EVInstall.nsf installs for each language it detects on the Domino server:
| Domino language detected | Language of extensions installed by EVInstall.nsf |
|---|---|
| Czech (cs) | Czech (en-US) |
| Danish (da) | Danish (da-DK) |
| Dutch (nl) | Dutch (nl-NL) |
| English (en) | English (en-US) |
| Finnish (fi) | Finnish (en-US) |
| French (fr) | French (fr-FR) |
| German (de) | German (de-DE) |
| Greek (el) | Greek (en-US) |
| Hebrew (he) | Hebrew (he-IL) |
| Hungarian (hu) | Hungarian (hu-HU) |
| Italian (it) | Italian (it-IT) |
| Japanese (ja) | Japanese (ja-JP) |
| Korean (ko) | Korean (ko-KR) |
| Norwegian (no) | Norwegian (en-US) |
| Polish (pl) | Polish (pl-PL) |
| Portuguese (pt) | Brazilian Portuguese (pt-BR) |
| Russian (ru) | Russian (ru-RU) |
| Simplified Chinese (zh-CN) | Simplified Chinese (zh-CN) |
| Slovenian (sl) | Slovenian (en-US) |
| Spanish (es) | Spanish (es-MX) |
| Swedish (sv) | Swedish (sv-SE) |
| Traditional Chinese (zh-TW) | Traditional Chinese (zh-TW) |
| Turkish (tr) | Turkish (en-US) |
File System Archiving (FSA) now supports Windows file server archiving without the requirement to make the Vault Service account a member of the local Administrators group on the file server. The account can run as a member of the local Print Operators group and with a reduced set of permissions and privileges. This change enables archiving from domain controllers, and from other file servers when local Administrator rights are not permitted for a service account.
For more information, see the chapter "Adding a Windows file server to File System Archiving" in Setting up File System Archiving.
Note: There is an additional requirement for the account that you use when configuring the FSA resource for an FSA cluster. See the section "Documentation additions and corrections" in the ReadMeFirst.
FSA now supports archiving from Windows Server 2012, including Server Core installations. The support for Server Core installations includes File Blocking and FSA Reporting.
New options in the Volume and Folder policies enable you to turn off archiving and placeholder creation for Windows Server 2012 deduplicated files, if required.
For more information, see the chapter "Adding a Windows file server to File System Archiving" in Setting up File System Archiving.
FSA now supports File Blocking and FSA Reporting on Server Core installations of Windows Server 2008 R2.
All the Enterprise Vault client applications, including the Outlook Add-In, Archive Explorer, search applications, and Outlook Web App (OWA) extensions, are now supported for use with the Windows 8 Pro and Enterprise editions. This release also supports FSA placeholder and internet shortcut access from clients that are running Windows 8 Pro or Enterprise.
The Enterprise Vault Client for Mac OS X that is included with this release is supported for use on client computers that run Mac OS X version 10.8 (Mountain Lion), as well as on computers that run Mac OS X version 10.5 through 10.7.
The Vault Cache Diagnostics page allows administrators to view the results of Vault Cache synchronization attempts by the Outlook Add-In.
The following technical note describes how to access the Vault Cache Diagnostics page and how to use the diagnostic information to troubleshoot synchronization issues:
http://www.symantec.com/docs/HOWTO77190
If you use System Center Operations Manager, the following Microsoft cumulative updates are required on the SCOM server and on each Enterprise Vault server that you monitor:
Because of an index schema update in Enterprise Vault 10.0.3, there is an automatic indexing metadata update when you upgrade from Enterprise Vault 10.0, 10.0.1 or 10.0.2.
The Indexing service startup is not complete until after the automatic update. For example, an Enterprise Vault server with the minimum recommended specification may take 40 minutes or longer to process 5,000 index volumes.
To obtain the changes described in this section, the Enterprise Vault 10.0.3 Outlook Add-In must be installed.
In certain circumstances, the Vault Cache contained fewer items than expected. In addition, the content of some items was missing in Virtual Vault.
This could occur in the following situation:
The issue resulted from a problem with the client retry mechanism, which has been fixed. If a Vault Cache database file fails to download to the client, the client now retries the download. The retry mechanism can now handle multiple database files for a quarter.
If the number of download attempts exceeds the maximum threshold, then the client writes to the log file, FailedDBDownloads.log, and moves on to download the next database file. The log file is located in the Vault Cache folder. The log file entry provides information about the dates and SNUM values of the items that the client failed to download.
The location of the Vault Cache folder is defined by one of the following client registry settings:
If you have access to Enterprise Vault properties on Outlook folders, you can change the retention category for a folder. You can also stop archiving a folder as follows:
If you used Enterprise Vault folder properties to stop archiving an Outlook folder, the retention category applied to archived items in the folder could change. This occurred if you had set a retention category other than the default retention category on the folder.
This has been fixed. If you stop archiving a folder, the retention category on archived items in the folder is not changed.
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 10.0.3 Outlook Add-In.
Users who installed the Polish version of the Outlook Add-In that was supplied with Enterprise Vault 10.0.1 or 10.0.2 would receive the following error message when they clicked any archived item in their mailboxes:
Script Error.Type mismatch:'CConst' Line No : 33
This has been fixed.
Users who installed additional language packs for Microsoft Office and then changed their Office language would sometimes find that the Virtual Vault feature was unavailable in Outlook.
This has been fixed.
The following error message would appear in Lotus Notes when you tried to forward multiple shortcuts that had attachments:
One or more of the source document's attachments are missing. Run Fixup to delete the document in the source database
However, you could forward multiple shortcuts without attachments and multiple unarchived items with attachments. In addition, the issue did not affect Lotus iNotes users.
This has been fixed.
The View and Restore options in the Enterprise Vault Client for Mac OS X did not work after users upgraded to Outlook 2011 for Mac Service Pack 2 (versions 14.2.0 and 14.2.2).
This has been fixed.
More items than expected were archived if the following options were configured in the Exchange Mailbox policy:
The archiving task did not stop when the configured percentage of mailbox available space was reached. Instead, the task continued archiving until the override condition was reached.
This issue is documented in the following technical note on the Symantec Enterprise Support site:
http://www.symantec.com/docs/TECH176051
This has been fixed.
In some circumstances, mailbox permissions for linked external accounts were not synchronized to the users' archives, with the result that users had no access to their archives.
This has been fixed.
UNC paths in the portion of an email message that is added to the body of a mailbox shortcut were lost during shortcut processing.
For example, \\server\share became \server in the mailbox shortcut.
This has been fixed.
Archiving performance was sometimes slow when external filters were enabled for the Exchange Journaling task. This issue could occur if several custom filter rules were based on large distribution lists.
This has been fixed.
In some circumstances Vault Cache synchronization produced warnings with event ID 1309 in the Enterprise Vault server's event log.
This has been fixed.
When Domino archiving tasks encountered some corrupt items that could not be archived, the tasks failed to blacklist the items. This meant that the archiving tasks tried to archive these items again on each archiving run, and created multiple savesets in the archive.
This has been fixed. The Domino archiving tasks now correctly blacklist corrupted items which they cannot archive.
If a FIELDGROUP LABEL attribute in Custom Properties.xml contained Unicode characters, this prevented the field group from being displayed in the Web Access application.
This has been fixed.
In a configuration with multiple target NetApp filers, a NetApp placeholder slave process named EvNetAppPhSvr.exe on the Enterprise Vault server restarted several times a day. The restarts of the process disrupted NetApp file archiving and recall.
The problem occurred during the periodic health checks of the slave process. The SQL query to fetch the list of NetApp filers did not return the list of filers in a consistent order, which inferred a change in server configuration when none had occurred.
This has been fixed.
After a placeholder recall, a file server could become unresponsive and require a reset. The problem occurred when the FSA filter driver evmf.sys became deadlocked with the Windows Cache Manager, when a file was recalled as part of the cache read-ahead mechanism.
This has been fixed.
If you defined File Blocking rules when adding a volume policy, the volume policy creation sometimes failed.
This has been fixed.
A problem could be introduced if you attempted to upgrade the FSA Agent to version 10.0.2, and the upgrade failed for some reason.
If you reattempted the upgrade it might then always fail, with an "Installation operation failed" error and error status 1603 in the FSA Agent installation log.
This has been fixed.
You can add targets from SharePoint 2013 for archiving only if they have either of the following authentication configurations:
You can add targets from SharePoint 2010 for archiving only if they have the classic mode authentication.
You cannot use shortcuts in Office Web Apps to access SharePoint 2013 content that has been archived by Enterprise Vault 10.0.3.
Enterprise Vault can archive from closed sites in SharePoint. SharePoint 2013 allows a closed site collection to be marked as read-only.
Enterprise Vault does not create shortcuts for items that are archived from read-only sites. Additionally, you cannot restore archived items to read-only sites. These limitations apply to all versions of SharePoint.
Enterprise Vault could not archive documents from SharePoint libraries when all the following were true:
This has been fixed.
If you added a custom date and time property to a Microsoft Office document or an item in SharePoint, EVSPShortcutManager failed to recall the document from the archive.
This has been fixed.
When Enterprise Vault collection encountered a file that was less than 4 KB, an error similar to the following was reported in the event log:
Log Name: Symantec Enterprise Vault Source: Enterprise Vault Date: ... Event ID: 6842 Task Category: Storage File Watch Level: Error Keywords: Classic User: N/A Computer: EV.Example.local Description: A Collector encountered an error. Reason: The data is invalid. (0x8007000d) PartitionEntryID: 1835FD8AF0C12D84F8EBFB370494293E81q10000EV10EV.Example.local Method: CCollector::CreateCollection
This has been fixed.
Storage File watch sometimes reported event ID 7110 warnings when verifying some SIS parts in collections. The size of the SIS part was incorrectly reported as 0 (zero) bytes.
This has been fixed.
It was possible to archive items to an incorrectly configured Hitachi Content Platform device. When this happened, it was not possible to retrieve the archived items.
This has been fixed. Enterprise Vault now does not archive to an incorrectly configured Hitachi Content Platform device.
This release updates the Centera SDK version to 3.3 (3.3.718), which EMC released on July 2, 2012.
Enterprise Vault did not normalize instances of Ý (Alt+0221) or ý (Alt+0253). The consequence was that you had to include these characters in search terms if you wanted to find words that contained those characters.
This has been fixed. These characters are now normalized correctly in new indexes.
If you want this fix to apply to indexes that were created in Enterprise Vault 10.0, 10.0.1, or 10.0.2, you must rebuild those indexes.
If you deployed Enterprise Vault Reporting with SQL Server 2012 Reporting Services, the following operation reports were not available:
This has been fixed.
Enterprise Vault Reporting's Vault Store Usage by Billing Account report did not correctly populate the Full Name column for each billing account.
This has been fixed.
During shortcut updates, Move Archive reported the same error when it encountered either of the following in Exchange mailboxes:
By design, Move Archive does not update orphaned shortcuts and should not have reported this as an error.
Move archive now skips orphaned shortcuts during the shortcut update stage and reports an error only for shortcuts that it does not update because the associated item was not moved to the target archive.
Note that this fix requires you to assign an additional cross-site permission in the case of moves between two sites that are controlled by different Enterprise Vault directories.
The Administrator's Guide already describes that in this case the Vault Service account or other account under which you run Move Archive in the source site must be assigned to the power administrator role in the target site.
In addition, the Vault Service account or other account under which you run the Exchange archiving task in the target site must be assigned to the task application role in the source site.
Some archived items that were originally archived by Enterprise Vault 2007 or earlier and then moved using Move Archive could not be retrieved with Enterprise Vault 10.0.1 or 10.0.2.
This has been fixed.
In the log files that EVSVR would produce when you ran the following operations, the summary report would show the wrong number of Domino mailbox archives and Domino journal archives:
This has been fixed.
In the log file that EVSVR would produce when you ran a Repair DatabaseReferences operation on a CIFS partition, the summary report would sometimes show the wrong number of saveset records that the operation failed to recreate. When this was the case, the "No Index Entry" and "No Target Entry" counts would be wrong. The problem did not affect Repair DatabaseReferences operations that you ran on Centera partitions or on partitions on streamer storage devices.
This has been fixed.
If the root path that you configured for a Hitachi Content Platform streamer device exceeded 37 characters, Enterprise Vault could not index, recall, and restore the items stored on it. The following errors in the Enterprise Vault event log were the most obvious signs of this issue:
Event Type: Error Event Source: Enterprise Vault Event Category: Storage Crawler Event ID: 28944 Computer: EVSERVER Description: The 3rd party storage system application 'Hitachi Content Platform (HCP) Streamer' has logged the following message: CStreamerObject::Read method failed Reason = 0x80070002 ConnectionManager::Set_Curl_Operation method http://HCPStorage.mydomain.com/rest/VeryLongRootPathNameForHitachiTestDevice /94618370CEA1E545AFDF5186F1604A8E/2012/May/03/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28 Reason = 404 : Not Found - opr_GETConnectionManager::Set_Curl_Operation method http://HCPStorage.mydomain.com/rest/VeryLongRootPathNameForHitachiTestDevice /94618370CEA1E545AFDF5186F1604A8E/2012/May/03/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28 Reason = 404 : Not Found - opr_GET Event Type: Error Event Source: Enterprise Vault Event Category: Storage Crawler Event ID: 7083 Computer: EVSERVER Description: Retrieval of saveset failed. Archive Id: 17309ED17DCB9B746931C1521D361D5061110000EVMBX01 Transaction Id: F0ECD449CD75B30B7FDCD645018E5691 Extended information: The system cannot find the file specified. (0x80070002) Internal Ref: Vault/RI
The cause of the issue was a character limit on a SQL column that Enterprise Vault uses to store the URL to each saveset's storage location on the Hitachi Content Platform streamer device. A root path longer than 37 characters caused the URL to exceed the column limit and consequently be truncated.
This has been fixed. If you have previously encountered this issue, we recommend that you do the following:
EVSVR would stop responding if you ran the Verify ArchiveObjects operation
with a verification level of SavesetValid, and the target partition was a
CIFS partition with no collection (.cab) files.
This has been fixed.
In rare cases, the EVSVR operations Verify DatabaseLinkages and Verify Complete would report an issue with one or more collection records, like this:
Collection file path: \\path_to\Collection123456.CAB, Identity: 123456, TotalCount: 201, RefCount: 204 Collection Reference Count greater than Total Count. Reference: 204, Total: 201
When you subsequently ran the Repair DatabaseReferences operation, and then the Repair DatabaseLinkages operation, neither corrected the issue.
This has been fixed.
The Enterprise Vault Administration Console 'Performance Trace' traces generated log files that did not show all time-related information.
This has been fixed.
In the Enterprise Vault Install Launcher (setup.exe in the
root folder of the Enterprise Vault media), the Server Preparation
option with which you can enable the required Windows components on a Compliance
Accelerator or Discovery Accelerator server did not enable an important prerequisite:
ASP.NET.
This has been fixed.
This release includes version 8.3.7 of the Outside In® Technology content converters from Oracle® Corporation. The content converters include patches up to, and including the following:
When the Storage service was restarting it was possible for errors such as the following to be logged by the Storage Online process:
Event ID: 6655 Storage Online Process (1) - Process failed PID: 0 Exit Code: Unspecified error (0x80004005) The process has failed abnormally and will not be restarted. Either the process has exceeded its restart count or automatic restart is disabled. The process can be restarted by stopping and restarting the Storage Service
The errors occurred when Storage Online was started at the same time as the Storage service was shutting down.
This has been fixed.
When Mobile Search users searched an archive with multiple index volumes, the search failed with an "Access Denied" message.
This has been fixed.
The Discovery Search Service was a new feature in Enterprise Vault 10.0.2. This service is designed to allow the Symantec Clearwell eDiscovery Platform to conduct advanced searches across all the archives in an Enterprise Vault installation. Current versions of the Clearwell eDiscovery Platform do not use the Discovery Search Service, so the option to install it has been removed from Enterprise Vault until a future version of the Clearwell eDiscovery Platform does use it.
If you installed the Discovery Search Service as part of Enterprise Vault 10.0.2, note the following points about upgrading to Enterprise Vault 10.0.3:
Copyright © 2013 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo, 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