[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 280
  • Last Modified:

RPC port limiting and RPC/HTTPS exchange functionality.

I currently force all of my users to use RPC/HTTPS for full outllook connections. We are working with more and more wireless and USB tethered devices and periodically run into issue with RPC requests.  We are thinking of using RPC for such devices but do not want to use dynamic RPC port alllocation. The following Microsoft KB article discusses the procedure for defining a set of ports for RPC to use: http://support.microsoft.com/?kbid=154596.  

Before applying this I wanted to be sure that this would in no way affect my RPC over HTTPS configuration for exchange
1 Solution
It will work fine, we currnently have this setup to allow none 2003 clients to connect via a vpn system and at the same time our external 2003 clients use RPC over HTTP.


Dave J

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now