Enterprise Vault (tm) for Exchange 5.0 SP4 English Client

Article:TECH38048  |  Created: 2005-01-29  |  Updated: 2006-01-01  |  Article URL http://www.symantec.com/docs/TECH38048
Article Type
Technical Solution

Environment

Issue



Enterprise Vault (tm) for Exchange 5.0 SP4 English Client

Solution



Enterprise Vault™ 5.0 Service Pack 4
This document describes the changes introduced by Enterprise Vault 5.0 Service Pack 4 server & client builds.
For details of the changes included in the earlier updates, see the previous updates.
Contents
  • Installation and prerequisite software
  • File System Archiving changes
  • Offline Vault changes
  • Changes affecting users
  • Administration Console changes
  • Policy Manager changes
  • Other changes
  • Outstanding issues
  • Copyright and trademarks
·
Installation and prerequisite software
Server installation
When you upgrade to Enterprise Vault 5.0 SP4 it is mandatory that you upgrade all Enterprise Vault servers, including OWA front-end and back-end servers.
Simplified OWA configuration [Ref 504059]
Most of the set up required for OWA Extensions has been automated in this release. For details of the new configuration steps, see "Installing and Configuring OWA Extensions" in Enterprise Vault Installing and Configuring.
MAPISVC.INF file version fix [Ref 504042]
If an invalid version of MAPISVC.INF is in the SYSTEM32 folder (normally C:\WINNT\SYSTEM32), a number of Enterprise Vault operations may fail with the error message MAPI-E-NOT-FOUND. In previous releases, this could be fixed by running the program SYSTEM32\FIXMAPI.EXE to update MAPISVC.INF.
In this release, the MAPISVC.INF file is automatically checked and updated, if necessary, by the Enterprise Vault Admin Service. The check is performed when the service starts and repeated at hourly intervals, because other applications may overwrite the file. Before the file is updated, a back-up copy called MAPISVC_ddmmhhmm.EVBK is created in the same folder. ddmmhhmm is the day, month, hour and minute when the back-up was taken.
This automatic check and update process is also performed on Accelerator systems, where Enterprise Vault services are installed but not configured.

File System Archiving changes
Restoring collected files using Archive Explorer [Ref 504054]
It was not possible to use Archive Explorer to restore files that had been archived by File System Archiving and subsequently stored in an NTFS collection.
This has been fixed.
Access permissions for Vault Service Account [Ref 504113]
If the Vault Service Account did not have Local Admin access to a volume or folder that was being processed by File System Archiving, errors such as the following error were logged:
Event Type: Error
Event Source: Enterprise Vault
Event Category: File Archive Server
Event ID: 40966
Date: 12/13/2004
Time: 3:46:24 PM
User: N/A
Computer: DEMO
Description:
A program fault has raised an exception.
Exception:
Object reference not set to an instance of an object.
Diagnostic:
Type: System.NullReferenceException
This has been fixed - the report file now provides information about access problems.
Errors when Vault Service Account has no access permissions [Ref 504116/1 and 504115 and 5040142]
When archiving or creating an archive point, there were Access Denied errors if the Vault Service Account did not have explicit write access permission to the appropriate volume or folder. There could also be errors if the Vault Service Account did have write access but the folder was set to Read-Only. For example, entries such as the following could appear in the Event Log:
Event Type: Error
Event Source: Enterprise Vault
Event Category: File Archive Server
Event ID: 40982
Date: 25/02/2005
Time: 09:36:02
User: N/A
Computer: DEMO
Description:
The Vault Service Account does not have write access
to the volume share: \\demo-2003\c$ or the volume is unavailable,
no items for this volume will be processed
This has been fixed. The Vault Service Account has access provided the account is a member of the Local Administrators group.
Archive Point management[Ref 504132]
It was not possible to use the ArchivePoints tool to specify both archive name and description, as documented in the Administration Console Help topic Archive points: Overriding default attributes.
This has been fixed.
Security fix for File System Archiving folders [Ref 504083]
When using Archive Explorer to view archived folders and files, it was possible for a user who had only List Folder Contents permission to read the contents of files.
This has been fixed.
Performance improvement for internet shortcuts [Ref 504116/2]
The amount of time taken to create an internet shortcut increased as the file size increased, with the result that files of several gigabytes could take minutes to turn into shortcuts.
This has been fixed. Large files now do not suffer a performance penalty.

