prf and ost files.

[The NomaD]

we deploy prf files with startup scripts. if the user logs on to a different
machine Outlook creates a new ost-file. if there is already an existing
..ost, is there a way to configure the ..prf to append to it instead of
creating outlook0.ost, outlook1.ost, outlook2.ost, etc.. ?

Thanks.

 

[Diane Poremsky [MVP]]

No, because OST are local files, not stored on the network. You would need
to use classic mode for the roamers.

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
(e-mail address removed)

EMO - a weekly newsletter about Outlook and Exchange:
(e-mail address removed)

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

 

[The NomaD]

thanx, but we set OST files on the network through ForceOSTPath reg key
(http://support.microsoft.com/kb/896591/en-us).

we want to use same ost file, when user run prf file second time.

No, because OST are local files, not stored on the network. You would
need to use classic mode for the roamers.

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
(e-mail address removed)

EMO - a weekly newsletter about Outlook and Exchange:
(e-mail address removed)

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

we deploy prf files with startup scripts. if the user logs on to a
different machine Outlook creates a new ost-file. if there is already an
existing .ost, is there a way to configure the ..prf to append to it
instead of creating outlook0.ost, outlook1.ost, outlook2.ost, etc.. ?

Thanks.