Re: RPC over HTTPS Performance issue

My experience is that Outlook 2003 will use TCP/IP when it is available and
switch to RPC over HTTPS when necessary. I don't know if Outlook 2007
changes this behavior, though. Are you seeing your Outlook 2007 always
using RPC over HTTPS? I'm not sure why you'd want to do that in preference,
since this method only really benefits you when users are outside your
firewall. Are you sure you're not confusing RPC over HTTPS with cached
mode? They're two different things although often used together.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"skip" <shofmann@xxxxxxx> wrote in message
news:50529ED6-D65C-4DBD-A1FD-83A04BDD7B6E@xxxxxxxxxxxxxxxx
Hello all

I am the exchange admin for our company currently I manage 2 exchange 2003
sp2 backend servers, and one exchange 2003 sp2 front end server. Recently
the help desk staff upgraded the office to 2007 sp1, and part of the
upgrade was to configure all the outlook clients so they use rpc over
https. There are roughly 600 clients on the network, so now i have 600
users talking to my exchange front end server first before they talk to
the one of the back end servers. What if any performance issues can i
expect from this configuration? i would think that having to talk to a
front end server first and then, have the front end server have to proxy
the request back to one of the back end servers would be more of a
performance hit vs talking directly the mailbox server using rpc



.

Loading