Offline Vault changes
Offline Archive Explorer [Ref 504121]
When setting up Offline Vault and using offline Archive Explorer with no mailbox shortcuts, Offline Vault would ignore the maximum permitted size of the offline vault and thus could attempt to download items that would not fit in the available space.
This affected only the first download, when the offline vault was being created. On subsequent downloads, older items are automatically deleted as necessary in order to make space for newer items.
This has been fixed. There is now a prompt asking whether or not to increase the size of the offline vault. If the user chooses not to increase the size, no items are downloaded.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Offline Vault space allocation [Ref 504122]
Because of the Offline Vault internal structure, it is possible for an offline vault to be full and yet not have used all the allocated space. There has been an improvement in the internal space allocation within the offline vault, which means that users are much less likely to have this problem.
This improvement applies to new offline vaults only, not to existing offline vaults.
You must install the Enterprise Vault 5.0 SP4 User Extensions in order to benefit from this improvement.
Offline Vault settings [Ref 504119]
Some new settings have been added to Desktopsettings.txt, providing you with finer control of the Offline Vault behavior:
OVRootDirectorySearchPath: Controls the location of the offline vault.
Enables you to supply a list of possible locations for the offline vault. The first such location that is valid on a user's computer is the one that will be used at the time the offline vault is created. This enables you to specify a list that is likely to be suitable for computers with different configurations.
For example, if you specify: E:\vault;C:\vault then the offline vault would be created in E:\vault if that was valid on the user's computer, and if it was not valid, then it would be created in C:\vault. If none of the locations in OVRootDirectorySearchPath is valid, the one specified by OVRootDirectory is used, if possible.
Possible values: A semi-colon separated list of folder paths
OVDownloadItemAgeLimit: Specifies the maximum age of an item that will be downloaded to the offline vault by default.
For example, specifying 365 (days) means that items up to one year old will be downloaded by default. Items older than this will be downloaded only if the user requests them.
Possible values: An integer indicating the maximum age in days.
Each of these settings has a corresponding registry entry that you can set to control the behavior on individual client computers. Create the registry entries under the following registry key:
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client
The possible registry entries are:
  • OVRootDirectorySearchPath (a string entry)
  • OVDownloadItemAgeLimit (a DWORD entry)
· Offline Vault downloads [Ref 504095]
Under some conditions, items were being ignored that should have been automatically added to the offline vault before they were eligible for archive. This meant that, after those items had been archived from the mailbox, they would be downloaded into the offline vault.
This has been fixed.
Offline Vault automatic updates [Ref 504090]
If a user had offline Archive Explorer and a problem occurred during a download to the offline vault, subsequent downloads did not take place.
This has been fixed.
Offline Vault error [Ref 504088]
When using Offline Vault with Windows 2000, it was possible under some circumstances to receive an error that began with the following text:
Conflicting edits have been made to the same message.
The different versions of the message appear below.
To resolve this conflict, do one of the following:
This has been fixed.

Changes affecting users
Note that PST file marking in Outlook 2003 cached Exchange mode, listed under "Other Changes", also requires you to install the Enterprise Vault 5.0 SP4 User Extensions even though it has no direct effect on users.
Archive Explorer 'Next' and 'Previous' buttons [Ref 504160]
When using Archive Explorer with Outlook 2003 in cached Exchange mode, clicking on the toolbar Next or Previous buttons caused Outlook to terminate.
This has been fixed.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Manual archiving when in Outlook 2003 cached Exchange mode [Ref 504153]
When performing a manual archive using the Enterprise Vault User Extensions, it was possible for a user to change the selection before the archive operation was complete. This then resulted in the wrong items being archived.
This problem did not affect the Self-Installing User Extensions.
This has been fixed.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Incorrect view in Archive Explorer [Ref 504151 and 504140]
When using Archive Explorer, clicking the Sent Items folder correctly showed a view of Sent Items, but the first column was From rather than To.
This has been fixed.
Empty error when searching [Ref 504047]
Under some circumstances, it was possible for a user who attempted to search for items to be shown an error message that contained no text.
This has been fixed.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Archiving from subfolders [Ref 504109]
Using the Self-Installing User Extensions, it was not possible to archive an item from a subfolder of the mailbox root, or from a subfolder of one of the special folders, such as Inbox.
This has been fixed.
In order to obtain the fix, you must install the Enterprise Vault 5.0 SP4 version of the Self-Installing User Extensions.
Dialog formatting with Windows XP SP2 [Ref 504041]
If a user with Windows XP with Service Pack 2 used Internet Explorer to view an archived item and then clicked the Restore button, the resulting dialog had a status bar that obscured the buttons.
This has been fixed.
You must install the Enterprise Vault 5.0 SP4 User Extensions in order to obtain this fix.
Archive and restore in Outlook 2003 Search folders [Ref 504036]
There is now a restriction that it is not possible to archive from, or restore to, Outlook 2003 Search folders. These are virtual folders that were introduced in Outlook 2003.
In previous versions of Enterprise Vault, attempting to archive from, or restore to, Outlook 2003 Search folders resulted in the Enterprise Vault Retrieval Service consuming significant processor resources. The only remedy was to stop the service and remove the problem message from the processing queue. Therefore, if you have users with Outlook 2003 you are recommended to install the Enterprise Vault 5.0 SP4 User Extensions.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
OWA and slashes in folder names [Ref 504039]
When using Outlook Web Access, it was not possible to open or preview an archived item if there was a slash ( / ) in the name of the folder that contained the item. Any attempt to view such an item produced a File Not Found error:
HTTP Error 404 - File not found
This has been fixed.
OWA now supports UPN style username [Ref 504089]
USER_PRINCIPAL_NAME (UPN) usernames take the form user@domain.com, as opposed to the NT format, domain\user. If an OWA user logged in with a UPN-style username and attempted to open an archived item, the following error was displayed:
KVS Enterprise Vault - Error
The Enterprise Vault service is not available.
This has been fixed; UPN style usernames are now supported.
Outlook can terminate when using Word as mail editor [Ref 504092]
When using Microsoft Word as a mail editor, or when using a third-party Outlook plug-in to add categories to mail messages, it was possible for Outlook to terminate unexpectedly when sending a message.
This has been fixed.
Outlook terminates when searching from root public folder [Ref 504086]
Outlook would terminate if a user selected the root public folder and then clicked Search Vaults.
This has been fixed.
Viewing large items from search results [Ref 504074]
From search results, it was not possible to open a large item (50MB or greater). Any attempt to do so produced the following error:
Could not show this item. Please try again.
This has been fixed.
Sorting search results by date and time [Ref 504019]
When sorting the results by date, the results are returned sorted by date, but not sorted by time. Thus, within the results for a particular day, the results can be in a seemingly random order.
There is a new DWORD registry value, SortByDateTime, that you can create on the Index Server computer to force results that are sorted by date to be also sorted by time. Create SortByDateTime under the following registry key on the Indexing Service computer:
HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault
The possible values are: 1 to turn on sorting by time, or 0 (the default) to turn off sorting by time.
Note that there will be a performance impact associated with sorting by time, which will become significant when a large number of results is returned.
Restoring from Archive Explorer [Ref 504049]
It was not possible to use Archive Explorer to restore a document that had an ampersand (&) in its file name.
This has been fixed.
Resizing Archive Explorer windows [Ref 504055]
There have been various improvements made to the Archive Explorer window panes. It is now possible to resize the preview pane and to increase the size of the folder list pane.
Missing shortcut text [Ref 504050]
If an item that was archived from a mailbox began with a numeric character, the resulting shortcut did not contain any text.
This has been fixed.
Duplicate copies when archive fails [Ref 504066]
If items were archived from mailboxes with copies being retained in the mailboxes, then a problem with archiving an item could result in the original item being left unarchived in the mailbox together with a duplicate copy.
This has been fixed.
Performance improvement when many users [Ref 504098]
There have been improvements made to user authentication procedures. These will result in a performance improvement for users when there are many users who have access to archived data. The improvement affects all data access, such as using Archive Explorer or viewing items found by a search.
Blank entry in archive list when searching [Ref 504145]
If a user performed a search using the Web Access application, viewed an item, and then selected a new archive to search, it was possible for there to be blank entry in the list of available archives.
This has been fixed.

