Discussion Locked

Tech Perspective: Dialing up Outlook 200

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Outlook 2000 often provides very sluggish performance for remote access dial-up users. What do you think causes this problem? Do you blame it on Outlook 2000 program design, larger e-mail messages and attachments, a lack of user knowledge in configuring Outlook, or another reason? How do you think this problem can be resolved? What are you doing to help your users work around it? You can read the related Gartner article, which will be posted 3 A.M. Monday, at https://www.techrepublic.com/article.jhtml?id=r00220000724ggp01.htm.

8 replies

by fred_e944

Synchronization causes slowness, especially when Outlook is opened, and at other times which depend on configuration.

To help the problem we configure Local Calendar use, and set synchronizaton to occur less intrusively. We also limit the size of e-mails and attachments sent from Exchange Server over RAS.

by hgarza

We have found that configuring Outlook so that messages arrive to the user's personal folders constitutes the most efficient solution. This configuration saves users from having to synchronize with the server, a process which sometimes takes up to an hour. Message transfer is sped up and eliminates risks associated with the popular [ctrl + alt + del] method of unfreezing Windows.
OWA may be of some help, but may not be a solution for everybody, since PDA synchonization demands a connection to Exchange or the user's personal folders.

by isaac

Well, at least one of the problems i.e. large file sizes can be solved with a product called MaxCompression. By installing it in Outlook, any mail that is sent from another user on the LAN will be automatically compressed. This dramatically imporoves the transmission time of Excel, Word and PP attatchments. You can find the software at www.c2c.com

by mrobards

Try running Outlook 2000 under terminal server with Metaframe. Outlook is always running, thus eliminating any synch time! We've been doing this for over 1 year connecting via 28.8k lines in rural West Alabama back to our Citrix Metaframe server and love it!

An alternative plan is to use Citrix NFuse technology to publish Outlook to a home page and connect to it via a browser. It will run either embedded or in a separate window.

Also you could chunk Outlook 2000 all together and use OWA and connect in regular fashion, or use Citrix Metaframe to run IE 5.5 for even better speed. Don't laugh. I've been doing it for > 1 year!

This discussion is closed to new replies.