Enterprise Vault Cache Settings

• What Is Vault Cache Location
• Enterprise Vault Cache Corrupt
• Enterprise Vault Cache Settings Google Chrome
• Enterprise Vault Cache Settings Windows 10

Setting Caching Behavior You can edit user or group profiles to control how files in designated folders are cached and refreshed. Automatically clearing the cache during logout reduces a user's cache size and increases security on machines that are used by multiple users. If you're just starting out with Vault Enterprise (or just 'Vault' for short) for the first time, welcome! We understand that getting to grips with a new system can be daunting, but don't worry: we've built Vault to be as simple-to-use as possible, and we're here to help with a library of how-to guides. How Cache Settings Are Displayed. The Caching page displays the current cache settings (from the latest User Application restart). It also displays the corresponding global and local values of those settings and lets you change them (for use at the next User Application restart). The global settings always have values. The local settings are. Enterprise Vault regularly synchronizes your online vault and your Vault Cache. Your administrator may also let you start the synchronization process yourself. Vos virtual orchestra studio download free. About Virtual Vault for Outlook users.

Code: Select all

• 1. Delete or rename the _sgvault folder and then delete all the Cache Members except for
  CacheMember_WorkingFolderAssignments and CacheMember_ChangeSetItems (this tracks adds, deletes, moves, shares, and branches that are pending).

• 2. Rename or delete the folder
  C:UsersusernameAppDataLocalSourcegearVault_1Client{repository-guid}{vaultuser}
  or
  C:Documents and SettingsLocal SettingsApplication DataSourceGearVault_1 Client {repository-guid}{vaultuser}.
  or on a Mac
  ~/Library/SourceGear/Vault(Pro)_1/com.sourcegear.vault.guiclient/..
  on your local computer. That will force Vault to recreate all cache information for that repository. You will need to reset working directories.

What Is Vault Cache Location

… that moment, when in the cloud – in a real one; i.e.: in a plane somewhere over an ocean – and you eventually got nothing else to do than reading those loads of docs you dropped into your mailbox for later use … that – very – moment … when your enterprise's archiver kicks in and Outlook tells you it can't load your eMail as you are – guess what? – OFFLINE!

Here's what I did.

Why?

Enterprise Vault is a great archiving solution. It integrates pretty seamlessly with Outlook. You don't realize any difference in accessing eMails whether they're meanwhile archived or not. There's however a difference: Once Vault has gotten hold of one of your eMails, all you really have in your folders is in essence a torso of 300 chars embedded with a link to the respective Vault item of your eMail.

And now, there's those occasions when you want to access exactly those old eMails that Vault has long ago grasped; also when offline; and – honestly: PST is not such a bad concept (while I indeed do appreciate companies' aim to reduce (restrict) PST usage). Anyway. I spent some thought around this recently and ultimately created a solution which works perfectly for me and now lets me access all my old mail again – through a PST folder.

This one's to explain how that solution works:

The Solution

is a simple Outlook VBA codepiece grabbing any vaulted eMail, opening it and copying it to a respective PST folder. Once opened and copied (the 'copy' is key) it loses its vault link and gets its entire content back.

1: Search vaulted eMails

First of all, I defined an Outlook Search Folder to grab all vaulted eMails. This can be done by querying the .MessageClass field:

I went by the Search Folder idea as otherwise I'd have to walk through all eMails to find the vaulted ones. BTW: On vaulted eMails the MessageClass field reads 'IPM.Note.EnterpriseVault.Shortcut' in its entirety.

2: Folder structure

Enterprise Vault Cache Corrupt

I then wanted to replicate my folder tree in the target PST – just … well: just 'cause I'm used to. That's a little recursion:

3: Get the search folder to retrieve the vaulted eMails from

Finding the respective search folder is just an iteration over all stores and figuring out the SearchFolder object with the right name.

4: Finally – the eMail copy routine

That one's the major piece of it; with every eMail retrieved from the SearchFolder you got to

• Open it by the MailItem.Display command; this creates an Inspector object
• Grab the Application.ActiveInspector and from that the Inspector.CurrentItem
• Once the MailItem is discovered you can copy it: currentItem.Copy. That's a major step. You could just right away move the item into the target folder in your PST, but that would not void the vault link.
• Finally – after that copy operation – you can now move the MailItem in the destined target folder (I made sure it is the same as in the original mail store): MailItem.Move targetFolderName
• After moving, close the item without changes: MailItem.Close olDiscard

With that operation on any of the vaulted eMails they get freed and accessible without vault connection.

Now – a few useful hints

for the benefit of your patience:

