<div>
<div class="content wysiwyg-content">
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. &nbsp;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: <a href="http://support.microsoft.com/?kbid=154596" rel="ugc">http://support.microsoft.com/?kbid=154596</a>. &nbsp;<br />
<br />
Before applying this I wanted to be sure that this would in no way affect my RPC over HTTPS configuration for exchange
</div>
</div>


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

RPC port limiting and RPC/HTTPS exchange functionality.

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.