So if I remove the ForceOSTPath setting pointing to a network share, would my
best move be to just unconfigure that and redo people's outlook profiles to
have it point back to their Local Settings folder?

"Diane Poremsky [MVP]" wrote:

outlook will complain and create a new one.

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Exchange Messaging Outlook newsletter:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

You can access this newsgroup by visiting
http://www.microsoft.com/office/comm...s/default.mspx or point your
newsreader to msnews.microsoft.com.


"Rich" wrote in message
...
I totally agree the OST file shouldn't be on a network share.

The reason they have Application Data redirect is because with the roaming
profiles, this allows for the musical chairs they play within the office.
All the machines are the same, with the same software load, and it's a
revolving door with users using whichever computer is available.

If I force the OST files via Group Policy to go to say C:\OST, wouldn't
that
cause problems when one person logs in, it creates an outlook.ost, then
they
sign off, and another person logs in and it tries to use that same
outlook.ost since the file name already exists (although its from a
different
user)?



"Roady [MVP]" wrote:

Yes, the ost-file is just a cached copy of the Exchange mailbox mainly to
reduce network traffic. Redirecting the folder back to a server therefore
doesn't make any sense and isn't even a supported configuration (just
like
connecting to pst-file located on a network share).

Outlook's Group Policies allows you to specify the location of ost-files.
Note that it doesn't work for existing ost-files. For that you'll need to
update the mail profile of the user.

See http://www.howto-outlook.com/howto/policies.htm

Note that there are several more reasons why you really shouldn't
relocate
the Local Application Data folder to a server share. If you really want
to
copy the nk2-file to the server, then use a logoff script to copy it.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

http://www.msoutlook.info/
Real World Questions, Real World Answers

-----

"Rich" wrote in message
...
Also, if they don't have the OST, they will still log in with their
Outlook
configured and all that, right? I'm pretty sure the OST is just the
cached
copy of the mailbox and nothing more.

"Rich" wrote:

I have a large site that has their Application Data folder redirected
to
a
server, but we're running into a big problem with disk space and
bandwidth
due to this redirection putting everyone's OST files from Outlook 2007
onto
the server. It's good because their .NK2 files go to the server, but
is
there a way to have the .OST files, which can easily and automatically
be
recreated when they log onto another machine, not on the server?

I guess I could go to every machine and change the path for the OST
file,
but hoping there is a better way. They all use roaming profiles by
the
way.