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:
The entries will look something like this:
As you can see from that screenshot I’m getting a build up of references to the VCBuilds folder on disk, where temporary files are located as built by the server ready for end-user machines to download. These are the Vault Cache .DB files.
The problem is that these entries are added to the registry key, but never cleared up by Outlook, or Windows. They’re added to support Windows Search. Whilst this isn’t something that we, from an Enterprise Vault perspective, want to have happen on the EV sever, the fact that Outlook 2007 is used leads to this happening inevitably.
There is a way around it, and future work in this area might mean that Enterprise Vault cleans things up.
The way around it is documented in a Symantec technote :
This is not the only location in the registry that the workaround can be added, but that’s the one which has chosen to be documented. i.e. :
DWORD : 1
(I had to create the Windows Search, and Preferences keys)
In addition, it should be noted that on 64 bit machines that registry key should be in: