Video Screencast Help
Search Video Help Close Back
to help

Archiving and eDiscovery Community Blog

Showing posts in English
Rob.Wilcox | 24 Oct 2012 | 0 comments

 

Many people in the Enterprise Vault administration world have heard of an MDC file.  Not everyone knows what it is though..  or what it looks like.  Below I’ll explain and show you.

The MDC file is the Metadata Cache file.  It contains mail messages, these resemble your archived items, but they’re not ‘quite’ the same.  Essentially the folder structure will follow the structure of your archive, and the mails are actually stubs, containing only some of the message metadata, and a short snippet of the message body (no attachments etc).  Another way to look at it is that is your Virtual Vault.  Obviously the Enterprise Vault Outlook Add-in has lots of code in it which manipulates these items, and presents them to you in such a way that they can seamlessly be your ‘full’ archived items, metadata, attachments and all.

The screenshot below shows you an example of the file...

Rob.Wilcox | 21 Oct 2012 | 0 comments

 

An interesting registry key which not many people know about for the Enterprise Vault Outlook Add-in is theDeleteHiddenMsgBtnVisible setting.

When the key is added to

HKEY_CURRENT_USER \ Software \ KVS \ Enterprise Vault \ Client, and as a DWORD set to 1, then a new, hidden option is enabled.

This is the option to delete the hidden message, if found, on a folder by folder basis.  It can often be done instead of ‘zapping’ the mailbox, which is something which is done all too often.

The reason for deleting the hidden message is that sometimes it gets out of synch between the end user in Outlook cached mode, versus the online copy of the hidden message (which is what Enterprise Vault writes to)

Here is the Vault Information dialog before the registry key is added:

...

Rob.Wilcox | 17 Oct 2012 | 0 comments

One of the common questions when it comes to archiving of Exchange messages with Enterprise Vault is which date attribute is used when searching ..  well the answer is in the following technote:

TECH198491

Hope that proves helpful to you.

Chau Tran | 14 Oct 2012 | 3 comments

Hi All,

You may or may not be aware that Microsoft is discontinuing ISA and TMG and a few MS Frorefront products:

http://blogs.technet.com/b/server-cloud/archive/2012/09/12/important-changes-to-forefront-product-roadmaps.aspx

I wrote this doc purely because EV OWA needs migrating from ISA/TMG to UAG.

Hope it's useful to all.

Regards,

Chau

Kristi Davis | 13 Feb 2013 | 5 comments

Check out the following 'How To' Videos.

How to Remove an Exchange Server from Enterprise Vault
Take a look at this video based on article TECH50256.

Enterprise Vault Exchange 2013 OWA Support (Introduction)
Take a look at this video.

Enterprise Vault Exchange 2013 OWA Support (User Actions)
Take a look at this video.

Enterprise Vault Exchange 2013 OWA Support (Deployment)
Take a look at this...

Rob.Wilcox | 11 Oct 2012 | 0 comments

 

As Enterprise Vault Administrators we often forget that to the end-user what they see is very different to what we see every day.  They usually see parts or all of the Outlook Add-in, whereas we stare at the Vault Admin Console. So, what does the Outlook Add-in look like?  For those that aren’t familiar read on:

First of all there is the toolbar, or ribbon.  The toolbar is present in Outlook 2003 and Outlook 2007, and looks like this:

In Outlook 2010 and later, then there is the ribbon, and that looks like this:

 

The buttons that a user is sees is dictated by the Desktop Policy that applies to them.

The next thing that users usually see is...

Rob.Wilcox | 15 Oct 2012 | 0 comments

 

I have heard this question asked a few times … 

What is the difference between a Message ID and a Saveset ID?

Well the answer is that a Message ID in ‘pure’ messaging terms is a unique identifier for a digital message, it is globally unique.  It’s generated and applied by the messaging system which sends the message.  Here is an example:

<EXCH17ojhB69EpYVNXX00008d4e@exch1.EV.Local>

A Saveset ID is a unique identifier generated by Enterprise Vault for an archived item.   Here is an example:

201210099800974~201210021109570000~Z~B033AD25E5A12FC3FC7849191C136AB1

The SaveSet ID is made up of a number of components, using the above as an example, here is a description:

2012100 Checksum High

99800974 Checksum Low

201210021109570000 Message Delivery Date/Time (in this particular case, because this is an email)

...
Rob.Wilcox | 10 Oct 2012 | 0 comments

 

Some experts will say that this isn’t really something that *I* learned the other day.  Technically they’d be correct, but when you think about it we talk about Message Class in Exchange and Enterprise Vault all the time.. but what is it?

We see things like this:

 

This is a machine running Outlook 2010 with the Enterprise Vault Add-in installed, and we can see that this item has a different icon..  so that is part of it.

If we use the ‘Field Chooser’, and add the ‘Message Class’ attribute we see things like this:

And:

...

Rob.Wilcox | 14 Oct 2012 | 0 comments

 

For the last few versions of Enterprise Vault we’ve been encouraged to set a property called the ‘Cache Location’ on each Enterprise Vault server.  The cache location is used by:

* The Indexing Service

* PST Migrations

* File System Archiving with some target file systems

* Vault Cache

One of the folders that you will see is the VCBuilds folder.  This is an example of the folder from my Enterprise Vault 10.0.2 system:

In this case it is showing me that a Vault Cache ‘DB’ file is being built for one of my test users.  The 154 Mb temp file in the middle of those is slowly growing, as the items are being added to the file.  Once it has finished being built then it will be turned over to a PST file, as this shows:

...

Rob.Wilcox | 09 Oct 2012 | 0 comments

 

A bit of an oops moment from the Enterprise Vault world which is described in this following technote:

http://www.symantec.com/docs/TECH197993

It is an issue relating to using the Server Settings Migration Wizard and in fact using it to migrate EV 10 to another machine with EV 10.   The Migration Wizard can't handle (at the moment) EV 10 as a source.  It is likely to be one of those that was just never thought of during the design and building - after all most people will use the Migration Wizard to move from EV 9 to EV 10.. not EV to EV 10.

Hopefully it will be something which gets addressed in the near future.