I am planning to implement RPC over HTTP for the following setup:Exchange 2003 Ent SP2 running on Windows 2003 Ent SP2Exchange server is a Global Catalog, and the only Exchange serverNo RPC proxy servers (service will be on Exchange server)Domain Controllers are Windows 2000 SP4, domain is in mixed modeAs far as I can tell, I cannot use RPC over HTTP with this current setup. All GC servers apparently have to be Win 2003. What I could help with is some explanation on how totranslate the requirements mentioned in this article:http://technet.microsoft.com/en-us/library/aa998943(EXCHG.65).aspx"Even though the client computer does not access the global catalog server directly, the RPC request from the client computer does not change as it passes from the client computer to the Exchange servers and then to the global catalog server. The global catalog server must be able to use the updated RPC protocol that the client computer uses."Since my Exchange server runs on Windows 2003 and it is a GC itself, will client requests ever hit the DCs? Can I implement RPC over HTTP with this setup or is it still a no go?Thanks

Hi,Generally speaking, to deploy the RPC over HTTP, we need to FE in the environment, since you have only one Exchange server, please try the following article to do this configuration:http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htmThanksAllen

Try this link for troubleshootinghttp://support.microsoft.com/default.aspx/kb/827330 Andrew Sword, MVP

Hi admin,good question, I think that this should work since Exchange itself is a GC and is running windows server 2003 sp2. Exchange would forward all nspi queries to itself before looking for another GC. so there should be no problems with this. But while i say that, it would be strongly reccomended that you upgrade your GC's to win 2k3. The link that Allen had mentioned is a very useful one for Rpc http on single servers. It has a tool for configuring the valid ports automatically :)Let me know if this helpsThanksSatishna