Re: RPC over HTTPS Performance issue

My experience is that regardless of how you set those checkboxes Outlook
will try a TCP connection in preference to an HTTPS one. Maybe yours is
different, but I've tried forcing HTTPS (for testing of course), and my
Outlook 2003 will always connect using TCP if it can.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9378741dhcce4o9fb0lrvo14ru4c083epu@xxxxxxxxxx
On Tue, 8 Jul 2008 07:13:01 -0700, skip
<skip@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Thanks for the reply, but i think you may be misunderstanding me. I am
running a single ex2003 spo2 front end server, and two ex 2003 sp2 backend
servers. All clients are running outlook 2007 sp1, and recently all
clients
have been configured for rpc over https. I thought that if you configured
the
outlook client for rpc over https, then the client would always talk to
front
end server where the proxy vs is located, are you suggesting that the
outlook
client can switch back to mapi/rpc if the front end server was not
available?

There are two checkboxes on the "Exchange proxy settings". One is "On
fast networks . . ." and the other is "on slow networks . . .". The
typical configuration is to check only the "On slow networks . . ."
box. When doen that way the Outlook client will use RPC-Over-HTTPS
only when it cannot connect directly to the mailbox server.

And, yes, if the Outlook client is using RPC-Over-HTTPS and a TCP/IP
connection becomes available then Outlook will switch to the TCP/IP
(i.e. high-speed) connection -- assuming the connection isn't a real
pig.

I guess i dont understand why anyone would configure all the internal
clients for rpc over https, i would think Microsoft would not recomend
this
setup.

They don't

I see the logic if the client is exteranl to the network, but this
change doenst make much sence if the clients are on the same network as
the
exchange servers.

You're correct. It doesn't make sense. That's why Ed's questioning why
you think your LAN-connected Outlook clients are using your Front-End
servers.

I would think with encryption and decryption that has to go
on with the rpc over https connection, all the proxing to the back end
exchange servers, and the overhead of client and front end sever having to
setup a https tunnel that contains rpc and mapi traffic, would all be
reason
why you wouldnt want to make rpc over https the primary way clients talk
to
the exhcange servers?

We're all in agreement on those points.
---
Rich Matheisen
MCSE+I, Exchange MVP


.