policies for "ownerless" vaults
I've recently discovered that, when a vault which belongs to a user account in a provisioning group etc has that active directory user account deleted all policies are removed and you are left with a vault with no policies assigned, specifically i'm concerned by the PST migration policy. we're still in the proccess of migrating the many TB of pst files that exist network wide and manual migration is an un managable task I'm getting on really well with the PST migrator tasks and makeing good progress (slow but steady and reliable is fine by me) but policy is to place pst files into the mailbox from which they originated where at all possible.
If user X leaves the company they are a user of EV and had a vault. the entire mailbox is archived and permissions applied to allow replacements/managers to access the vault as required. eventually (at about the six month mark) the user account is deleted from AD and thus exchange as part of our internal housekeeping. the vault is retained and hte access permissions kept so access is available ot those who need it. however adding psts and such falls foul of this lack of a policy.
I've looked but canot find any way of making a provisioning group for "all other vaults" - kinda of makes sense as they already exist and don't in AD. so i need a way to assign policies to these ex staff vaults. it would also be reassuring to know that some process is placing hte retention policy on these vaults.... currently i'm not sure where we stand on retention policies of vaults affected this way.
Thanks for your help
PST FlighDeck is the answer
Then you might want to have a look at PST FlighDeck
You can contact me directly should you need any further assistance.