K
Kevin McD
I'm well aware that PST access over a LAN link is unsupported as outlined
here (http://support.microsoft.com/kb/297019/) and here
(http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx).
I've only recently seen a marked increase in the symptoms outlined in
"things that may happen if you do this" such as 2020 errors in the System log
of the File server cluster node that hosts the files, and also plenty of
random "Outlook cannot access the PST" , "Item cannot be displayed", "archive
is full", etc.
I can't point to a reason why it's started happening so much in the last 2
weeks, but has reached critical mass. We understand that in general for an
enterprise setting, PSTs are unacceptable in this setup for many reasons, and
are looking toward an archiving solution, but I need a way to try to stem the
immediate pain.
TechNet blog post notes "Is there any server-side tweaking that can be done
to mitigate some of these effects? Yes. Is there any guarantee that this
will resolve the problem completely and indefinitely? No. "
Can anyone speak to tweaking that I can assess to tied me over while the
powers that be come up with an implementation plan for an archiving solution?
Is the tweaking on the file server, the outlook client, or within exchange
server?
here (http://support.microsoft.com/kb/297019/) and here
(http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx).
I've only recently seen a marked increase in the symptoms outlined in
"things that may happen if you do this" such as 2020 errors in the System log
of the File server cluster node that hosts the files, and also plenty of
random "Outlook cannot access the PST" , "Item cannot be displayed", "archive
is full", etc.
I can't point to a reason why it's started happening so much in the last 2
weeks, but has reached critical mass. We understand that in general for an
enterprise setting, PSTs are unacceptable in this setup for many reasons, and
are looking toward an archiving solution, but I need a way to try to stem the
immediate pain.
TechNet blog post notes "Is there any server-side tweaking that can be done
to mitigate some of these effects? Yes. Is there any guarantee that this
will resolve the problem completely and indefinitely? No. "
Can anyone speak to tweaking that I can assess to tied me over while the
powers that be come up with an implementation plan for an archiving solution?
Is the tweaking on the file server, the outlook client, or within exchange
server?