There are several occasions in which an administrator would want to export Exchange 2010 mailbox to PST. The most common ones include to migrate on-premise mailboxes to Exchange online and to extract a single or a few mailboxes from the database. Though rare, another situation that demands such an export is to salvage data from a damaged or corrupted Exchange 2010 database file (EDB).
You’d have to agree that all those are pretty good reasons to support the conversion of EDB data to PST format. Now that that’s established, how about moving on to the technique to do it? Well, that’s the interesting part; we’re letting you know a neat method to use PowerShell commands and achieve the said export. But if you’re in the mood for some automation, we also have a suggestion up our sleeve that’ll surely impress you. So hang on tight and let the fun begin!
VMs – Gotta love them.
I like playing with Virtual Machines. I like playing with Virtual Hosts. In fact, 90% of my servers are all VM based at the office. It makes business sense to go virtual when the positives far outweighs the negatives.
The ability to swap between them when failure occurs in the blink of an eye is such a great advantage, any business who has not looked at going this direction is shooting themselves in the foot.
Unless specific requirements are needed, I prefer creating VMs that have “host only” communication. This way I can lock away what needs to be locked and NAT what needs to be seen. One of the issues that I have run into when going the “host only” route is that some installations throughput is seriously lacking with the speed cracking. A little bit of scratching showed me that it was Microsoft Windows(2008 and up) trying to be [their version of] clever by doing some TCP off loading(among others).
This becomes a problem when speed is exactly what the doctor ordered. How did I get around it?
Easy, follow these steps: