Hi,

I've just got Outlook Anywhere/RPC over HTTPS working, and I've been
testing the setup of Outlook. But I seem to be having a few problems.

Firstly, I tried just adding the Exchange Proxy settings to my
existing profile. This works OK when out of the office, users are
asked to authenticate to the PRC proxy, and then Outlook connects,
pretty quickly 10 - 20 seconds. However, when in the office, users are
still asked to authenticate, I assume Outlook is still trying to
connect to the RPC Proxy, rather than going straight to the Exchange
server. This is also highlighted because we run Office Live Comms
server, and the client pops up at start-up, and now asks the user to
authenticate before they've even opened Outlook.

I've tried un-checking the 'On fast networks connect using HTTP first,
then TCP/IP' setting, however this has an adverse effect when out of
the office, in that when you open Outlook, it hangs for about 2
minutes, with just the title bar, and a blank white screen, I assume
while Outlook tries to connect using TCP/IP, fails, and then tries
HTTP.

So the only option I can think of for the moment is to use 2 profiles,
the first for 'In the office', set as default, without the Exchange
proxy settings, so users/LCS do not have to authenticate, and then one
for 'Out of office' with the Exchange Proxy settings, and both options
for 'slow/fast networks use HTTP first' checked. The trouble with this
option is that users will moan about having to perform yet another
step to open Outlook, even if its just 1 button click (some of our
users will moan about anything), and it also means that if they setup
any rules in one profile, they will have to duplicate them in the
second profile.

Is there anyway to set Outlook up with one profile, so that when out
of the office it will use the Exchange proxy settings, but be clever
enough to realise that when in the office it doesn't need to?

I think the trouble with the 'On fast/slow networks use HTTP first'
option, is that most people now a days connect either from home when
connected to a LAN/WLAN or using mobile broadband, which must fall
into the fast networks category. This means Outlook will always think
its on a fast network, and telling it to only connect with HTTP over
on a slow network is pointless.

Any help or suggestions would be much appreciated!

Ben

I hear your pain but over time the users can get used to the 2 minute wait
while Outlook tries a TCP connection and then eventually fails over to
HTTPS.

As for speed threshold of what is considered fast/slow, this can be adjusted
using a GPO/registry key. I believe the default is 128Kbits. I've tried
playing with this, but unfortunately there isn't a perfect solution when you
have a person that can plug into a soho network that has speeds of
100/1000Mbit. The key becomes moot because the operating system/outlook
only looks at link speed of network interface. Doesn't give a hoot about
actual speed between the 2 points.


"Ben" wrote in message
...
Hi,

I've just got Outlook Anywhere/RPC over HTTPS working, and I've been
testing the setup of Outlook. But I seem to be having a few problems.

Firstly, I tried just adding the Exchange Proxy settings to my
existing profile. This works OK when out of the office, users are
asked to authenticate to the PRC proxy, and then Outlook connects,
pretty quickly 10 - 20 seconds. However, when in the office, users are
still asked to authenticate, I assume Outlook is still trying to
connect to the RPC Proxy, rather than going straight to the Exchange
server. This is also highlighted because we run Office Live Comms
server, and the client pops up at start-up, and now asks the user to
authenticate before they've even opened Outlook.

I've tried un-checking the 'On fast networks connect using HTTP first,
then TCP/IP' setting, however this has an adverse effect when out of
the office, in that when you open Outlook, it hangs for about 2
minutes, with just the title bar, and a blank white screen, I assume
while Outlook tries to connect using TCP/IP, fails, and then tries
HTTP.

So the only option I can think of for the moment is to use 2 profiles,
the first for 'In the office', set as default, without the Exchange
proxy settings, so users/LCS do not have to authenticate, and then one
for 'Out of office' with the Exchange Proxy settings, and both options
for 'slow/fast networks use HTTP first' checked. The trouble with this
option is that users will moan about having to perform yet another
step to open Outlook, even if its just 1 button click (some of our
users will moan about anything), and it also means that if they setup
any rules in one profile, they will have to duplicate them in the
second profile.

Is there anyway to set Outlook up with one profile, so that when out
of the office it will use the Exchange proxy settings, but be clever
enough to realise that when in the office it doesn't need to?

I think the trouble with the 'On fast/slow networks use HTTP first'
option, is that most people now a days connect either from home when
connected to a LAN/WLAN or using mobile broadband, which must fall
into the fast networks category. This means Outlook will always think
its on a fast network, and telling it to only connect with HTTP over
on a slow network is pointless.

Any help or suggestions would be much appreciated!

Ben