Ggast
01-18-2001, 10:12 AM
What he's said makes sense to me, except for two things: copying the user's Outlook .pst files and remote access to mail.
My users's OL 97/98 .pst files are on the network, because they're so bloody big. Mine is 172 mb, and it's not abnormal. I have users with 500 mb .pst files! Unless you've got a fast connection between offices (he mentioned a T-1), it would be better to have the user's .pst files in their home directories, and back them up there.
For remote access to mail, I would suggest using PINE. Simply set each user with a shortcut to c:\windows\telnet.exe with an argument of the mail server's IP. You don't have fancy graphics or HTML mail, but you can get your mail from anywhere in the world. Info on Pine can be found at: http://www.washington.edu/pine/
The only other reason for Outlook would be group calendaring / scheduling, and I'm sure there's an open source solution to that.
My users's OL 97/98 .pst files are on the network, because they're so bloody big. Mine is 172 mb, and it's not abnormal. I have users with 500 mb .pst files! Unless you've got a fast connection between offices (he mentioned a T-1), it would be better to have the user's .pst files in their home directories, and back them up there.
For remote access to mail, I would suggest using PINE. Simply set each user with a shortcut to c:\windows\telnet.exe with an argument of the mail server's IP. You don't have fancy graphics or HTML mail, but you can get your mail from anywhere in the world. Info on Pine can be found at: http://www.washington.edu/pine/
The only other reason for Outlook would be group calendaring / scheduling, and I'm sure there's an open source solution to that.