Administration Console changes
Archive permissions shown incorrectly in Administration Console [Ref 504120]
If archive permissions were synchronized and no account had Full mailbox access permission to the mailbox, then the archive's permissions were incorrectly shown as Manually set permissions instead of Automatically set permissions.
This has been fixed.
File server is inaccessible from Administration Console [Ref 504035]
One customer reported a problem in which computers listed in the File Servers container of the Administration Console showed a status of '(Unknown)' and the Status tab of the a file servers' properties showed 'Access is denied'. (These symptoms can also be caused by incorrectly-registered DLL files but in this particular case the process EVFileSvrArcMngr.exe was present, which would not be there if DLL files had been incorrectly registered.)
This has been fixed.

Policy Manager changes
Policy Manager restrictions [Ref 504103]
The following settings are valid only for the root of a mailbox; they are not valid for mailbox folders:
  • PercentageQuota
  • QMinimumAgeThresholdPeriod
  • QMinimumAgeThresholdUnits
  • QPrioritizeItemsOver
  • QPrioritizeLargeItems
  • UseInactivityPeriod
· In Enterprise Vault 5.0 SP4 these settings are ignored if an attempt is made to set them for mailbox folders. In versions before Enterprise Vault 5.0 SP4 the settings were not ignored, which resulted in errors when attempting to view folder properties.
Setting permissions on all archives in a vault store [Ref 504102]
It is now possible, using Policy Manager, to set access permissions on all the archives in a vault store. You can now use VaultStoreName in the [ArchivePermissions] of a Policy Manager initialization file to set the permissions.
Examples
  • To grant an account named myDomain\auditor read access to all archives in a vault store called myVaultStore:
· [Directory]
DirectoryComputerName=myServer.myDomain.local
SiteName=MyVaultSite
[ArchivePermissions]
VaultStoreName=myVaultStore
GrantAccess = read, myDomain\auditor
  • To grant an account named myDomain\auditor read and write access to all mailbox archives:
· [Directory]
DirectoryComputerName=myServer.myDomain.local
SiteName=MyVaultSite
[ArchivePermissions]
archivename=ALL_MAILBOX
GrantAccess = read write, myDomain\auditor
Setting the billing owner when enabling a mailbox [Ref 504075]
It is now possible to set the billing owner for a mailbox when the mailbox is enabled. To do this, use the BillingOwner setting in the [Folder] section of a Policy Manager initialization file.
Example
  • To enable a mailbox called mailbox1 and make the billing owner be TECH-SUPPORT\mailbox2 :
· [Directory]
DirectoryComputerName=myServer.myDomain.local
SiteName=Enterprise Vault Site
[Mailbox]
DistinguishedName=/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=mailbox1
[Folder]
Name=mailboxroot
Enabled=true
BillingOwner=TECH-SUPPORT\mailbox2
Incorrect LDAP queries when using Policy Manager [Ref 504043]
When using Policy Manager to perform LDAP queries on Exchange Server 5.5, there were incorrect results if the distinguished name (DN) contained a comma.
This has been fixed.

