M
Microsoft NNTP
Hi all
I am running Outlook 2003 against an Exchange 2003 server using cached mode.
Whilst it works OK I can find no way of moving the new type of OST file that
is created when the profile is initially setup. I must admit that
considering a standard legacy OST file could be placed anywhere this is a
major problem for users who have already got their legacy OST file in a
location other than their C: drive.
My real question is how to relocate the cache file. Simply moving the file
to another location just causes a new one to be recreated in the default
location with no prompts whatsoever. I have tried modifying the location at
setup and no matter what I do it just ends up in the default location. I
have also searched the registry for any pointers again to no avail. The only
way I can see is to relocate the users profile directories to the required
location thus moving the default location of the cache file. However, this
is far less than ideal and seems rather a convoluted compared to what was a
very simple issue to resolve in previous versions.
Any ideas gratefully received. Many thanks in advance.
Regards,
Paul Lemonidis.
I am running Outlook 2003 against an Exchange 2003 server using cached mode.
Whilst it works OK I can find no way of moving the new type of OST file that
is created when the profile is initially setup. I must admit that
considering a standard legacy OST file could be placed anywhere this is a
major problem for users who have already got their legacy OST file in a
location other than their C: drive.
My real question is how to relocate the cache file. Simply moving the file
to another location just causes a new one to be recreated in the default
location with no prompts whatsoever. I have tried modifying the location at
setup and no matter what I do it just ends up in the default location. I
have also searched the registry for any pointers again to no avail. The only
way I can see is to relocate the users profile directories to the required
location thus moving the default location of the cache file. However, this
is far less than ideal and seems rather a convoluted compared to what was a
very simple issue to resolve in previous versions.
Any ideas gratefully received. Many thanks in advance.
Regards,
Paul Lemonidis.