Video Screencast Help
Search Video Help Close Back
to help

Archiving and eDiscovery Community Blog

Showing posts in English
Rob.Wilcox | 23 Jun 2010 | 2 comments

If you use Outlook 2007 on your Enterprise Vault Server you might notice occasional “odd” MAPI errors.

If you do then you might fall in to the realm of this article :

http://seer.entsupport.symantec.com/docs/351405.htm

Essentially Outlook 2007 introduced a limit to the number of objects/sessions it would support.  This limit is 32, well, strictly it’s a 4 Kb block of memory.  The processes and threads in Enterprise Vault use these sessions, and you can get odd connection errors when threads try to do MAPI activity as your approach and “break” the limit.  You get an event like this one logged in the event log :

3880002            11:02:51.217     [8500]  (MigratorServer)    ...

Rob.Wilcox | 22 Jun 2010 | 0 comments

Sometimes people want to mark messages in Outlook as Do Not Archive.  This functionality exists in the Enterprise Vault Outlook Addin.  Here is what you can do :

Firstly you have to be using the full client, not the HTTP client.  Note: I have not tried DCOMOverrideRPCHTTP.

If you use the full client, you get to the “Do Not Archive” checkbox as follows, depending on your Outlook version :

Outlook 2007

Open the item, by double clicking on it.

Click on the Office symbol at the top left of the item :

 

And then click on Properties

Lastly you’ll see the checkbox, on the Enterprise Vault tab :

 

Outlook 2003

You get to the same dialog by opening the item, and...

Rob.Wilcox | 21 Jun 2010 | 1 comment

A new check added to Enterprise Vault 8 Service Pack 3 is around OUTLVBS.DLL.  Our forms don’t work without this DLL, so it’s kind of important.  If you using the Outlook Addin from EV 8 SP 3 or later, and OUTLVBS.DLL can not be found in the same folder as Outlook.exe, then you will see the following pop-up.

A “quick way” to correct this is to copy the .DLL from another machine to the same folder as Outlook.exe, and restart Outlook.  That should fix it.  There are of course other methods, which may be listed on Microsoft’s knowledgebase.

Rob.Wilcox | 21 Jun 2010 | 0 comments

Rather than archiving everything in every single mailbox that Enterprise Vault encounters, some customers configure what I would term “elective archiving”.  By this I mean that by default nothing is archived in an end-users mailbox, except things in one particular folder.  If this is something that fits your business requirements, read on.

EVPM becomes your friend in order to accomplish the goal here.  You have to use EVPM to set the overall mailbox to “Do not archive”, and then to mark/make a particular folder as archivable.  Here is an example of the EVPM script you might use :

 

[Directory]
directorycomputername=evault1
sitename=EV Site 1

[Filter]
name = filterA
CreateShortcut=true
DeleteOriginal = true
unreadMail = true
UseInactivityPeriod = true
InactivityUnits = days
InactivityPeriod = 0
UsePercentageQuota = false

...
Rob.Wilcox | 21 Jun 2010 | 0 comments

One of the things that I almost always forget is what version numbers relate to which versions of Exchange server.

In Exchange 2003 we have :-

6944.4 Exchange 2003 RTM

7226.6 Exchange 2003 SP 1

7638.2 Exchange 2003 SP 2

It is also worth noting that Exchange 2003 base release is supported for Enterprise Vault *archiving*, but Outlook Web Access isn’t supported until Exchange 2003 SP 1 is applied.

Rob.Wilcox | 16 Jun 2010 | 0 comments


I’ve seen several articles on the internet which list Exchange 2000 version information, others that list Exchange 2003 version information, but I’ve been searching for a while for a listing of ALL the versions.

Here some of the individual versions :

Exchange 2000

http://www.petri.co.il/what%27s_my_e2k_sp_version.htm

4417.5 = Exchange 2000 RTM

4629.1 = SBS 2000 Exchange 2000

4712.7 = Exchange 2000 SP1

5762.4 = Exchange 2000 SP2

6249.4 = Exchange 2000 SP3

6396.1 = Exchange 2000 Post-SP3 Super Roll-up

63xx/64xx = Exchange 2000 Post-SP3 Hotfixes

Exchange 2003

...

Rob.Wilcox | 16 Jun 2010 | 0 comments


You can use Log Parser for a huge variety of things, including looking at Enterprise Vault data.

Grab a copy from :

http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=en

After installing that you can write some fairly powerful queries rapidly.  Here are a couple of examples :-

LogParser.exe -i:EVT -o:CSV "select DISTINCT ComputerName,EventLog,EventID,EventTypeName,EventCategoryName,SourceName,Strings,Message into C:\testev1.csv FROM '\\evault1\Symantec Enterprise Vault' WHERE (EventTypeName = 'Error event' AND EventID NOT IN(13360;6796)

And

LogParser.exe -i:EVT -o:CSV "select DISTINCT...

Rob.Wilcox | 16 Jun 2010 | 0 comments

You can change the sort order which is used when results are returned to the Outlook Integrated Search of Enterprise Vault.  Normally you get something back like this :

You see the dates are in a bit of a random order there.  Most people are used to trying to think of findings things “around” a particular date, so you can change it so that the default sort order is date.

Create or edit webapp.ini on your Enterprise Vault server, in the Enterprise Vault program folder (not a unicode file) and add a line :

DefaultRankResults=-date

The results then look like this :

 


Much better for most users!

There is a comprehensive list of what you can put for the sort order in the Administrators Guide.  Search in there for webapp.ini, and you’ll see...

Rob.Wilcox | 15 Jun 2010 | 0 comments

There are many uses for Process Monitor, the former Sysinternals tool, now developed at Microsoft.  One such use is to see which process or executable loaded a particular DLL – and what version it is.

First of all you can get Process Monitor from this link :

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

You can run the binary on either an x86 or x64 system.  When you run it on an x64 system, an x64 .exe is actually spawned from inside the x86 version – which is quite neat.

The main interface looks like this :

You’ll see all sorts of useful information such as who the binaries belongs to, process ID’s, memory usage (private byes), CPU usage and so on.

You...

Rob.Wilcox | 15 Jun 2010 | 1 comment

Prior to Enterprise Vault 8 SP 4, if you tried to install the Vault Administration Console on a Windows 7 client machine, the installation goes through checking the pre-reqs, but installation stops with the following shown in Deployment Scanner :

With Enterprise Vault 8 SP 4, you can now install the VAC, and it works quite nicely. 

Note: It has actually worked since 8 SP 3, but “officially” the Windows 7 support was released with EV 8 SP 4.