Other changes
PST file marking in Outlook 2003 cached Exchange mode [Ref 504137]
When PST file marking was enabled, PST files were not marked if Outlook 2003 was being used in cached Exchange mode.
This has been fixed. Note, however, that Outlook 2003 must be in 'Connected' mode in order for the marking to take place, even if it is being used in cached Exchange mode.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Changes to NetApp Filer settings are automatically applied [Ref 504108]
Configuration changes made by editing registry values that affect the archiving of existing NetApp Filer devices are now picked up automatically, with no service restarts required. For example, if you configure archiving for another NetApp Filer device and specify that placeholders must be left, this change is recognized automatically.
All changes under the following registry key are automatically recognized:
HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\NetAppPlaceholderService
Note that, when you add the first NetApp Filer device, you must do the following:
1. Add the NetApp Filer using the Enterprise Vault Administration Console.
2. Restart the Enterprise Vault Admin Service on the Storage Service computer.
3. Edit the registry values on the Storage Service computer, as described in the previous updates.
OWA Authentication works correctly in a mixed environment [Ref 504028]
OWA authentication failed when Exchange Server 2003 was installed on a Windows 2000 server.
This has been fixed.
Updated Centera SDK [Ref 504014]
Enterprise Vault has now certified Centera SDK version 2.3.327 (2.3 SP2).
Centera upgrades to CentraStar 2.3 SP3 [Ref 32192]
CentraStar 2.3 SP3 has a new naming convention called "M++". This new naming convention is enabled by default.
If your Centera is upgraded to CentraStar 2.3 SP3 then, to avoid "Content Address mismatch" errors, you must make sure that the M++ naming convention is disabled .
Journal Service Event 2270 [Ref 504007/1]
If a Journal Service logged Event 2270 in the Application Event log, each such entry had a large amount of irrelevant data appended.
This has been fixed
Invalid LegacyExchangeDN values are now ignored [Ref 504007/2]
If a message is addressed to a mailbox that has a invalid (or duplicate) LegacyExchangeDN, the invalid LegacyExchangeDN is now skipped. This can occur when expanding distribution lists during journal mailbox archiving.
Recall limits on NetApp Filer devices [Ref 504114]
On NetApp Filer devices, recalls of files containing multiple streams resulted in the recall limit being reached too soon. This has been fixed.
Changes to placeholders on NetApp Filer devices [Ref 504106]
On NetApp Filer devices new placeholders have changed so that they now show a size of zero bytes, rather than four kilobytes as previously.
Note:
  • The change means that you cannot restore placeholders on NetApp Filer devices that were created using Enterprise Vault 5.0 versions earlier than Service Pack 4. There is no conversion utility to migrate existing placeholders to the new placeholders.
  • The NetApp Filer placeholder functionality has been developed using the beta release of Data ONTAP™ 7.0. If there are changes between the beta release and the final release of Data ONTAP™ 7.0, VERITAS will make changes to support the final release in a future Service Pack.
· Errors with backslashes in folder names on NT4 [Ref 504085]
When using Exchange Server 5.5 on a Windows NT4 server, a backslash ( \ ) in a folder name prevented items in that folder from being archived.
This has been fixed.
Archiving encrypted or opaque-signed SMIME messages [Ref 504081]
When encrypted or opaque-signed SMIME messages were archived, the resulting shortcut had approximately the same size as the original message. This was because the message attachments were not being deleted.
This has been fixed.
Improvements to usage reports [Ref 504033]
It was possible for there to be errors when reports of very large vault stores were generated.
This has been fixed by changing the display totals so that they are shown in megabytes instead of kilobytes.
Index replay when item is deleted [Ref 504032]
If an archived item was deleted and the index was out of date, an automatic index update resulted in informational messages in the Application Event log, such as:
Event 6474
Starting update of Vault Index with Storage transactions from 71431 to 71869
This was fixed in Enterprise Vault 5.0 SP3, but further improvements have been made.
Journaling Service and calendar items [Ref 504150]
The Journaling Service now archives all calendar items, including those that are recurring or have an end date in the future.

Outstanding issues
Error when starting Outlook 2003 [Ref 512 and SRZ040414002287]
The first time a user starts Outlook 2003 after installing the Enterprise Vault User Extensions the following error message may appear:
Error in registry for extension "Exchange Extensions;?".
The syntax or format of the registry entry is incorrect.
Check the registry settings and compare the registry for
this extension to other extensions in the registry.
The error does not appear the next time Outlook 2003 is started.
The registry entry to which the message refers is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\Extensions
The correct value for the entry is:
"4.0;emsuix32.dll;7;011111111111110;1111011100"
The problem is caused by an Outlook 2003 bug which is fixed in Outlook 2003 SP1.
For more details, see Microsoft Support article 823633
File System Archiving placeholder timeouts [Ref 30880]
When a user attempts to open a placeholder shortcut and the item to be restored is large, it is possible that the user's application may assume that the file cannot be opened when in fact the file is still being restored. For example, Microsoft Word may issue the following error:
The document name or path is not valid
The file size at which this occurs depends on the speed at which files are restored. For example, on a LAN this may occur when a file is several tens of megabytes in size.
If the user waits until the file has been restored and then tries again, the file can be opened successfully.

