Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Archiving and eDiscovery Community Blog
Showing posts in English
StephenConnolly | 01 Dec 2011 | 5 comments

In September 2011 Enterprise Vault adopted a new Digital Certificate for signing files. This certificate's root certificate is Verisign Class 3 Public Primary Certification Authority G5. Most systems that have an internet connection will get this certificate via an automatic update, but if that doesn't happen then you will get an error like this in the installation log when you attempt to install the FSA agent on that system:

DIFXAPP: ERROR: Signature verification
failed while checking integrity of driver package 'evmf.inf'
('C:\EV_Install\drivers\evmf.inf').

If you check the MSI package's digital signature on the target file server, you will see that the root certificate cannot be found on the local system.

To address the problem you will need to install the new root certificate on the file server. For more details about how to obtain the certificate, see the...

Rob.Wilcox | 01 Dec 2011 | 0 comments

 

I know that there are some customers out there which use HTTPS in their Enterprise Vault environment, for all communication (not just RPC/HTTP, aka Outlook Anywhere).

An issue was uncovered by one of our developers the other day where this will cause problems with the Enterprise Vault Outlook Addin if the Addin is upgraded to 9.0.3.  The specific problems are :-

* Unable to synchronise Vault Cache

* Unable to retrieve items

Right now this is just a heads-up, I'm sure there will be more on this in the next few days.

Rob.Wilcox | 01 Dec 2011 | 0 comments

 

Everyday is a school day!

On the forums the other day a colleague asked if there was a way of limiting, or rather –extending- the number of archives which are returned when you do an Export Archive from the VAC, and choose ‘List All’. The default is that you get 10,000 back. They wanted more.

I didn’t think there was a way of doing that, but there is !

Way back in EV 5 times a registry key was added, and documented :

HKEY_LOCAL_MACHINE
Software
KVS
Enterprise Vault
AdminService
MSMQ Queue

STRING: MaxArchivesToFind 

You can tell how old it is because the key is a STRING not a DWORD.. and unfortunately it’s documented incorrectly, it is in fact :

HKEY_LOCAL_MACHINE
Software
KVS
Enterprise Vault
Admin
MSMQ Queue

STRING: MaxArchivesToFind 

Rob.Wilcox | 30 Nov 2011 | 9 comments

 

For the people out there who still have Windows XP deployed, it is worth noting that you can’t install the Enterprise Vault Outlook Addin (Version 9.0.3) on XP SP 2 or lower.  The minimum required version is Windows XP SP 3.  It is shown in the Release Notes :

 

Service Pack 3 is the new minimum version of Windows XP [Ref 90310584]

Windows XP SP3 is the new minimum version that is supported for use with the following:

The Enterprise Vault Outlook Add-Ins
A standalone Enterprise Vault Administration Console

 

… but it didn’t make the latest Compatibility Charts (Don’t worry, I’ve already submitted a bug for that !)

 

Small correction: Including the EV Outlook Add-in version number.

Rob.Wilcox | 30 Nov 2011 | 0 comments

 

One of the things mentioned in the Enterprise Vault 9.0.3 Release Notes is that a change has been introduced with regards to Exchange Over Quota archiving issues.  Traditionally the ‘issue’ is that when the mailbox is bumped right up on to the send/receive quota when the mailbox is synchronised, the current policy/desktop settings were removed… but because we’re right at the quota limit, we couldn’t then add a new message to the mailbox, with the ‘new’ (often unchanged) settings in it.

 

Net result is that when the user next logged in to Outlook it would appear that they weren’t enabled – they’ve had no EV buttons.

This has now been fixed so that the new policy settings are written, and saved, and if successful, the old policy settings-messages are removed.  If the save is unsuccessful, then a new event is logged :

 

Event Type: Error

...

Rob.Wilcox | 30 Nov 2011 | 0 comments

 

Prior to Enterprise Vault 9.0.1 when you deleted an archived item, and it’s associated shortcut the shortcut was deleted to the Deleted Items folder.  This has the sometimes undesirable effect that people could go to the deleted items folder in Outlook, and drag-and-drop the shortcut  back in to the mailbox.  For a while the item might then work, and be retrievable.  So where is the undesirable bit?  Of course this is based on a false – hope, since the item in EV is in the EV dumpster, and after 14 days (by default) it will be removed from there, meaning that the shortcut will then be orphaned.  A user trying to open it will get just the shortcut, not the full item.  This is not good.

This lead to many a long hour spent by help desks and by Symantec Support in trying to track down what happened.  It is pretty hard to prove conclusively that this is what has happened because of course it’s all non-...

Rob.Wilcox | 28 Nov 2011 | 0 comments

 

Available any time soon from FileConnect is Enterprise Vault 9.0.3.  There are a huge number of changes in this release, including :-

* FIPS Compliance

* IPv6 Support

* Updated ‘Converters’

* MAPI improvements

* Over (Exchange Mailbox)-quota improvements

* Backtrace

* Client trace and and event log improvements

 

I’ll write a little more about some of the above in future blog entries, so stay tuned.

 

Read more about it here :-

http://www.symantec.com/docs/TECH147782
http://www.symantec.com/docs/TECH147783

Glenn Martin | 24 Nov 2011 | 0 comments

A question that quite often comes up from customers and partners when we release a new version of the product, as we did a few months ago with V10, is "when will you stop supporting version x y or z". This is actually a very easy question to answer because Symantec has a clear policy on our approach to product support life cycle.

You can read the full policy from this link but in summary there are really three main stages involved as part of the product life cycle.

1) Release Date - obviously the official first released date of the product version

2) End of Engineering Support = the date after which we will issue no more patches or fixes

3) End of Assisted Support = the date after which we will no longer accept support calls for the product version

You can look up the particular...

KarlW | 24 Nov 2011 | 4 comments

As many of you are well aware through recent Microsoft Blog postings, the Connect forum and the Symantec KB Article 16949 there is an issue with space not being reclaimed by the Exchange 2010 store when objects are deleted or truncated.  This impacts many scenarios some of which are prevalent when archiving.

Before we get into too much detail here's the good news - Microsoft have fixed this issue and it's available on request.  For the fix go to http://support.microsoft.com/kb/2621266 .

This is an interim update (IU) and will hopefully be made available in an upcoming Rollup Update (RU) for Exchange Server 2010 SP2.  There are something's to note for the fix, once installed it won't magically reclaim all space, there are undefined deletion thresholds that have...

Rob.Wilcox | 18 Nov 2011 | 0 comments

 

I spotted an interesting article this morning :

http://www.symantec.com/business/support//index?page=content&id=HOWTO32552

In the article it explains how to setup a sort of minimalist Virtual Vault and Vault Cache. 

I like the article, however, I would add two pinches of salt :

* MDC / Metadata cache can be large

Remember regardless of the size limits you put down for disk space, or the number of months worth of data you want to keep, or the policy shown in the article around not storing any content locally – you always get a full MDC file for each archive you have opted to synchronise.

That can be large.

Mine is just under 1.6Gb.

* Consider load on the EV Server

One of the things that can really hammer an Enterprise Vault server if allowed to happen is retrieving content for items in Virtual...