Yes, I do indeed realize that. And, I realize that Exchange should be
used. I'm working at an institution that adapts new technologies at a
snail's pace. To this date, we still run NT 4 and we only converted
from a token ring topology 3 years ago.

So, aside from the obvious - adopting Win2k3 and Exchange - let's
assume I cannot (which I cannot) and figure out the solution to this
problem.

We have over 120 machines, about 100 of which have .PSTs stored locally
in a factory that runs 24 hours a day. Running an automatic backup
script to copy the .PST files to the network doesn't work because the
file may be open, and if it isn't, we're probably shutting down or
restarting the computer, which doesn't happen because it's been used
all day and all night. So we have Outlook always open on many many
machines with no way to get the users to manually shut down Outlook and
run a batch file and no way to automate one during the day/night or
during shutdown because of open file / lack of rebooting issues. So
what do we do to protect that .PST data other than storing it on a file
server?

Lanwench [MVP - Exchange] wrote:
In oups.com,
typed:
Hi folks,

We have users running Microsoft Outlook 2003. If their .PST file gets
moved or deleted, Outlook will prompt the user to find or create a new
one when it's opened the next time.

The problem is that users often don't know where their existing .PST
files are and will simply create a new one. Once it's created, all
their new mail is downloaded to the new .PST file and they think
they've lost all their existing mail, contacts, etc. They call the
help desk and we not only have to find the old .PST file, but we have
to temporarily disable mail retreival, merge the contents of the old
one and the new one, and hope this one doesn't get moved.

I've scoured the web and found pages like this one
(http://support.microsoft.com/kb/896515/) which only prevent the
creating of a .PST file from the File menu, once Outlook is already
fully open.

Is there a way, if the existing .PST file is moved or lost, to prevent
the user from creating a new .PST file when Outlook is opened again
and causing headaches for us?

DS

Get Exchange server and you don't have to deal with PST files anymore!

That said - why would the users' PST files be getting moved or deleted in
the first place? I don't know of any way to do what you're asking, but it
doesn't sound like an environment I'd enjoy supporting.

(You do know that PST files must remain on the user's local drive, and not
be accessed across a LAN or WAN connection, right? )