Enterprise Vault™ 5.0 Service Pack 4
This document describes the changes introduced by Enterprise Vault 5.0 Service Pack 4 server & client builds.
For details of the changes included in the earlier updates, see the previous updates.
Contents
  • Installation and prerequisite software
  • File System Archiving changes
  • Offline Vault changes
  • Changes affecting users
  • Administration Console changes
  • Policy Manager changes
  • Other changes
  • Outstanding issues
  • Copyright and trademarks
·
Installation and prerequisite software
Server installation
When you upgrade to Enterprise Vault 5.0 SP4 it is mandatory that you upgrade all Enterprise Vault servers, including OWA front-end and back-end servers.
Simplified OWA configuration [Ref 504059]
Most of the set up required for OWA Extensions has been automated in this release. For details of the new configuration steps, see "Installing and Configuring OWA Extensions" in Enterprise Vault Installing and Configuring.
MAPISVC.INF file version fix [Ref 504042]
If an invalid version of MAPISVC.INF is in the SYSTEM32 folder (normally C:\WINNT\SYSTEM32), a number of Enterprise Vault operations may fail with the error message MAPI-E-NOT-FOUND. In previous releases, this could be fixed by running the program SYSTEM32\FIXMAPI.EXE to update MAPISVC.INF.
In this release, the MAPISVC.INF file is automatically checked and updated, if necessary, by the Enterprise Vault Admin Service. The check is performed when the service starts and repeated at hourly intervals, because other applications may overwrite the file. Before the file is updated, a back-up copy called MAPISVC_ddmmhhmm.EVBK is created in the same folder. ddmmhhmm is the day, month, hour and minute when the back-up was taken.
This automatic check and update process is also performed on Accelerator systems, where Enterprise Vault services are installed but not configured.

File System Archiving changes
Restoring collected files using Archive Explorer [Ref 504054]
It was not possible to use Archive Explorer to restore files that had been archived by File System Archiving and subsequently stored in an NTFS collection.
This has been fixed.
Access permissions for Vault Service Account [Ref 504113]
If the Vault Service Account did not have Local Admin access to a volume or folder that was being processed by File System Archiving, errors such as the following error were logged:
Event Type: Error
Event Source: Enterprise Vault
Event Category: File Archive Server
Event ID: 40966
Date: 12/13/2004
Time: 3:46:24 PM
User: N/A
Computer: DEMO
Description:
A program fault has raised an exception.
Exception:
Object reference not set to an instance of an object.
Diagnostic:
Type: System.NullReferenceException
This has been fixed - the report file now provides information about access problems.
Errors when Vault Service Account has no access permissions [Ref 504116/1 and 504115 and 5040142]
When archiving or creating an archive point, there were Access Denied errors if the Vault Service Account did not have explicit write access permission to the appropriate volume or folder. There could also be errors if the Vault Service Account did have write access but the folder was set to Read-Only. For example, entries such as the following could appear in the Event Log:
Event Type: Error
Event Source: Enterprise Vault
Event Category: File Archive Server
Event ID: 40982
Date: 25/02/2005
Time: 09:36:02
User: N/A
Computer: DEMO
Description:
The Vault Service Account does not have write access
to the volume share: \\demo-2003\c$ or the volume is unavailable,
no items for this volume will be processed
This has been fixed. The Vault Service Account has access provided the account is a member of the Local Administrators group.
Archive Point management[Ref 504132]
It was not possible to use the ArchivePoints tool to specify both archive name and description, as documented in the Administration Console Help topic Archive points: Overriding default attributes.
This has been fixed.
Security fix for File System Archiving folders [Ref 504083]
When using Archive Explorer to view archived folders and files, it was possible for a user who had only List Folder Contents permission to read the contents of files.
This has been fixed.
Performance improvement for internet shortcuts [Ref 504116/2]
The amount of time taken to create an internet shortcut increased as the file size increased, with the result that files of several gigabytes could take minutes to turn into shortcuts.
This has been fixed. Large files now do not suffer a performance penalty.

Offline Vault changes
Offline Archive Explorer [Ref 504121]
When setting up Offline Vault and using offline Archive Explorer with no mailbox shortcuts, Offline Vault would ignore the maximum permitted size of the offline vault and thus could attempt to download items that would not fit in the available space.
This affected only the first download, when the offline vault was being created. On subsequent downloads, older items are automatically deleted as necessary in order to make space for newer items.
This has been fixed. There is now a prompt asking whether or not to increase the size of the offline vault. If the user chooses not to increase the size, no items are downloaded.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Offline Vault space allocation [Ref 504122]
Because of the Offline Vault internal structure, it is possible for an offline vault to be full and yet not have used all the allocated space. There has been an improvement in the internal space allocation within the offline vault, which means that users are much less likely to have this problem.
This improvement applies to new offline vaults only, not to existing offline vaults.
You must install the Enterprise Vault 5.0 SP4 User Extensions in order to benefit from this improvement.
Offline Vault settings [Ref 504119]
Some new settings have been added to Desktopsettings.txt, providing you with finer control of the Offline Vault behavior:
OVRootDirectorySearchPath: Controls the location of the offline vault.
Enables you to supply a list of possible locations for the offline vault. The first such location that is valid on a user's computer is the one that will be used at the time the offline vault is created. This enables you to specify a list that is likely to be suitable for computers with different configurations.
For example, if you specify: E:\vault;C:\vault then the offline vault would be created in E:\vault if that was valid on the user's computer, and if it was not valid, then it would be created in C:\vault. If none of the locations in OVRootDirectorySearchPath is valid, the one specified by OVRootDirectory is used, if possible.
Possible values: A semi-colon separated list of folder paths
OVDownloadItemAgeLimit: Specifies the maximum age of an item that will be downloaded to the offline vault by default.
For example, specifying 365 (days) means that items up to one year old will be downloaded by default. Items older than this will be downloaded only if the user requests them.
Possible values: An integer indicating the maximum age in days.
Each of these settings has a corresponding registry entry that you can set to control the behavior on individual client computers. Create the registry entries under the following registry key:
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client
The possible registry entries are:
  • OVRootDirectorySearchPath (a string entry)
  • OVDownloadItemAgeLimit (a DWORD entry)
