Welcome to TechNet Blogs Sign in | Join | Help

Implementing RPC over HTTP

Eileen here.....

I seem to get more questions about using RPC over HTTP than anything else, and here at Chesterfield has been no exception.  We use RPC over HTTP at Microsoft, and I hardly ever use VPN just to get my mails.  This is simple to implement, providing you follow the setup instructions and works really well.

So here's what you need to do...

1: Read the benefits that you get with RPC over HTTP

2: Read the RPC over HTTP Deployment scenarios document 

3: Make sure you comply with the System Requirements documentation

4: Follow the steps in the how to Deploy RPC over HTTP on a front end server document 

So if something goes wrong with your deployment, you'll need to do a bit of troubleshooting so that you can identify where you may have had a problem.  For this, you need to have a look at one of my previous blog entries where I talked about this very topic...

And this is what you need to deploy RPC over HTTP and get truly mobile..

Eileen Brown

 

Published Thursday, December 01, 2005 1:46 PM by TechNet UK - Exchange Tour

Comments

# re: Implementing RPC over HTTP

Wednesday, September 12, 2007 5:51 PM by mgarrett

I am trying to setup RPC over HTTPS on a new exchange server (back-end/no front end).  I already have it working on our production Exchange server and have taken good notes on how to set this up but it has been 2 years.  On the new server it isn't working on the extranet or even a computer on our intranet but not a domain member computer.  I've used rpcping utility to diagnose the problem and I'm getting 12175 & 1722 errors on the new server but all rpcpings to old server are fine.  I have read many, many things to check and am at my wit's end.  I'm using Basic Authentication with SSL.  The certificate Common Name is the same FQDN as the server.  My computers are trusting the root certificate as it is a certificate created on our own CA.  It hasn't expired so the date is good.  OWA for this new server is working with HTTPS so it seems the certificate is good for that.  I've gone through MS TechNet Troubleshooting RPC over HTTP Communications (http://technet.microsoft.com/en-us/library/bb124649.aspx).

Anonymous comments are disabled
 
Page view tracker