• Facebook
  • RSS Feed
  • Instagram
  • LinkedIn
  • Twitter
Apr 192012

I read over on the Exchange Team blog, and bink.nu about two new Exchange updates:

Exchange 2010 SP 2 Update Rollup 2 (which is just in 31 Mb)

Exchange 2007 SP 3 Update Rollup 7 (which is 55-60 Mb)

As ever these aren’t specifically tested by Symantec for Enterprise Vault, so test them in your own test environment first.  Of course should you encounter issues in relation to Enterprise Vault, then Symantec Support will be able to assist.

Jul 142011

An issue that I thought we had resolved a long time ago crept again a week or so ago.  The issue that you can’t perform Enterprise Vault Outlook Addin actions on large numbers of items..  large being “about 250”.

This is apparent in an ONLINE Outlook profile, and it is because Exchange 2003 and later limit the number of objects that a user/client can have open at any one time.  The Outlook Addin touches/opens each item in your selection to check various properties on it.  Unfortunately the way that it is written at the moment is that this causes us to push against the default limit or 250 message objects…

You get a 9646 event on your Exchange Server, and it’ll tell you about hitting the objtMessage limit.  The following technet article goes in to a bit more detail about the limit, and it being a protection mechanism for Exchange :


The only ways around it with the Enterprise Vault Outlook Addin at the moment are :-

* Use Outlook Web Access (I don’t think that is affected)

* Use cached mode Outlook

* Increase the limit described above (but I wouldn’t recommend that, and neither does Microsoft from the looks of the Technet article)

Read a bit more about it, and subscribe for updates :


Dec 022009

A point worth noting, I think …  Say your Mailbox as reported in Exchange Management Console/Shell/ESM is 110 Mb, an often asked question is why the OST file for that mailbox is soooo much bigger.

Microsoft have the answer : http://office.microsoft.com/en-us/ork2003/HA011402591033.aspx


When deploying Cached Exchange Mode for Outlook, be aware that users’ OST files can increase in size by 50 percent to 80 percent over the size of the mailbox reported in Exchange Server. The format Outlook uses to store data locally for Cached Exchange Mode is less efficient than the server data file format, resulting in more disk space used when mailboxes are downloaded to provide a local copy for Cached Exchange Mode.


And further..  Remember the OST/PST “speed up” patch which was released.  It had a small side-effect :


Hope that’s interesting !