• The Outlook forms cache is a tricky beast. As Enterprise Vault uses a bunch of custom forms to handle vaulted eMails, the forms cache is heavily used during this operation. I removed it before execution and also made sure that in case it gets scrambled again forms would be loaded from their original source instead to load'em from the cache. Here's a few sources on the Outlook forms cache and the ForceFormReload registry key.
• This still did not allow the macro to execute on all the 1300-something eMails I had to unvault. Ultimately, a simple DoEvents command in the macro's main loop allowed Outlook to regularly recover from its heavy use of the forms cache.
• Where to start? I used the namespace method PickFolder and simply chose the right folder to target my eMails to by the dialog it throws up.
• Deletion after unvault: You might wanna consider deleting any vaulted eMail from your main mail store once it's been copied to the PST.

Code: Select all

• 1. Delete or rename the _sgvault folder and then delete all the Cache Members except for
  CacheMember_WorkingFolderAssignments and CacheMember_ChangeSetItems (this tracks adds, deletes, moves, shares, and branches that are pending).

• 2. Rename or delete the folder
  C:UsersusernameAppDataLocalSourcegearVault_1Client{repository-guid}{vaultuser}
  or
  C:Documents and SettingsLocal SettingsApplication DataSourceGearVault_1 Client {repository-guid}{vaultuser}.
  or on a Mac
  ~/Library/SourceGear/Vault(Pro)_1/com.sourcegear.vault.guiclient/..
  on your local computer. That will force Vault to recreate all cache information for that repository. You will need to reset working directories.

What Is Vault Cache Location

… that moment, when in the cloud – in a real one; i.e.: in a plane somewhere over an ocean – and you eventually got nothing else to do than reading those loads of docs you dropped into your mailbox for later use … that – very – moment … when your enterprise's archiver kicks in and Outlook tells you it can't load your eMail as you are – guess what? – OFFLINE!

Here's what I did.

Why?

Enterprise Vault is a great archiving solution. It integrates pretty seamlessly with Outlook. You don't realize any difference in accessing eMails whether they're meanwhile archived or not. There's however a difference: Once Vault has gotten hold of one of your eMails, all you really have in your folders is in essence a torso of 300 chars embedded with a link to the respective Vault item of your eMail.

And now, there's those occasions when you want to access exactly those old eMails that Vault has long ago grasped; also when offline; and – honestly: PST is not such a bad concept (while I indeed do appreciate companies' aim to reduce (restrict) PST usage). Anyway. I spent some thought around this recently and ultimately created a solution which works perfectly for me and now lets me access all my old mail again – through a PST folder.

This one's to explain how that solution works:

The Solution

is a simple Outlook VBA codepiece grabbing any vaulted eMail, opening it and copying it to a respective PST folder. Once opened and copied (the 'copy' is key) it loses its vault link and gets its entire content back.

1: Search vaulted eMails

First of all, I defined an Outlook Search Folder to grab all vaulted eMails. This can be done by querying the .MessageClass field:

I went by the Search Folder idea as otherwise I'd have to walk through all eMails to find the vaulted ones. BTW: On vaulted eMails the MessageClass field reads 'IPM.Note.EnterpriseVault.Shortcut' in its entirety.

2: Folder structure

Enterprise Vault Cache Corrupt

I then wanted to replicate my folder tree in the target PST – just … well: just 'cause I'm used to. That's a little recursion:

3: Get the search folder to retrieve the vaulted eMails from

Finding the respective search folder is just an iteration over all stores and figuring out the SearchFolder object with the right name.

4: Finally – the eMail copy routine

That one's the major piece of it; with every eMail retrieved from the SearchFolder you got to

• Open it by the MailItem.Display command; this creates an Inspector object
• Grab the Application.ActiveInspector and from that the Inspector.CurrentItem
• Once the MailItem is discovered you can copy it: currentItem.Copy. That's a major step. You could just right away move the item into the target folder in your PST, but that would not void the vault link.
• Finally – after that copy operation – you can now move the MailItem in the destined target folder (I made sure it is the same as in the original mail store): MailItem.Move targetFolderName
• After moving, close the item without changes: MailItem.Close olDiscard

With that operation on any of the vaulted eMails they get freed and accessible without vault connection.

Now – a few useful hints

for the benefit of your patience:

• The Outlook forms cache is a tricky beast. As Enterprise Vault uses a bunch of custom forms to handle vaulted eMails, the forms cache is heavily used during this operation. I removed it before execution and also made sure that in case it gets scrambled again forms would be loaded from their original source instead to load'em from the cache. Here's a few sources on the Outlook forms cache and the ForceFormReload registry key.
• This still did not allow the macro to execute on all the 1300-something eMails I had to unvault. Ultimately, a simple DoEvents command in the macro's main loop allowed Outlook to regularly recover from its heavy use of the forms cache.
• Where to start? I used the namespace method PickFolder and simply chose the right folder to target my eMails to by the dialog it throws up.
• Deletion after unvault: You might wanna consider deleting any vaulted eMail from your main mail store once it's been copied to the PST.

Enterprise Vault Cache Settings Google Chrome

So, finally the end result now resides within my Outlook Applicaiton as a VBA routine and lets me regularly unvault and PST-archive my eMail.

Enterprise Vault Cache Settings Windows 10

Nice . I think.