Backup & Archiving Community Blog

Today I was playing with EV 9 + Exchange 2010. I have found out I have no EV functionality in OWA. While checking EV OWA log at Client Access server I've found such entry:

[EVContext::IsValidBrowser] Returning: False

I tried then several browsers: IE 9, Firefox 9, Aurora (Firefox 11), Chrome 16.0.912.77. So, only IE 9 gave expected result.

Later I've checked Compatibility Chart and ensured only IE 7, 8 and 9 are supported. However I don't understand why EV cares about browser used by OWA if all presentation (e.g. browser dependent layer) is implemented by OWA

This issue originally came up in early 2010, but I was reminded about it the other day when a colleague asked whether the issue still existed or not. I looked back over my blogs and discovered I didn’t write about it the first time around, so … here goes!

This issue only exists with Outlook 2007 on the Enterprise Vault server. It does not exist when Outlook 2003 is installed. I do not know about Outlook 2010 – and that is currently not supported anyway (on the EV server).

With Outlook 2007 installed, if PST migrations are done and/or Vault Cache is enabled for end users then a large number of entries may build up in the registry under the following location:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Catalog

The entries will look something like this:

As you can see from that screenshot I’m getting a...

Following my earlier blogs about an issue with Enterprise Vault and SSL configured on the Enterprise Vault virtual directory in IIS on the EV server, there is now a post 9.0.3 Client hotfix available to correct the issue.

It’s available as:

* DCOM/HTTP variants

* All supported languages

.. so that should cover all the bases.

I have to admit that I like the Enterprise Vault Client Driven PST Migration method.  There are plenty of things which can be done to improve it, but right off the bat, it does a pretty decent job of getting PSTs up to the Enterprise Vault server, from client machines.

To use it effectively there are a number of things to think about:

* PST Migration Policy

Review or create new ones in the VAC and assign them to users.

Also as part of this decide whether you are going to use the template mail EnablePSTMigrationMessage.msg.  This can be sent to end users when you enable them for client driven PST migration.

* Location of PSTs

Hopefully the end users are storing their Outlook connected PSTs locally on their machine.  Client driven migration can scan the whole end-user workstation, or just look under the ‘Documents and Settings’ folder for the user, when it runs.

 (See...