Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Archiving and eDiscovery Community Blog
Showing posts tagged with Enterprise Vault
Showing posts in English
Rob.Wilcox | 04 Nov 2013 | 3 comments
I helped a colleague with this just the other day, and it's quite interesting.  The issue was that the Enterprise Vault Indexing Service on his Enterprise Vault 10 server would not start. He would get a pop-up saying that the service started, then immediately stopped.  I had a quick look at the event log on the server, and spotted this:
Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          30.10.2013 14:50:18

Event ID:      41299

Task Category: Index Admin Service

Level:         Information

Keywords:      Classic

User:          N/A



The Indexing Service is pending initialization.

Requesting additional time for initialization routines....
Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          30.10.2013 14:50:39

Event ID:      41293

Task Category: Index...
Rob.Wilcox | 30 Oct 2013 | 0 comments

Using Enterprise Vault for File System Archiving is something that I still sometimes get involved in, in my post Symantec career. It doesn't crop up all that often, and, most times I get involved I learn something new. Something that cropped up on the Symantec Connect Forums a few days ago is something that I saw on one of my environments a few weeks ago.

The issue relates to results when performing a search.

I still use a rough old Windows XP workstation to do most of my testing on, since it is pretty quick in a Virtual Machine. So I hit an issue where I was searching for a file that I knew was archived, but no results were coming back when I searched based on the name of the file.

Low and behold it is a known issue, and document in this technote.

This is what I did:


You see some files with the word OFFLINE in their name.

And then I...

Rob.Wilcox | 27 Oct 2013 | 1 comment

FSARunNow is perhaps a long forgotten about utility, but it's actually pretty hand in some situations. What does it do? Well, as the name suggests it runs an FSA 'task' or 'operation' now. This bypasses any schedule that might be defined and simply starts things going right now. That to me makes it quite handy.

You can run FSARunNow in a number of different modes, perhaps the simplest one is to get the utility to just run a simple pre-defined archiving task. To do that you would execute:

FSARUNNOW Archive "The name of the task that you see in the Vault Admin Console"

Simple, yet powerful!

Rob.Wilcox | 24 Oct 2013 | 0 comments

A topically conversation today - Outlook on the Enterprise Vault server.  As everyone knows Outlook is needed on the Enterprise Vault server in order to perform mailbox archiving. For quite some time Outlook 2003 was the de-facto on the server, but that has progressed to Outlook 2007 with Service Pack 3 and some hotfixes.  

The question that gets asked a lot is whether Outlook 2010 or Outlook 2013 can be used.

The answer is - No.

They are not supported on the server.

As with all these sorts of things the bible for knowing what is supported, and in which combinations is the Compatibility List, and in this particular case, refer to this section:

Screenshot 2013-10-24 10.13.24.png

Eileen | 17 Oct 2013 | 0 comments

For information on the on Service Impact Level Definitions and Response Times please download the attached document.

Rob.Wilcox | 16 Oct 2013 | 0 comments

Hot off the presses comes an Enterprise Vault 10.0.4 Cumulative Hotfix. The first since the release of Enteprise Vault 10.0.4 a few months ago.  A technote has been created which lists the changes:

The download is close to 150 Mb.  It is always worth testing such a fix in a lab environment. I've written before why you should have your own lab environment, and this is exactly one of those reasons :)

Rob.Wilcox | 13 Oct 2013 | 0 comments

I find many of the Sysinternals tools invaluable when it comes to looking after even a bunch of test machines in a lab, or two, or three.  I spotted last week that a few of the tools have been given a brush up, so head over to:

Process Explorer is a superb tool when it comes to watching what various Enterprise Vault server based processes are loading which DLL's from which folders when they're performing operations.  If you've never used the tools before head over to take a look.

InsentraCameronM | 10 Oct 2013 | 0 comments

Files can be exported from archives to PSTs using the EV web search app. This is especially useful for Exchange Public Folder archives since there is no way to export to PST from the Vault Admin Console.

  1. Add a file called webapp.ini to the root of the Enterprise Vault server's installation folder.

  2. Add one of the following entries into webapp.ini:

    1. RestoreToPSTOption=All

    2. RestoreToPSTOption=domain\user

  3. Save webapp.ini

  4. Restart IIS (not necessary with Server 2008 R2 and IIS 7.5).

    1. Open a command line and type iisrest

  5. Open the EV search app: http://evservername/enterprisevault/search.asp, where evservername is the name of your EV server.

  6. Choose an archive, enter your search criteria and click Search.

  7. Either click Add to Basket or Restore all...

EC at TW | 09 Oct 2013 | 0 comments

We had a number of cases of this logged on one of our servers. I checked the forums and tech notes, found and started to investigate.

The messages looked OK but the issue in our case was caused by the Exchange mailbox and quotas. The mailbox was enabled for Retention Hold and it had hit Database Quota Default (RecoverableItemsQuota)

Nothing could be archived (removed from the mailbox) as nothing could be added to the mailbox database.

Quick removal of the quota (Set-Mailbox alias -UseDatabaseQuotaDefaults $false) and archiving resumed. Obviously the quota issue needs addressing.

Rob.Wilcox | 08 Oct 2013 | 0 comments
Many organisations end up running several different versions of Microsoft Office on different laptops and desktops. Sometimes it is the need to maintain a particular version because of legacy apps that require the particular version,  or would need significant re-writes or updates in order to use a new version of Office.  I can understand that, though I don't agree with it :)  With that in mind though, do you have just one Enterprise Vault Outlook Add-in version deployed across the board, or multiple? Do you need to have an older version of Add-in because of a clash between a different Outlook Add-in and the Enterprise Vault one?
Personally I'm all for deploying 'one' version, but I know that there reasons why organisations might end up with more than one - I just wondered how frequently multiple versions were deliberately deployed.