Comments on: PSTWay for OWA http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/ Written by Henrik Walther, Microsoft MVP, the intention of this blog is to deliver the best content when it comes to information, news, tips and tweaks for the Microsoft Exchange Server product on topics such as mobile messaging, MONAD, and Active Directory integration. There is a discussion on various aspects of Exchange administration and management with a very special focus on Exchange Server 2007. Thu, 4 Dec 2008 20:38:59 +0000 http://wordpress.org/?v=MU by: Bryon http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-89446 Mon, 13 Aug 2007 10:00:01 +0000 http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-89446 1st of all please do not confuse Outlook with PSTWay or OWA. Microsoft has no comments of accessing the PST via OWA. We fully support leaving the PST on the users personal local Drive "C" and then the only application accessing the PST over the network is PSTWay which is specifically designed to read the PST over the network. 2nd again we have 100s and i mean 3-400 customers that tells us they already and have been sucessfully supporting a centralized storage of PSTs. I expect many of them to have complex SAN systems. see www.pstway.com for more info 1st of all please do not confuse Outlook with PSTWay or OWA. Microsoft has no comments of accessing the PST via OWA. We fully support leaving the PST on the users personal local Drive “C” and then the only application accessing the PST over the network is PSTWay which is specifically designed to read the PST over the network. 2nd again we have 100s and i mean 3-400 customers that tells us they already and have been sucessfully supporting a centralized storage of PSTs. I expect many of them to have complex SAN systems. see www.pstway.com for more info

]]> by: Bryon http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-84288 Tue, 19 Jun 2007 18:31:31 +0000 http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-84288 Everywhere Networks maintains a PSTWay FAQ at http://www.everywherenetworks.com/owa-pstway-faq.php#9 Bryon Everywhere Networks Everywhere Networks maintains a PSTWay FAQ at http://www.everywherenetworks.com/owa-pstway-faq.php#9

Bryon
Everywhere Networks

]]> by: Bryon http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-84276 Tue, 19 Jun 2007 18:25:46 +0000 http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-84276 Hey now you are jumping the gun, 1st of all we give the choice to leave the PST on your Local drive (C) as many of customers will utilize PSTWay for OWA this way. That said, hundreds more tell us they already successfully store PSTs on Network shares. Some suggested the Network stored PST issues went away with the implementation of their SAN. In either case we support it. PSTWay for OWA also has some built in functionality to overcome network latency associated with extremely large PSTs no matter where they are stored. The product was initially built to mission critical specs of a customer with over 75,000 global OWA users many with large multiple PSTs of both flavors. They tell us that 50% of the PSTs are maintained in Network shares, 20% stored on local drives, and 30% don’t use PSTs. B Hey now you are jumping the gun, 1st of all we give the choice to leave the PST on your Local drive (C) as many of customers will utilize PSTWay for OWA this way. That said, hundreds more tell us they already successfully store PSTs on Network shares. Some suggested the Network stored PST issues went away with the implementation of their SAN. In either case we support it. PSTWay for OWA also has some built in functionality to overcome network latency associated with extremely large PSTs no matter where they are stored. The product was initially built to mission critical specs of a customer with over 75,000 global OWA users many with large multiple PSTs of both flavors. They tell us that 50% of the PSTs are maintained in Network shares, 20% stored on local drives, and 30% don’t use PSTs.
B

]]> by: Jeff http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-83375 Mon, 11 Jun 2007 02:11:47 +0000 http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-83375 Interesting...but this product inherently requires people to use PSTs across a network--a bad, bad idea. Microsoft does not support opening PSTs across a network, and with good reason. I've seen the results at one of my clients who insisted on doing this, over my objections. Once PST usage blossomed, file server hung a couple times a week, usually in the mornings when everyone came to work and opened Outlook. This article (whose link I think I first found on this blog...) describes the problems it causes--and I can vouch for it! http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx Interesting…but this product inherently requires people to use PSTs across a network–a bad, bad idea.

Microsoft does not support opening PSTs across a network, and with good reason. I’ve seen the results at one of my clients who insisted on doing this, over my objections. Once PST usage blossomed, file server hung a couple times a week, usually in the mornings when everyone came to work and opened Outlook.

This article (whose link I think I first found on this blog…) describes the problems it causes–and I can vouch for it!

http://blogs.technet.com/askperf/archive/2007/01/2...t.aspx

]]> by: Sean van Osnabrugge http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-81336 Mon, 04 Jun 2007 17:50:48 +0000 http://blogs.msexchange.org/walther/2007/06/03/pstway-for-owa/#comment-81336 That looks like an interesting product, but I thought that Microsoft doesn't support PST files over network shares as per the following KB: http://support.microsoft.com/kb/297019/en-us It kind of troubles me to be implemeting a product for something that Microsoft won't support. That looks like an interesting product, but I thought that Microsoft doesn’t support PST files over network shares as per the following KB: http://support.microsoft.com/kb/297019/en-us

It kind of troubles me to be implemeting a product for something that Microsoft won’t support.

]]>