· Offline Vault downloads [Ref 504095]
Under some conditions, items were being ignored that should have been automatically added to the offline vault before they were eligible for archive. This meant that, after those items had been archived from the mailbox, they would be downloaded into the offline vault.
This has been fixed.
Offline Vault automatic updates [Ref 504090]
If a user had offline Archive Explorer and a problem occurred during a download to the offline vault, subsequent downloads did not take place.
This has been fixed.
Offline Vault error [Ref 504088]
When using Offline Vault with Windows 2000, it was possible under some circumstances to receive an error that began with the following text:
Conflicting edits have been made to the same message.
The different versions of the message appear below.
To resolve this conflict, do one of the following:
This has been fixed.

Changes affecting users
Note that PST file marking in Outlook 2003 cached Exchange mode, listed under "Other Changes", also requires you to install the Enterprise Vault 5.0 SP4 User Extensions even though it has no direct effect on users.
Archive Explorer 'Next' and 'Previous' buttons [Ref 504160]
When using Archive Explorer with Outlook 2003 in cached Exchange mode, clicking on the toolbar Next or Previous buttons caused Outlook to terminate.
This has been fixed.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Manual archiving when in Outlook 2003 cached Exchange mode [Ref 504153]
When performing a manual archive using the Enterprise Vault User Extensions, it was possible for a user to change the selection before the archive operation was complete. This then resulted in the wrong items being archived.
This problem did not affect the Self-Installing User Extensions.
This has been fixed.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Incorrect view in Archive Explorer [Ref 504151 and 504140]
When using Archive Explorer, clicking the Sent Items folder correctly showed a view of Sent Items, but the first column was From rather than To.
This has been fixed.
Empty error when searching [Ref 504047]
Under some circumstances, it was possible for a user who attempted to search for items to be shown an error message that contained no text.
This has been fixed.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Archiving from subfolders [Ref 504109]
Using the Self-Installing User Extensions, it was not possible to archive an item from a subfolder of the mailbox root, or from a subfolder of one of the special folders, such as Inbox.
This has been fixed.
In order to obtain the fix, you must install the Enterprise Vault 5.0 SP4 version of the Self-Installing User Extensions.
Dialog formatting with Windows XP SP2 [Ref 504041]
If a user with Windows XP with Service Pack 2 used Internet Explorer to view an archived item and then clicked the Restore button, the resulting dialog had a status bar that obscured the buttons.
This has been fixed.
You must install the Enterprise Vault 5.0 SP4 User Extensions in order to obtain this fix.
Archive and restore in Outlook 2003 Search folders [Ref 504036]
There is now a restriction that it is not possible to archive from, or restore to, Outlook 2003 Search folders. These are virtual folders that were introduced in Outlook 2003.
In previous versions of Enterprise Vault, attempting to archive from, or restore to, Outlook 2003 Search folders resulted in the Enterprise Vault Retrieval Service consuming significant processor resources. The only remedy was to stop the service and remove the problem message from the processing queue. Therefore, if you have users with Outlook 2003 you are recommended to install the Enterprise Vault 5.0 SP4 User Extensions.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
OWA and slashes in folder names [Ref 504039]
When using Outlook Web Access, it was not possible to open or preview an archived item if there was a slash ( / ) in the name of the folder that contained the item. Any attempt to view such an item produced a File Not Found error:
HTTP Error 404 - File not found
This has been fixed.
OWA now supports UPN style username [Ref 504089]
USER_PRINCIPAL_NAME (UPN) usernames take the form user@domain.com, as opposed to the NT format, domain\user. If an OWA user logged in with a UPN-style username and attempted to open an archived item, the following error was displayed:
KVS Enterprise Vault - Error
The Enterprise Vault service is not available.
This has been fixed; UPN style usernames are now supported.
Outlook can terminate when using Word as mail editor [Ref 504092]
When using Microsoft Word as a mail editor, or when using a third-party Outlook plug-in to add categories to mail messages, it was possible for Outlook to terminate unexpectedly when sending a message.
This has been fixed.
Outlook terminates when searching from root public folder [Ref 504086]
Outlook would terminate if a user selected the root public folder and then clicked Search Vaults.
This has been fixed.
Viewing large items from search results [Ref 504074]
From search results, it was not possible to open a large item (50MB or greater). Any attempt to do so produced the following error:
Could not show this item. Please try again.
This has been fixed.
Sorting search results by date and time [Ref 504019]
When sorting the results by date, the results are returned sorted by date, but not sorted by time. Thus, within the results for a particular day, the results can be in a seemingly random order.
There is a new DWORD registry value, SortByDateTime, that you can create on the Index Server computer to force results that are sorted by date to be also sorted by time. Create SortByDateTime under the following registry key on the Indexing Service computer:
HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault
The possible values are: 1 to turn on sorting by time, or 0 (the default) to turn off sorting by time.
Note that there will be a performance impact associated with sorting by time, which will become significant when a large number of results is returned.
Restoring from Archive Explorer [Ref 504049]
It was not possible to use Archive Explorer to restore a document that had an ampersand (&) in its file name.
This has been fixed.
Resizing Archive Explorer windows [Ref 504055]
There have been various improvements made to the Archive Explorer window panes. It is now possible to resize the preview pane and to increase the size of the folder list pane.
Missing shortcut text [Ref 504050]
If an item that was archived from a mailbox began with a numeric character, the resulting shortcut did not contain any text.
This has been fixed.
Duplicate copies when archive fails [Ref 504066]
If items were archived from mailboxes with copies being retained in the mailboxes, then a problem with archiving an item could result in the original item being left unarchived in the mailbox together with a duplicate copy.
This has been fixed.
Performance improvement when many users [Ref 504098]
There have been improvements made to user authentication procedures. These will result in a performance improvement for users when there are many users who have access to archived data. The improvement affects all data access, such as using Archive Explorer or viewing items found by a search.
Blank entry in archive list when searching [Ref 504145]
If a user performed a search using the Web Access application, viewed an item, and then selected a new archive to search, it was possible for there to be blank entry in the list of available archives.
This has been fixed.

