EV Offline Vault Migrate or re-populate

If you can go through all those hoops, perhaps semi-automated, then yes, go for it.

Otherwise rebuild it.

You don't mention which version of EV or the EV Outlook Add-in you have (or will have)...

How many users are you talking?
Also what version of the client are you using now, and what version of the client will you be using when you push them to the new machine? and what version of the EV Server?

Typically those steps will work just fine, as long as you take the registry keys along with it, however you will have to edit certain paths as the technote suggests

For instance, in XP You would have something like

OVRoot = C:\Documents and Settings\username\Application Data\KVS\Enterprise Vault\
to OVRoot = C:\Users\username\AppData\Local\KVS\Enterprise Vault\

You cannot use wildcards like OVRoot = %APPDATA%\KVS\Enterprise Vault\ 

But again, really depends what you're going from and to
So if you're going from say EV2007 Offline Vault to an EV9 Vault Cache then a rebuild would definitely be in order, but if you're going to keep the same EV Client then you shouldnt have an issue

Depending on the timing of it we are looking at 500+ users.

Going from EV9 client or ev10.0.4 client

with a ev10 backend

Well my suggestion would be to test on a few machines if possible, ensure that the file moves/registry moves do what you expect, and then if all goes well, go ahead and move them all across....

End of the day, worst case scenario after the items move is that you will have to rebuild.

That being said, I would probably notify those users, if you use Virtual Vault, to check that they have no items in the To Archive search folder, because if they do get moved from one machine to the other but something happens with the MDC, then they will have dataloss because those items only exist locally in the vault cache and not the archive

But that scenario would be the same for whether you move the Vault Cache or whether you reset it, the risks remain

Thanks that makes alot of sense.

What would be the easiest way to pause archiving for the people being migrated but not for the rest of the organization.

I'm thinking a policy of some sort