I have Exchange 2003 SP2 and want to implement “RPC over HTTP”. But I only have ONE Exchange Server and there is no particular front end server. I like to get guide to configure it. Is there any drawback of implementing like that using a single server? Thanks in advance. Kyi

Hi, Have a look into following links : http://www.petri.co.il/how-can-i-configure-rpc-over-https-on-exchange-2003-single-server-scenario.htm http://www.msexchange.org/tutorials/Implementing-RPC-over-HTTPS-single-Exchange-Server-2003-environment.html http://blogs.techrepublic.com.com/networking/?p=292 These article might help you understand.Ripu Daman Mina | MCSE 2003 & MCSA Messaging

You can deploy RPC Over HTTP in a single server Scenario. Ripu has provided all good reference articles. Here are some more.. http://technet.microsoft.com/en-us/library/bb124876(EXCHG.65).aspx http://technet.microsoft.com/en-us/library/aa998943(EXCHG.65).aspx http://technet.microsoft.com/en-us/library/bb124796(EXCHG.65).aspx Front-end/back-end scenario In this scenario, you have the following roles: One or more front-end servers running Exchange Server 2003 without service packs One or more back-end servers running Exchange Server 2003 without service packs One or more global catalog servers These three roles are all deployed on separate servers. Your Exchange back-end servers can be clustered. For detailed steps for how to deploy RPC over HTTP in this scenario, see How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, Front-End/Back-End Scenario. Front-end/back-end scenario where at least one global catalog server is also a back-end Exchange server In this scenario, you have the following roles: One or more front-end servers running Exchange Server 2003 without service packs At least one server that is both an Exchange back-end server and a global catalog server. You can have additional back-end servers and global catalog servers on separate servers. Your Exchange back-end servers can be clustered. For detailed steps for how to deploy RPC over HTTP in this scenario, see How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, Front-End/Back-End Scenario, Back End on Global Catalog Server. No front-end server In this scenario, you have the following roles: One or more back-end servers running Exchange Server 2003 without service packs One or more global catalog servers These two roles are on separate servers. If your back-end servers are clustered, you cannot designate them as RPC proxy servers. You must designate a separate server as the RPC proxy server. For detailed steps about how to deploy RPC over HTTP in this scenario, see How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, No Front-End Server. No front-end server where at least one global catalog server is also a back-end Exchange server In this scenario, you have the following roles: One or more back-end servers running Exchange Server 2003 without service packs. At least one of these servers is also a global catalog server. You can have additional back-end servers and global catalog servers on separate servers. If your back-end servers are clustered, you cannot designate them as RPC proxy servers. You must designate a separate server as the RPC proxy server. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Kyi, Above gave some very good information, if you have any other issue, plaese tell us.

Any update?Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

I have successfully configured my Exchange server to be used with RPC over HTTPS and really appreciate all of your help and suggestions in here. In fact, domain controller and exchange server are not in the same box in here. Thanks. Kyi