Administration Console changes
Archive permissions shown incorrectly in Administration Console [Ref 504120]
If archive permissions were synchronized and no account had Full mailbox access permission to the mailbox, then the archive's permissions were incorrectly shown as Manually set permissions instead of Automatically set permissions.
This has been fixed.
File server is inaccessible from Administration Console [Ref 504035]
One customer reported a problem in which computers listed in the File Servers container of the Administration Console showed a status of '(Unknown)' and the Status tab of the a file servers' properties showed 'Access is denied'. (These symptoms can also be caused by incorrectly-registered DLL files but in this particular case the process EVFileSvrArcMngr.exe was present, which would not be there if DLL files had been incorrectly registered.)
This has been fixed.

Policy Manager changes
Policy Manager restrictions [Ref 504103]
The following settings are valid only for the root of a mailbox; they are not valid for mailbox folders:
  • PercentageQuota
  • QMinimumAgeThresholdPeriod
  • QMinimumAgeThresholdUnits
  • QPrioritizeItemsOver
  • QPrioritizeLargeItems
  • UseInactivityPeriod
· In Enterprise Vault 5.0 SP4 these settings are ignored if an attempt is made to set them for mailbox folders. In versions before Enterprise Vault 5.0 SP4 the settings were not ignored, which resulted in errors when attempting to view folder properties.
Setting permissions on all archives in a vault store [Ref 504102]
It is now possible, using Policy Manager, to set access permissions on all the archives in a vault store. You can now use VaultStoreName in the [ArchivePermissions] of a Policy Manager initialization file to set the permissions.
Examples
  • To grant an account named myDomain\auditor read access to all archives in a vault store called myVaultStore:
· [Directory]
DirectoryComputerName=myServer.myDomain.local
SiteName=MyVaultSite
[ArchivePermissions]
VaultStoreName=myVaultStore
GrantAccess = read, myDomain\auditor
  • To grant an account named myDomain\auditor read and write access to all mailbox archives:
· [Directory]
DirectoryComputerName=myServer.myDomain.local
SiteName=MyVaultSite
[ArchivePermissions]
archivename=ALL_MAILBOX
GrantAccess = read write, myDomain\auditor
Setting the billing owner when enabling a mailbox [Ref 504075]
It is now possible to set the billing owner for a mailbox when the mailbox is enabled. To do this, use the BillingOwner setting in the [Folder] section of a Policy Manager initialization file.
Example
  • To enable a mailbox called mailbox1 and make the billing owner be TECH-SUPPORT\mailbox2 :
· [Directory]
DirectoryComputerName=myServer.myDomain.local
SiteName=Enterprise Vault Site
[Mailbox]
DistinguishedName=/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=mailbox1
[Folder]
Name=mailboxroot
Enabled=true
BillingOwner=TECH-SUPPORT\mailbox2
Incorrect LDAP queries when using Policy Manager [Ref 504043]
When using Policy Manager to perform LDAP queries on Exchange Server 5.5, there were incorrect results if the distinguished name (DN) contained a comma.
This has been fixed.

