Re: RPC over HTTPS Performance issue

Hi Ed

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?

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. 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. 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?

Many thanks in advance

"Ed Crowley [MVP]" wrote:

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




.

Relevant Pages

  • Re: Automatic Updates security concern
    ... If those servers are not configured to support SSL ... on tcp 443 then the update clients will be forced to use tcp ... Is there any way of setting the AU repository so it never uses https (tcp ... clients end up ...
    (microsoft.public.security)
  • Re: Certificate requirements for OWA
    ... Thank you Mark. ... to use a FE server topology, especially for RPC over HTTPS in W2K3? ... >>couple of load balanced FE servers. ...
    (microsoft.public.exchange2000.admin)
  • RE: RPC over HTTP
    ... If you want to use RPC over HTTP in your domain, ... clients will access using RPC over HTTP, such as mailbox servers and public ... *All global catalog servers that Outlook 2003 clients and Exchange Server ...
    (microsoft.public.exchange.setup)
  • Re: RPC over HTTPS Performance issue
    ... All clients are running outlook 2007 sp1, ... have been configured for rpc over https. ... exchange servers. ...
    (microsoft.public.exchange.admin)
  • Strange RPC/HTTP behavior
    ... RPC clients. ... RPC over HTTPs works well, clients connect, mail comes in, ... I know there are scripts to disable that button but the customer would ...
    (microsoft.public.isaserver)