Today’s announcement that the Microsoft Exchange development group plans to release a tool to allow administrators to discover Personal Storage (PST) files on a network and then import the data into Exchange 2010 on-premises servers or Exchange Online (Office 365) left a couple of unanswered questions floating. Don’t get me wrong. I hate PST files as I think they are the work of the devil – unstable, unprotected, and out of control. It’s an area of the Exchange/Outlook product combination that has needed attention for years and it’s surprising that Microsoft has taken so long to make a move in this direction, some two years after the launch of Exchange 2010 and the introduction of online archive mailboxes.
The first question that comes to mind is exactly when will Microsoft release the tool? There’s no firm date in the announcement, just “later this year“. Maybe it will be a Christmas gift.
Second, what will be Microsoft’s added value over the proven PST ingestion tools that companies such as Transvault and Sherpa Software have developed over many years? The cynic in me says that the added value will come through the zero dollar value price point, which is fine as far as it goes and certainly better than the current situation. However, it’s also fair to say that third-party software vendors have invested a great deal of intellectual capital in their products and that they deserve your attention and support in terms of investigation before you assume that any software written by Microsoft to perform a particular task will automatically be the best. Some testing of available PST ingestion tools in your own environment is therefore required to identify whether, for instance, one tool is more automated than another or whether one allows greater flexibility in terms of deciding what data should be ingested, ideally through easy-to-understand and easy-to-deploy policy settings that can truly unearth PSTs lurking on PCs scattered around the enterprise.
I’m sure that Microsoft will avoid the trap of providing a tool that makes it too easy to ingest vast quantities of PSTs without some control. There’s no point in ingesting tens of gigabytes of absolute crap from user PSTs into an online mailbox database just because you can…
Automation is a big thing for me when I look at tools that are designed to help administrators and is particularly valuable if the software saves time. Remember that time is money and a paid-for automated tool that saves an Exchange administrator a lot of time is so much better in the long run than something that’s free and does a basic job.
Of course, I’m writing this without any idea whatsoever of the functionality that Microsoft will bring to the table and it is entirely possible that they will deliver a fantastic automated all-singing and all-dancing PST ingestion tool that allows administrators to sit back, admire, and watch the gigabytes flowing into mailbox databases. If this is the case then I have another concern and that is why Microsoft is investing time in tools like this that eliminates an area covered by third-party software vendors when there are other areas that they could deliver real value in, such as figuring out the long-term future for public folders.
Microsoft can rightly say that they are simply answering customer concerns and that’s a fair and valid statement. Microsoft can also say that competition spurs progress and that the third-party software vendors will increase the feature/functionality set in their products to stay ahead of the free tool. I hope this is true but I do worry when the elephant in the Exchange market threatens to squash some of the smaller players who have helped to make Exchange such a success.
Last, what does Microsoft mean when it refers to “pirate growl” when it mentions the “dreaded PST scourge” in the blog post? I think I understand the aforementioned scourge to mean the uncontrolled sprawl of potentially valuable information held in the worst-secured file format on the face of the planet, but I am baffled at the reference to pirate growl.
Lots to think about – and I look forward to investigating just how well Microsoft’s PST ingestion tool works when it is released to the public.
I will try to refrain from keeping posting but I am becoming an avid follower of your blog after a few days, adding now to many years of respect! (With a recent visit to Ypres to see my great-grandfather’s grave and having a grown up surrounded by collections of WWI & II books and memorabilia, the description of your visit was emotive and a reminder of true courage and great loss in our history)
I had that “don’t get me started” feeling after reading this post! One does wonder if this will just be an Exmerge+ 2011(or 2012 by release)?
As it was left to commercial applications, administrators have commonly written scripts to scan network shares and domain computers, then importing with Exmerge/Powershell what is required based on an aged date criteria to split between live and archive.
The problem is that any PST tool is still only any use if an organisation faces the bitter pill of dealing with PST’s. PST’s and public folders seem here to stay for a while because many organisations have failed to get rid of them before they have consumed hundreds of gigabytes, by leaving them in user’s control.
The cost implication of migrating all that data to Cloud providers and good competition in the archiving marketplace may be the driving force in now reducing PST usage for many.
As you say, lots to ponder in awaiting the release. Looking forward to RIP PST still though!
No worries about leaving replies… after all, at least then I know that someone is reading the blog!
Well said Tony. You have to wonder if Quest, Symantec, etc. can keep providing independent applications for Exchange which add value. Yet as long as there are faults/limitations the 3rd party vendors will bring something to the table. Usually the 800 pound Gorilla (Microsoft) is so way behind nowadays with product innovation after their initial launch.
PST ingestion tool from Microsoft? I say big deal. Symantec and others (whom you mentioned in the article) have been providing this for years.
Oh we’re reading all right and getting a lot of value from the blog. Really glad you’re taking the time. Talking to colleagues over the last few weeks, it would seem that all of us UK messaging guys at your former employer are tuning in regularly for a start.
I’m delighted to hear that many of my previous Digital-Compaq-HP messaging colleagues might be tuning into the blog. This makes it even more worthwhile and enjoyable than it already was.
I would assume they would release the tool really soon. Half of the work has already been done for them…
Ingesting the PST is just a part of the workflow, especially in large organzations.
a) Mobile Users which have their PST’s on local laptops which are not connected always to the company lan
b) Password protected PST’s
c) Corrupt PST’s
d) Copies of PST’s with the same Data
there are a lot more…
My conclusion: PST Migration in medium and large Enterprises need a workflow and a “preflightcheck” before ingestion.
We’ve published a whitepaper related to this:
Click to access FlightDeck-Exchange_2010-WhitePaper.pdf
Happy reading 🙂