Other changes
PST file marking in Outlook 2003 cached Exchange mode [Ref 504137]
When PST file marking was enabled, PST files were not marked if Outlook 2003 was being used in cached Exchange mode.
This has been fixed. Note, however, that Outlook 2003 must be in 'Connected' mode in order for the marking to take place, even if it is being used in cached Exchange mode.
In order to obtain this fix, you must install the Enterprise Vault 5.0 SP4 User Extensions.
Changes to NetApp Filer settings are automatically applied [Ref 504108]
Configuration changes made by editing registry values that affect the archiving of existing NetApp Filer devices are now picked up automatically, with no service restarts required. For example, if you configure archiving for another NetApp Filer device and specify that placeholders must be left, this change is recognized automatically.
All changes under the following registry key are automatically recognized:
HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\NetAppPlaceholderService
Note that, when you add the first NetApp Filer device, you must do the following:
1. Add the NetApp Filer using the Enterprise Vault Administration Console.
2. Restart the Enterprise Vault Admin Service on the Storage Service computer.
3. Edit the registry values on the Storage Service computer, as described in the previous updates.
OWA Authentication works correctly in a mixed environment [Ref 504028]
OWA authentication failed when Exchange Server 2003 was installed on a Windows 2000 server.
This has been fixed.
Updated Centera SDK [Ref 504014]
Enterprise Vault has now certified Centera SDK version 2.3.327 (2.3 SP2).
Centera upgrades to CentraStar 2.3 SP3 [Ref 32192]
CentraStar 2.3 SP3 has a new naming convention called "M++". This new naming convention is enabled by default.
If your Centera is upgraded to CentraStar 2.3 SP3 then, to avoid "Content Address mismatch" errors, you must make sure that the M++ naming convention is disabled .
Journal Service Event 2270 [Ref 504007/1]
If a Journal Service logged Event 2270 in the Application Event log, each such entry had a large amount of irrelevant data appended.
This has been fixed
Invalid LegacyExchangeDN values are now ignored [Ref 504007/2]
If a message is addressed to a mailbox that has a invalid (or duplicate) LegacyExchangeDN, the invalid LegacyExchangeDN is now skipped. This can occur when expanding distribution lists during journal mailbox archiving.
Recall limits on NetApp Filer devices [Ref 504114]
On NetApp Filer devices, recalls of files containing multiple streams resulted in the recall limit being reached too soon. This has been fixed.
Changes to placeholders on NetApp Filer devices [Ref 504106]
On NetApp Filer devices new placeholders have changed so that they now show a size of zero bytes, rather than four kilobytes as previously.
Note:
  • The change means that you cannot restore placeholders on NetApp Filer devices that were created using Enterprise Vault 5.0 versions earlier than Service Pack 4. There is no conversion utility to migrate existing placeholders to the new placeholders.
  • The NetApp Filer placeholder functionality has been developed using the beta release of Data ONTAP™ 7.0. If there are changes between the beta release and the final release of Data ONTAP™ 7.0, VERITAS will make changes to support the final release in a future Service Pack.
· Errors with backslashes in folder names on NT4 [Ref 504085]
When using Exchange Server 5.5 on a Windows NT4 server, a backslash ( \ ) in a folder name prevented items in that folder from being archived.
This has been fixed.
Archiving encrypted or opaque-signed SMIME messages [Ref 504081]
When encrypted or opaque-signed SMIME messages were archived, the resulting shortcut had approximately the same size as the original message. This was because the message attachments were not being deleted.
This has been fixed.
Improvements to usage reports [Ref 504033]
It was possible for there to be errors when reports of very large vault stores were generated.
This has been fixed by changing the display totals so that they are shown in megabytes instead of kilobytes.
Index replay when item is deleted [Ref 504032]
If an archived item was deleted and the index was out of date, an automatic index update resulted in informational messages in the Application Event log, such as:
Event 6474
Starting update of Vault Index with Storage transactions from 71431 to 71869
This was fixed in Enterprise Vault 5.0 SP3, but further improvements have been made.
Journaling Service and calendar items [Ref 504150]
The Journaling Service now archives all calendar items, including those that are recurring or have an end date in the future.

Outstanding issues
Error when starting Outlook 2003 [Ref 512 and SRZ040414002287]
The first time a user starts Outlook 2003 after installing the Enterprise Vault User Extensions the following error message may appear:
Error in registry for extension "Exchange Extensions;?".
The syntax or format of the registry entry is incorrect.
Check the registry settings and compare the registry for
this extension to other extensions in the registry.
The error does not appear the next time Outlook 2003 is started.
The registry entry to which the message refers is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\Extensions
The correct value for the entry is:
"4.0;emsuix32.dll;7;011111111111110;1111011100"
The problem is caused by an Outlook 2003 bug which is fixed in Outlook 2003 SP1.
For more details, see Microsoft Support article 823633
File System Archiving placeholder timeouts [Ref 30880]
When a user attempts to open a placeholder shortcut and the item to be restored is large, it is possible that the user's application may assume that the file cannot be opened when in fact the file is still being restored. For example, Microsoft Word may issue the following error:
The document name or path is not valid
The file size at which this occurs depends on the speed at which files are restored. For example, on a LAN this may occur when a file is several tens of megabytes in size.
If the user waits until the file has been restored and then tries again, the file can be opened successfully.

Password for the zip file is "administrationconsole"

Attachments

ev50_en_client_276035.zip (1.7 MBytes)


Legacy ID



276035


Article URL http://www.symantec.com/docs/TECH38048


Terms of use for this information are found in Legal Notices