?
Solved

Outlook 2007 / Office 365 / high-latency Internet connection

Posted on 2014-10-01
5
Medium Priority
?
582 Views
Last Modified: 2014-11-10
We have a client whose office Internet connection is via a high-latency satellite connection.  They use Office 365, and connect to their mailboxes using Outlook 2007.

Users are reporting that Outlook 2007 takes several minutes to open, and performance is generally dreadful (yes, they are using cached Exchange mode!).

I've run some very basic tests using Outlook 2013 connecting to my own Office 365 mailbox while visiting their office, and find that its performance isn't as bad.  It seems on the face of it that Outlook 2013 handles this type of high-latency connection better than its predecessor.

Are there any configuration options for Outlook 2007 specifically that could help with performance when working with a high-latency Internet connection?  (apart from just buying new software!)
0
Comment
Question by:wakatashi
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 
LVL 8

Expert Comment

by:Acosta Technology Services
ID: 40354488
I would check the Exchange proxy settings in Outlook.  

Tools -> Account Settings -> Change -> More Settings -> Connection Tab

ensure the checkbox for "On slow networks..." is checked.
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40356465
Thanks, good idea!  Am visiting them Tuesday next week so will have a look at a few of their PCs and see how that's configured.
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40359464
I've had a look, and "On slow networks, connect using HTTP first, then connect using TCP/IP" is indeed checked.

There's nothing else as far as I can see in the ordinary GUI that relates to optimising things for slow/high-latency network connections.  Perhaps there are some Registry tweaks that could be applied?
0
 
LVL 1

Accepted Solution

by:
wakatashi earned 0 total points
ID: 40424239
Well, we ended up giving up on Outlook connecting via RPC over HTTP (or whatever it's called now) and ended up connecting via IMAP instead.   A workaround with lots of disadvantages, of course, but it works better if not brilliantly.

Moral of the story - don't get yourself a satellite Internet connection unless you really really REALLY have no other option!

Thanks for your help, Acosta Technology Services.
0
 
LVL 1

Author Closing Comment

by:wakatashi
ID: 40432336
Found workaround myself (but not a very good one!)
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question