HI Guys
Thanks for the advice. it seems that general opinion is agreed, dont get yourself in the situation i'm in.... however is there a way out of it now that i find myself with PST files and vaults that do not have valid mailboxes associated with them.
we're a company of over 20 globally distributed offices each with local file servers and workstation pools, and in many cases separate domains. This, combined with historically poor enforcement of IT policies, has meant that pst files are hidden all over the place, it seems that many staff members will have, through their careers, been stationed in 3 or 4 different offices and used a similar number of workstations. some psts are on file server, some on workstations that the current user has out in the field for weeks at a time. this makes PST collection a chalenge. even though users don't remember where pst files are and no longer reference them the comapny policy states they should be imported to the vault for permanent retention but i've been running pst migrations for 12 months and am a long way from completeing even the location phase, let alone working out who's they all are and then migrating them. in all this means i'm going to have this problem again as the chances of me keeping up with staff changes are zero.
if the proper EV tools aren't enough is there any way to forcibly import them, even as crudely as using outlook one file/folder at a time (suddering at the thought)?
