Microsoft RPC

<h2 id="example">Example</h2>
<p>The DCE 1.0 reference implementation only allows such constructs as size_is(len), or possibly size_is(len-1). MSRPC allows much more complex constructs such as size_is(len / 2 - 1) and even length_is ((max & ~0x7) + 0x7), a common expression in DCOM IDL files.
</p>
<h2 id="use">Use</h2>
<p>MSRPC was used by Microsoft to seamlessly create a client/server model in <a href="/facts/Windows_NT/EtccWvxQ">Windows NT</a>, with very little effort. For example, the <a href="/facts/Windows_Server_domain/tAzIX31E">Windows Server domains</a> protocols are entirely MSRPC based, as is Microsoft's <a href="/facts/Domain_Name_System/rfxdWFsj">DNS</a> administrative tool. <a href="/facts/Microsoft_Exchange_Server/9pu8G4It">Microsoft Exchange Server</a> 5.5's administrative front-ends are all MSRPC client/server applications, and its <a href="/facts/MAPI/Dpbq9ozA">MAPI</a> was made more secure by "proxying" MAPI over a set of simple MSRPC functions that enable encryption at the MSRPC layer without involving the MAPI protocol.
</p>
<h2 id="history">History</h2>
<p>MSRPC is derived from the <a href="/facts/Distributed_Computing_Environment/0vpvuBhs">Distributed Computing Environment</a> 1.2 reference implementation from the <a href="/facts/Open_Software_Foundation/sBn7Q7gt">Open Software Foundation</a>, but has been copyrighted by Microsoft. DCE/RPC was originally commissioned by the Open Software Foundation, an industry consortium to set vendor- and technology-neutral open standards for computing infrastructure. None of the <a href="/facts/Unix/0pNL2seI">Unix</a> vendors (now represented by the <a href="/facts/Open_Group/uRoDdEae">Open Group</a>), wanted to use the complex DCE or such components as DCE/RPC at the time. 
</p><p>Microsoft's <a href="/facts/Component_Object_Model/2DtIAufW">Component Object Model</a> is based heavily on MSRPC, adding interfaces and inheritance. The marshalling semantics of DCE/RPC are used to serialize method calls and results between processes with separate address spaces, albeit COM did not initially allow network calls between different machines.
</p><p>With <a href="/facts/Distributed_Component_Object_Model/mpDM1JXX">Distributed Component Object Model</a> (DCOM), COM was extended to software components distributed across several networked computers. DCOM, which originally was called "Network OLE", extends Microsoft's COM, and provides the communication substrate under Microsoft's COM+ application server infrastructure.
</p>

<ul><li>Shirley, John; Rosenberry, Ward (1995). <a href="https://archive.org/details/microsoftrpc00shirmiss"><i>Microsoft RPC programming guide</i></a>. O'Reilly & Associates, Inc. Open Book. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 1-56592-070-8.</li>
<li>Luke Kenneth Casson Leighton (1999). <i>DCE/RPC over SMB: Samba and Windows NT Domain Internals</i>. Sams. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 1-57870-150-3.</li></ul>
<h2 id="external-links">External links</h2>
<ul><li><a href="https://docs.microsoft.com/en-us/windows/win32/rpc">MSRPC at MSDN</a></li>
<li><a href="http://www.hsc.fr/ressources/articles/win_net_srv/chap_msrpc.html">[1]</a>, a chapter on MSRPC from a technical article by Jean-Baptiste Marchand.</li></ul>

Microsoft RPC open-in-new

Microsoft RPC