Last updated: 6-Jul-2009
This document describes Enterprise Vault 8.0. The Enterprise Vault 8.0 Service Pack 2 (SP2) document, included as Updates_en.htm on the Enterprise Vault media, describes the new features and fixes included in Enterprise Vault 8.0 SP2. For the most up-to-date version of these documents, see http://entsupport.symantec.com/docs/308966 on the Symantec Enterprise Support site.
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 8.0 SP2, included as Upgrade_Instructions.pdf and Upgrade_Instructions.chm on the Enterprise Vault media.
Before you install or upgrade to Enterprise Vault 8.0 SP2, it is important to read the Points to note and issues sections.
For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).
For the latest information on Enterprise Vault 8.0 sizing and performance, see the Enterprise Vault Performance Guide (http://entsupport.symantec.com/docs/312319).
The Enterprise Vault Administration Console and documentation are available in Japanese and Simplified Chinese. The localized context-sensitive Help is included on the Enterprise Vault 8.0 SP2 media. You can download localized versions of the release notes and manuals from http://entsupport.symantec.com/docs/308966.
Enterprise Vault 8.0 provides the following new features:
The Enterprise Vault 8.0 Service Pack 2 document describes the new features included in Enterprise Vault 8.0 SP2.
Enterprise Vault 8.0 uses an optimized single instance storage model that can help to significantly reduce the storage space for archives.
Enterprise Vault identifies the shareable parts (SIS parts) of an item and gives each SIS part a digital fingerprint. It then stores each SIS part separately and only once within the sharing boundary, which can extend across vault stores. When Enterprise Vault identifies a SIS part that it has already stored, it references the existing SIS part instead of storing the SIS part again.
Single instance storage can help to reduce storage space in a number of ways. For example:
Vault stores are now grouped into vault store groups. A vault store group acts as the outer boundary for the sharing of SIS parts. Each vault store group requires a fingerprint database, which may grow quickly when you use single instance storage. You create and configure the fingerprint database when you create a vault store group.
You can set the sharing level for each vault store to be one of the following:
The Configure Sharing wizard lets you set the sharing level for each vault store in a vault store group. The wizard includes a connectivity test to help to determine whether the network latency is low enough over the relevant connections to provide a reasonable level of performance when sharing.
On upgrade from Enterprise Vault 2007, Enterprise Vault places your existing vault stores in a vault store group named "Default Upgrade Group". Enterprise Vault sets the sharing level of all vault stores in that group to "No sharing", until you configure sharing for that group.
Note: Enterprise Vault single instance storage is not performed when items are stored to partitions hosted on EMC Centera devices. Enterprise Vault continues to provide a device-level sharing option to take advantage of the sharing capabilities of EMC Centera.
For more information on setting up single instance storage, see the chapter "Setting up storage" in Installing and Configuring.
Enterprise Vault 8.0 introduces a new backup mode for vault stores and index locations. This feature allows vault stores and index locations to be backed up without the need to restart Enterprise Vault services or set registry values. While vault stores and index locations are in backup mode, users can continue to search their archives and restore items, but Enterprise Vault does not write to archives or indexes.
Note that the use of registry keys to place Enterprise Vault in read-only mode is deprecated but is still supported.
Backup mode can be controlled through the administration console. Enterprise Vault 8.0 also introduces six new PowerShell cmdlets:
Set-IndexLocationBackupMode Set-VaultStoreBackupMode Clear-IndexLocationBackUpMode Clear-VaultStoreBackupMode Get-IndexLocationBackupMode Get-VaultStoreBackupMode
The cmdlets set and clear backup mode, and report the current backup mode of vault stores and index locations. You can use these cmdlets to set and clear backup mode in your backup scripts.
Note: Microsoft PowerShell 1.0 must be installed on your server to run these cmdlets.
For more detailed information about backing up Enterprise Vault, refer to the Administrator's Guide.
Vault Cache for Outlook users replaces the Offline Vault feature that was in previous releases of Enterprise Vault. Like Offline Vault, Vault Cache provides instant access to archived items when the user is working offline.
For Lotus Notes users, Vault Cache was introduced in Enterprise Vault 2007 Service Pack 3.
The main changes are as follows:
The administrator controls the availability of the Enable Vault Cache wizard, the Vault Cache Properties dialog box, and the manual synchronization option.
The main changes are as follows:
The main changes are as follows:
In Windows XP and Windows 2003, the "Offline Vault" option in the main toolbar of Windows Desktop Search now appears as "Vault Cache".
In Windows Vista, there is no "Vault Cache" option in the main toolbar of Windows Search. Instead, users must select the All or E-mail option to search for emails in their vault cache. For specific attachment types in the vault cache, use the remaining tabs like "Document", "Picture", "Music", and "Other" only.
Before Enterprise Vault 8.0, you could select an archiving strategy based on one of the following:
When archiving is based only on age, it may not archive enough items to keep some mailboxes within their quota. When archiving is based only on quota, some mailboxes may not come close to the storage limit. In this case, not even older items are archived.
With Enterprise Vault 8.0, you can select archiving based on age and quota. Enterprise Vault performs age-based archiving first. If age-based archiving does not make the required percentage of mailbox storage limit free, archiving continues until the required percentage is reached.
The main changes are as follows:
When you use UseInactivityPeriod and UsePercentageQuota, you must set at least one of them to true.
The new Enterprise Vault Getting Started wizard enables you to configure archiving as quickly as possible. You can run the Getting Started wizard immediately after the Enterprise Vault Configuration wizard.
The wizard helps you to do the following, as appropriate:
You can choose to run sections of the wizard in express mode or in custom mode, as follows:
See Installing and Configuring for information on using the Getting Started wizard.
The new Administration Console Common Tasks pane provides shortcuts to tasks that you often need to perform in the Administration Console.
To go to Common Tasks
If you are using roles-based administration, the tasks that are shown in Common Tasks correspond to the functionality that is available to your role.
Desktop policies enable the administrator to manage the availability of features and behavior of the Enterprise Vault clients for Exchange and Domino.
Desktop policy settings control options such as the following:
You assign a desktop policy to a provisioning group when you create the provisioning group. You can create multiple desktop policies if you want different provisioning groups to provide a different desktop experience.
Enterprise Vault provides a default desktop policy for Exchange and Domino.
Note that the mailbox policy settings that affect the user's desktop experience have now been moved into the desktop policy. Many of the mailbox policy's Advanced settings have now been moved to various tabs on the desktop policy.
Enterprise Vault’s partition rollover feature allows you to configure vault store partitions so that archiving rolls over from one partition to another when certain criteria are met. For example, you can configure a partition to roll over to the next available partition when the disk that hosts it has only 5% free space. You can also configure a partition to roll over on a specific date.
In each vault store, you can configure a series of rollover enabled partitions, using volume based rollover, time based rollover, or a mixture of the two, to suit your environment and backup requirements. Archiving can then run for an extended period of time without administrator intervention.
For more details, see the Administrator’s Guide.
Partition rollover can be controlled through the administration console. Enterprise Vault 8.0 also introduces a new PowerShell cmdlet called Start-PartitionRollover which lets you force partition rollover in the vault store you specify.
Note: Microsoft PowerShell 1.0 must be installed on your server to run this cmdlet.
The following script extract shows how you can use Start-PartitionRollover in a script to:
Start-PartitionRollover cmdlet to force partition rolloverpowershell -psconsolefile "C:\Program Files\Enterprise Vault\EVShell.psc1" -command "& {Start-PartitionRollover EVArch1 VS1}"
This connects to the Enterprise Vault server EVArch1 and verifies that vault store VS1 uses the storage service on this server. If it does, Start-PartitionRollover forces partition rollover in vault store VS1.
Enterprise Vault’s trigger file mechanism, which controls the removal of safety copies of archived items, has been enhanced. The existing TXT file mechanism is still supported, and a new XML trigger file mechanism has been introduced. This mechanism allows vendors of backup software and devices to place an XML file in the root of a partition to show that a backup has been completed. The date value in the file indicates the date and time of the backup. Enterprise Vault uses this information to determine which saveset files on the partition have been secured, so it can remove the corresponding safety copies.
Configuration of the trigger file mechanism no longer relies on registry values. The configuration of this feature is now managed within the administration console. As a result, the following registry values are removed from Enterprise Vault 8.0 during upgrade.
FileWatchEMCCenteraScanInterval
FileWatchEnableIgnoreArchiveBit
FileWatchScanInterval
For more details, see the Administrator’s Guide.
Enterprise Vault can now apply retention categories to items based on settings synchronized from Exchange 2007 Managed Folders.
This new feature lets you avoid conflict between the retention periods set in Enterprise Vault and the Managed Folder Content Settings specified for Exchange Managed Folders.
The main changes are as follows:
Before Enterprise Vault 8.0, an archive did not reflect changes to the location of a shortcut in an Exchange mailbox, or a change to the retention category of an archived item. For example, if a user moved a shortcut to another mailbox folder, the item's location in the archive was still the original folder from which it was archived.
In Enterprise Vault 8.0 SP1, when a user moves or copies a shortcut to another folder or changes an item's retention category, the change is reflected inside the archive. If the new location is configured to use a shared archive, Enterprise Vault creates a copy of the item in that archive. It leaves a copy in the original archive even if the item's shortcut was moved, rather than copied.
The main changes are as follows:
When you use the Administration Console to nominate a new location in which
the Indexing service can store its indexes, Enterprise Vault now creates eight
subfolders of your chosen folder. These subfolders are called index1,
index2, and so on. The creation of a number of index locations
in advance makes it easier to move them to another storage volume when they
are full.
The Vault Site alias and Web Access application URL are now generated automatically when the first computer is added to the Enterprise Vault Site.
The Web Access application URL is generated as follows:http://EVserver_alias/EnterpriseVault
where EVserver_alias is the fully-qualified DNS alias of the first Enterprise Vault
server that is added to the Site.
The name of the Web Access application virtual directory in IIS must be /EnterpriseVault.
The Vault Site alias, Web Access application URL and virtual directory for the Web Access application are read-only and cannot be changed.
In Site Properties, on the General page, you can view but not change the Vault Site alias. The Web Access application URL is no longer displayed, but the following options enable you to change the protocol or port used to access the Web Access application:
Use TCP port
Before setting a different protocol or port, you should first make the required changes to the default web site in IIS.
Note: Changing the Web Access application protocol or port after items have been archived will break existing shortcuts.
File System Archiving policies now enable you to specify that the archiving task must not create a shortcut immediately when an item is archived. The archiving task then creates a shortcut when the file meets the criteria that you define.
This new feature enables you to ensure that Enterprise Vault does not create shortcuts for files that are modified frequently. This means that a user who wants to modify a file can open a local copy of the file, even though the file is safely archived. When the file is no longer changed frequently, Enterprise Vault creates a shortcut to the archived version.
There are several date and time criteria that you can use when defining the archiving rule. For example, you can make Enterprise Vault archive a file and then create a shortcut 15 days after the last modification date.
For more information about the new shortcut creation options, see the 'Shortcut creation options' section in Setting up File System Archiving.
File System Archiving now starts processing from the point at which it was interrupted. This enables File System Archiving to process volumes that are too large to be processed during a single archiving run.
File System Archiving creates a report for each run, so a volume that requires several runs to process completely will result in several reports. The reports are stored in folders under the FSA subfolder of the Enterprise Vault program folder.
For more information, see the 'File System Archiving task reports' section in the Setting up File System Archiving manual.
FSA Reporting includes the following enhancements:
The batch file is named FSAReporting_TrimData.bat. It is located in the
FSAReportssubfolder of the Enterprise Vault program folder, typicallyC:\Program Files\Enterprise Vault\FSAReports. Only the FSAReporting user can run the batch file.For more information on running the trimming batch file, see the Administrator's Guide.
Enterprise Vault Reporting includes three new Operation Reports that provide information on the storage space reduction that has resulted from Enterprise Vault single instance storage:
"Storage Reduction by File Extension" provides information on the storage reduction in a vault store group for different types of files, grouped by file extension. The report shows storage savings for both the most shared files and the most commonly occurring files.
"Storage Reduction per Vault Store Group" provides information on the storage reduction within every vault store in a specified vault store group.
"Storage Reduction Summary" provides summary information on the storage reduction for each vault store group in an Enterprise Vault site.
If you have installed and configured Enterprise Vault Reporting you can access the storage savings reports from the Administration Console. To do this, right-click the vault store groups container or a vault store group, and on the shortcut menu click the name of the report that you want to run.
Enterprise Vault Reporting and Operations Manager now use roles-based administration. For example, in Operations Manager a Domino administrator can view only Domino information and parameters.
Archive Explorer has been enhanced as follows:
When you open Archive Explorer in a Web browser, the preview pane now displays an HTML version of archived files. Some file types, for example JPG and GIF, cannot be previewed. The administrator can set the maximum size of archived files that can be displayed in the preview pane, using the setting MaxPreviewSize in the Web application configuration file WebApp.ini. The default is 512 KB. The setting does not apply to archived messages.
The Enterprise Vault Advanced Search dialog, which is part of Integrated Search in Outlook and Lotus Notes, has been redesigned. The Outlook version of Advanced Search provides improved options for searching a file system archive.
It is now possible to install the Enterprise Vault Domino Gateway on a Domino partitioned server. The Enterprise Vault installation enables you to select the required partitions.
Enterprise Vault 8.0 includes the following Centera components:
Enterprise Vault 8.0 includes a management pack for System Center Operations Manager 2007 (SCOM).
The management pack contains rules that enable SCOM to monitor critical Enterprise Vault events in the Application Event Log.
See the Administrator's Guide chapter 'Automatic monitoring' for more information.
Enterprise Vault 8.0 supports the hotfix and the changes to the journal report format described in the following Microsoft support article: http://support.microsoft.com/KB/956892.
The Enterprise Vault Administration Console and Operations Manager, their help, and the administration manuals are available in English, Japanese and Simplified Chinese.
The Enterprise Vault Outlook User Add-Ins, extensions for Lotus Notes clients, Archive Explorer, Enterprise Vault search applications and SharePoint Archive Search Web Parts are available in:
The prerequisite software has changed at Enterprise Vault 8.0. For example: Internet Explorer 6.0 is the new prerequisite version for both client and server; and the new minimum version of Outlook, to support the new Enterprise Vault 8.0 functionality, is Outlook 2003. For details of all the changes, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).
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.
The Deployment Scanner has been updated for Enterprise Vault 8.0, and is included in the Symantec Enterprise Vault 8.0 SPn\Deployment Scanner
folder on the Enterprise Vault media, where n is the number of the service pack.
Before installing Enterprise Vault 8.0, or upgrading, we strongly recommend that you run the Deployment Scanner to check prerequisite software and settings.
Use the Vault Service account when running the Deployment Scanner.
To install 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.
The Enterprise Vault Deployment Scanner checks for the following prerequisites 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.
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.
For important guidelines on the deployment of FSA Reporting, see the following Enterprise Vault technical note: http://entsupport.symantec.com/docs/327402.
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.
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 Enterprise Vault 8.0 it is no longer possible for Web clients to download .DVS files when retrieving archived item. The download options are now as follows:
This option requires that you define the new Webapp.ini setting, HTMLNotMSG, as follows:
HTMLNotMSG=1
The old HTMLNotDVS setting still works but is now deprecated. You are recommended to use HTMLNotMSG.
In previous versions of Enterprise Vault you could use the registry value ShortcutDeletionNow to make shortcut expiry runs as soon as the archiving task started.
In Enterprise Vault 8.0, ShortcutDeletionNow has been replaced by options in the Administration Console Run Now dialog boxes. When you use Run Now you can choose to run the task to perform either Archiving and Shortcut processing or Shortcut processing.
Enterprise Vault no longer uses the registry value ShortcutDeletionNow.
The registry value SkipEnvelopeSMTPDomain is no longer used. This registry
value was used to improve performance when processing large distribution lists. Performance
improvements in Enterprise Vault 8.0 mean that SkipEnvelopeSMTPDomain
is no longer required.
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".
Previously, unprivileged users in the PST Administrator role could not perform PST migrations unless they were members of the local administrators group on the Enterprise Vault server. The group membership was required so that the users could connect to a Migrator server on a remote computer.
This has now been fixed by changes to the Distributed Component Object Model (DCOM) permissions for the Migrator Server.
The changes are as follows:
You can, if required, change the permissions to fit your own security requirements.
Backup Exec 12 and 12.5 Agents for Enterprise Vault are not fully compatible with Enterprise Vault 8.0 or its service packs.
For more information, subscribe to the following TechNote on the Symantec Support Web site: http://entsupport.symantec.com/docs/321534.
Unless you assign the SQL system administrator (sysadmin) role to the Vault Service account, you must perform the following additional steps before you run the Enterprise Vault Configuration wizard:
If you do not perform these additional steps, the following occur:
See Steps for SQL Server 2000, or Steps for SQL Server 2005 or SQL Server 2008.
Add the Vault Service account to the msdb system database as follows:
Grant permissions to the Vault Service account as follows:
Steps for SQL Server 2005 or SQL Server 2008
Add the Vault Service account to the msdb system database as follows:
Grant permissions to the Vault Service account as follows:
Assign the database role SQLAgentUserRole to the Vault Service account as follows:
When you install Enterprise Vault 8.0 SP2 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 2007 have not yet been certified for Enterprise Vault 8.0.
Before you upgrade, check the Compatibility Charts for details of the supported devices:
http://entsupport.symantec.com/docs/276547
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.
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.
You can use any of the IBM Lotus Domino Server types for the Domino Server installed on the Enterprise Vault Domino Gateway. The IBM Lotus Domino Messaging Server satisfies the minimum requirements in terms of application features.
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 TechNote 289556 at http://entsupport.symantec.com/docs/289556.
When you install IIS on Windows Server 2008, you must include the IIS 6 Management Console component which is required by Enterprise Vault.
This prerequisite component is omitted from the section called "Enterprise Vault prerequisites for IIS on Windows Server 2008" in Installing and Configuring.
On Exchange Server 2000 and Exchange Server 2003, non-envelope journal archiving does not process meeting requests correctly. Enterprise Vault archives each meeting request repeatedly, each time creating a new archived item. When several hundred meeting requests have been received, the journaling process is continuously archiving meeting requests and is unable to process other types of message.
You can resolve this issue by installing the hotfix that is available from the following page: http://support.veritas.com/docs/316728
This issue may occur when Enterprise Vault has archived an item for which it does not create a shortcut (a calendar item, meeting request, or contact), and has replaced an OLE attachment in the item with a hyperlink.
The usual behavior is that clicking a hyperlink to an attachment downloads the attachment. If this issue occurs, clicking the hyperlink downloads the whole item in .msg format and opens it in Outlook.
For OWA users, the item opens only if they have Outlook installed. If Outlook is not installed, they have to search for the archived item and restore it to the mailbox in order to view the attachment.
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. This value means that OWA 2003 users access the Enterprise Vault server through the Enterprise Vault proxy.
For any other type of connection, the option Show 'Browser Search' link in Integrated Search is respected for OWA 2003 users.
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.
When you create a Domino retention folder, Enterprise Vault does not let you include the vertical bar character (|) or the backslash character (\) in the folder name.
This is a permanent restriction. It means you cannot create a Domino retention folder with an alias, or specify a folder hierarchy when you add a single folder name definition to the retention plan XML file. (To specify a folder hierarchy, you must define separate hierarchical folder names in the retention plan XML file.)
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 1414946.
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.
It is not possible to use Notes 8.0.2 to run EVInstall.nsf in order to modify a Russian mail template.
You can use Notes 8.0.1 to run EVInstall.nsf.
Symantec have applied to IBM for a fix to this issue.
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 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.
Retrieved encrypted items cannot be viewed when using DWA.
A user who attempts to use DWA to view an encrypted archived item is presented with standard Domino error text:
The body of this message is encrypted and cannot be decrypted. 1. You must import your Notes ID (which contains your certificates). 2. Import your internet certificate(X5.09) into your Notes ID for S/MIME.
Neither of the solutions suggested in the help text will fix the problem. The retrieved encrypted item cannot be viewed using DWA.
The user can restore the item and then view the restored item.
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.
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:
The Japanese and Chinese language versions of Enterprise Vault Reporting's single instance storage reports do not display from within the Administration Console. When you right-click on the Vault Store Groups container or a vault store group in the left pane, the context menu options only work for the English language reports.
To work around this issue, access the reports using the SQL Server Reporting Services Report Manager Web application.
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.
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.
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 have fixed this issue in Outlook 2007.
If users experience this issue, they should close Outlook to release the open file handles.
The PST Locator task cannot perform hard disk searches for PST files on NetApp MultiStore (Vfiler) devices.
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 support document http://entsupport.symantec.com/docs/281568.
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 are archived, but no shortcuts are created in the mail file.
A problem can occur on an NTFS file server when you recall placeholders in bulk for a volume on which pass-through recall is enabled. The bulk recall fails and the following error appears in the file server's event log:
The server was unable to allocate from the system nonpaged pool because the pool was empty
You can work around the problem by unloading and reloading the Enterprise Vault minifilter driver EvFilter, as follows:
Symantec will provide a hotfix for this problem for Enterprise Vault 8.0 SP2. When the hotfix is available you can download it from http://entsupport.symantec.com/docs/327168.
If you 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 for details of how to correct the problem:
http://entsupport.symantec.com/docs/326485
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.
Unwanted placeholder recalls can occur if you use the Windows Explorer preview pane that is provided with Windows Vista and Windows Server 2008. When you select a placeholder, Windows recalls the file to display the preview.
If pass-through recall of placeholders is configured, the pass-through recall does not succeed.
This problem is due to a limitation with the previewing of offline files. Symantec is working with Microsoft to resolve this problem.
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 attempt to recall a file that is larger than 4 GB from an internet shortcut, 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.
If you configure a non-default TCP port for the Enterprise Vault Web Access application, the archiving and recall of files may fail on an EMC Celerra device.
See the following TechNote on the Symantec Support Web site for more information and a workaround for this issue:
http://entsupport.symantec.com/docs/289676
The recall of large files on EMC Celerra can be slow. For more details and the latest information on this issue, see the following TechNote on the Symantec Enterprise Support site:
http://entsupport.symantec.com/docs/316523.
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 now 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.
A limitation with versions of Network Appliance Data ONTAP earlier than Data ONTAP 7.2 prevents Enterprise Vault from working correctly with Network Appliance MultiStore (Vfiler) systems. Enterprise Vault is unable to create an fpolicy on the filer automatically, and an error message appears in the event log on the Enterprise Vault server.
For details of how to create an fpolicy for Enterprise Vault to use, see the following support document: http://entsupport.symantec.com/docs/280369.
When it archives a file, File System Archiving does not archive any alternate data stream (ADS) that is associated with the file. Consequently, if you later restore the archived file or recreate its placeholder, the associated ADS is missing.
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 an NTFS 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 an NTFS 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.
In Enterprise Vault 8.0 SP2 the FSA Cluster Configuration wizard's help buttons do not display any help.
You can work around this by viewing the wizard's help topics as follows:
Launch the Enterprise Vault help. You can do this in either of the following ways:
- From the Administration Console, click Help > Help on Enterprise Vault.
- From the Start menu, click Start > Programs > Enterprise Vault > Documentation.
- FSA Cluster Configuration: Welcome
- FSA Cluster Configuration: Option
- FSA Cluster Configuration: Group
- FSA Cluster Configuration: Progress
- FSA Cluster Configuration: Summary
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.
By default, Microsoft Office XP, Microsoft Office 2003, and 2007 Microsoft Office programs do not install the VBScript component in Windows Terminal Server environments.
The Enterprise Vault Outlook Add-Ins require VBScript in order to retrieve Enterprise Vault shortcuts. If VBScript is not present, the Outlook Add-Ins show the content of shortcuts, without retrieving the archived items.
For details of how to add VBScript in a Terminal Services environments, see the following Microsoft support article: http://support.microsoft.com/default.aspx?scid=kb;en-us;302003.
If you set the PstDisableGrow registry value to prevent Outlook 2003 and 2007 users from adding new items to PST files, vault cache stopped working.
This has been fixed but depends on a Microsoft hotfix and further configuration. For more information, see the section called "Enabling vault cache if PstDisableGrow is set" in the Administrator's Guide.
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.
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 does not support this integration with Enterprise Vault, and so these options are no longer available.
When using Windows Desktop Search (WDS) with vault cache, WDS does not index password protected files in a user's vault cache.
WDS does not index the contents of vault caches on computers that are running the 64-bit versions of Windows.
It is possible for WDS 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 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.
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:
Vault cache may not work in an Exchange Server 2007 environment when the Desktop policy Advanced setting RPC over HTTP connection is set to 'Use proxy'.
See the following TechNote on the Symantec Support Web site for more information:
http://entsupport.symantec.com/docs/316191
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.
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.
When you run the Enterprise Vault Cluster Setup wizard in a 64-bit environment, the Enterprise Vault registry key that the wizard adds to the replication data is incorrect. In both 32-bit and 64-bit environments, the wizard adds the following registry key to the replication data:
HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault
However, in 64-bit environments, the correct registry key is as follows:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\KVS\Enterprise Vault
To resolve this issue, you must manually add the correct key to the Registry Replication (RegRep) resource.
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.
The Enterprise Vault Reporting Operation Reports do not display correctly when saved in PDF format on Japanese systems using SQL Server2000.
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 SQL Server 2005 or later is used, the account must also be a member of the 'SQLAgentUserRole' role.
The Enterprise Vault Reporting "File Groups Summary" report does not take into account any archived files that are recalled to the file server. The report data indicates the numbers of archived files, and the space occupied and saved, as if the files had not been recalled.
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://entsupport.symantec.com/docs/289435
The Enterprise Vault Reporting Operation Reports do not display correctly when saved in PDF format on Japanese systems using SQL Server 2000.
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:
When you have configured your Enterprise Vault MOM or SCOM management pack, you must also configure some of the rules before you can use them.
For example, if you want to use the following rule you must configure it to specify which SQL server to monitor:
Sample value of the performance counter SQL Server - Checkpoint pages / sec is greater than the defined threshold
This note provides more information on how to specify the URL of the Web Access application when you configure an EMC Celerra device for placeholder recalls.
The section "Adding an EMC Celerra device" in Setting up File System Archiving describes how to add an EMC Celerra device as an archiving target. Step 6 of the procedure describes how to use the fs_dhsm command to configure the HTTP connection for file recall requests. One of the parameters to the fs_dhsm command is ev_url, the URL of the Enterprise Vault Web Access application.
The Celerra is case-sensitive, so make sure that you supply the URL in the correct case. If the Celerra fails to find a connection with the server name that you specify in the URL, the files are archived but no placeholders are created. The File System Archiving task report's "Shortcut status" column then shows the error "NO_MATCHING_CONNECTION".
The format of ev_url is as follows:
http://server_name/EnterpriseVault
where server_name is the name of the Enterprise Vault server that hosts the Storage service for the Celerra archiving target, as specified in the ComputerEntryTable of the Directory database. This name is the same as the display name of the Enterprise Vault server in the Administration Console. You can determine server_name as follows:
Unless you assign the SQL system administrator (sysadmin) role to the Vault Service account, you must perform the following additional steps before you run the Enterprise Vault Configuration wizard:
For details, see Additional pre-installation tasks for Enterprise Vault server.
The Enterprise Vault 8.0 documentation, updated for Enterprise Vault 8.0 SP2, is available from the following locations:
Enterprise Vault 8.0 SP2\Documentation folder on the Enterprise
Vault media| Document | File names | Comments |
|---|---|---|
| Enterprise Vault Help | EV_Help.chm | Includes all the following documentation so that you can search across all files. You can access this file from the Windows Start menu (click Start > Programs > Enterprise Vault > Documentation) or from within the Administration Console (click Help > Help on Enterprise Vault). |
| Introduction and Planning | Introduction_and_Planning.pdf Introduction_and_Planning.chm |
Provides an overview of Enterprise Vault functionality. |
| Deployment Scanner | Deployment_Scanner.pdf Deployment_Scanner.chm |
Describes how to check the prerequisite software and settings before you install Enterprise Vault. |
| Installing and Configuring | Installing_and_Configuring.pdf Installing_and_Configuring.chm |
Provides detailed information on setting up Enterprise Vault. |
| Upgrade Instructions | Upgrade_Instructions.pdf Upgrade_Instructions.chm |
Describes how to upgrade an existing Enterprise Vault installation to the latest version. |
| Setting up Exchange Server Archiving | Setting_up_Exchange_Server_Archiving.pdf Setting_up_Exchange_Server_Archiving.chm |
Describes how to archive items from Microsoft Exchange user mailboxes, journal mailboxes, and public folders. |
| Setting up Domino Server Archiving | Setting_up_Domino_Server_Archiving.pdf Setting_up_Domino_Server_Archiving.chm |
Describes how to archive items from Domino mail files and journal databases. |
| Setting up File System Archiving | Setting_up_File_System_Archiving.pdf Setting_up_File_System_Archiving.chm |
Describes how to archive files that are held on network file servers. |
| Setting up SharePoint Server Archiving | Setting_up_SharePoint_Server_Archiving.pdf Setting_up_SharePoint_Server_Archiving.chm |
Describes how to archive documents that are held on Microsoft SharePoint servers. |
| Setting up SMTP Archiving | Setting_up_SMTP_Archiving.pdf Setting_up_SMTP_Archiving.chm |
Describes how to archive SMTP messages from other messaging servers. |
| Administrator's Guide | Administrators_Guide.pdf Administrators_Guide.chm |
Describes how to perform day-to-day administration, backup, and recovery procedures. |
| Reporting | Reporting.pdf Reporting.chm |
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 | Utilities.pdf Utilities.chm |
Describes Enterprise Vault tools and utilities. |
| Registry Values | Registry_Values.pdf Registry_Values.chm |
A reference document that lists the registry values with which you can modify many aspects of Enterprise Vault behavior. |
| Mobile Search Installation Guide | Mobile_Search_Installation_Guide.pdf Mobile_Search_Installation_Guide.chm |
Describes how to set up the Enterprise Vault Mobile Search application, which lets you search for and view Exchange archived emails and their attachments from the Internet browser on your mobile device. |
| Help for Administration Console | Admin_Console_Help.chm | The online Help for the Enterprise Vault Administration Console. |
| Help for Enterprise Vault Operations Manager | EVOM.chm | The online Help for Enterprise Vault Operations Manager. |
The Installing and Configuring manual was restructured for Enterprise Vault 8.0. It now comprises the Installing and Configuring manual, which describes how to set up Enterprise Vault, and a set of manuals that describe how to set up the different types of archiving after you have set up Enterprise Vault, for example Setting up Exchange Server Archiving.
The new Reporting guide 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. This information was previously included in Installing and Configuring and the Administrator’s Guide.
The Upgrade Instructions are no longer provided in HTML format. They are now provided in both .CHM and .PDF formats, as follows:
Symantec Enterprise Vault 8.0 SP2\Upgrade_Instructions.pdf
Symantec Enterprise Vault 8.0 SP2\Upgrade_Instructions.chm
C:\Program Files\Enterprise Vault\Upgrade_Instructions.pdf
C:\Program Files\Enterprise Vault\Upgrade_Instructions.chm
The Enterprise Vault Compatibility Charts, at http://entsupport.symantec.com/docs/276547, lists the supported devices and versions of software for Enterprise Vault.
Complimentary eLearning classes (a free one year subscription to the Enterprise Vault Tech Center for three logins) are included with your purchase of Enterprise Vault.
Enterprise Vault Tech Center features a collection of concise subject-specific on-demand modules that addresses key features, common questions, and advanced topics that you will encounter when using Enterprise Vault in your data center. The Enterprise Vault Tech Center features detailed information on the topics at hand and many modules include self-running demonstrations.
For each login:
Instructor Led Training (ILT), Virtual Training (VA) and On Demand (OD) classes also available:
For more information on Symantec courses, see http://www.symantec.com/enterprise/training/training_by_country/index.jsp
Copyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, VERITAS, and Enterprise Vault 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 contains 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 Enterprise Vault 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 Enterprise Vault
350 Ellis Street
Mountain View, CA 94043