My company is currently using RPC over HTTP on a single server using the No
Front End Server scenario.
The current server is getting overused and performance is degrading so we
are bringing up a second Exchange 2003 back-end server. My understanding is
that we now also need an Exchange 2003 front-end server as well. I have
both of the new servers configured, with Exchange installed and part of the
Exchange organization. I have a few questions about the next steps.
If I configure the new server as a front-end server for testing will that
make any changes to the existing back-end server that is currently handling
the RPC-HTTP and OWA connections? My plan would be to do initial testing
using a different URL on the new front-end server and then later migrate the
existing URL and certificate from the current back-end only server. I know
that front end servers will dynamically update when a back end server is
added and I'm just concerned that if the back-end server might update
someting when a front-end server is added so users can no longer connect to
I have not found any documentation on making this transition from back-end
only to front-end back end setup. Technet gives instructions titled "How to
Deploy RPC over HTTP for the First Time on Exchange Server 2003 SP1
(Front-End/Back-End Scenario)" but we are not deploying RPC over HTTP for
the first time, we want to transition an existing setup.
Can anyone point me to any documentation that covers our scenario?
15. End-to-End VOIP