<div>
<div class="content wysiwyg-content">
We have a single Exchange 2003 server (no Front-end obviously) setup for RPC over HTTPS and it has been working fine for about 300 remote Outlook users.<br />
<br />
Soon we will be installing a 2nd Exchange server in the same organization and then move some of these mailboxes there. I intend to modify ValidPorts subkey in registry on the first Exchange server, where OWA/RPCproxy is located, to include information about the new Exchange server.<br />
<br />
It is my understanding that remote Outlooks need not be touched. They should be automatically redirected to the new Exchange server if their mailboxes have moved there. I need confirmation of this. Thanks.<br />
<br />
Jay
</div>
</div>


We have a single Exchange 2003 server (no Front-end obviously) setup for RPC over HTTPS and it has been working fine for about 300 remote Outlook users.

Soon we will be installing a 2nd Exchange server in the same organization and then move some of these mailboxes there. I intend to modify ValidPorts subkey in registry on the first Exchange server, where OWA/RPCproxy is located, to include information about the new Exchange server.

It is my understanding that remote Outlooks need not be touched. They should be automatically redirected to the new Exchange server if their mailboxes have moved there. I need confirmation of this. Thanks.

Jay

Outlook RPC-over-HTTPS clients and Additiona Exchange Server

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.