> 1) move the .pst files out of local settings and into:
>
> c:\documents and settings\<user>\application data\microsoft\outlook
>
> which would save them to the user's roving profile in the PDC when the
> user logs off, and update from the PDC when the user logs on. This would
> satisfy the backup scenario, and would get local copies of the .pst
> files from the PDC, but I'm concerned about what would happen if the
> user logged in at a second machine before logging off at the first:
> they'd have parallel .pst files and only one of these would end up saved
> to the PDC. I think. I may be trying to be too smart about this:
> Microsoft certainly has thought about these issues and perhaps it'll
> "just work".
Don't know about this.
>
> 2) move the .pst files into the user's home directory on the PDC, so
> that outlook is accessing them over the network and not locally. This
> satisfies the backup scenario and also fixes the overcopying concern, but:
This is what I do. My PST files are on a Linux file server and work very
nicely.
> a) are the .pst files multi-user capable? I ask this because it is
> possible that a user will have Outlook running on one machine, then go
> to a different machine, log in again, and start Outlook again. They
> didn't mean to open a shared .pst, but there you go it happened anyway.
No, they are not. In fact, I've had trouble backing up a PST from a Windows
file server when the user had Outlook running. "Cannot access outlook.pst
because anothe rprocess has the file locked." I guess I should try again with
Linux.
> b) will performance suffer by not having the .pst files local?
Not that I've noticed. I've been running PST files on the server for five or
six years (Windows, then Linux) and have never been unhappy - and my PST
files can get to be nearly a gig.
--
Whil
Moving to Linux: Freedom, Choice, Security, Opportunity
http://www.hentzenwerke.com
©2004 Whil Hentzen |
