In the previous part of this guide we looked at gaining a list of PST files and machines. In this, the final part of this series, we will look at how to import these into Exchange 2010.
In the last part of this guide the process for importing a local PST file into exchange server was shown. However, in reality it is likely that these PST files are scattered liberally around your network on the hard drives of your users machines as a result of Outlooks personal archiving. Ideally – so that this process is transparent to your users, you’d like some way of finding all these PST files – pairing them up with their users, and importing them into the appropriate mailbox. Here I show you how.
With the new online Move-Mailbox functionality in Exchange Server 2010, invoked by calling the New-MoveRequest cmdlet, the time a mailbox is offline has been reduced to only seconds, and as such the end-user experience has been greatly improved.
There’s a mystery about early Exchange 2010 deployments: despite the much-publicized removal of single instance storage, sizes of Exchange 2010 databases have not increased. The same message has trickling back from all quarters, as businesses go live: after moving mailboxes, database sizes in Exchange 2010 are roughly the same as they were in Exchange 2007.