RPC to Go v.1

RPC to Go v.3 – Named Pipes

Microsoft Enterprise Networking Team — Wed, 29 Apr 2009 00:28:25 GMT

In this blog I’d like to give some information on what Named Pipes are, what a Named Pipes connection

re: RPC to Go v.1

Gaurav Bhambri — Mon, 16 Feb 2009 15:11:53 GMT

Was really understandable , and knowledegable.

Got teh hack of this eaisly and may researh it more on this

RPC to Go v.2

Microsoft Enterprise Networking Team — Fri, 05 Dec 2008 01:30:44 GMT

This post is an update to “ RPC to Go v.1 .”  I assume that you have read v.1 and have

re: RPC to Go v.1

dj_palindrome — Sun, 16 Nov 2008 00:23:26 GMT

Thanks for the great article. For some reason discussions of RPC always made me say - Huh?

It would be great if you could include a concrete example, like Outlook in Cached Exchange Mode. Then the abstract concepts might not make my eyes glaze over ;-)

re: RPC to Go v.1

Rich Chambers — Tue, 11 Nov 2008 18:13:14 GMT

Eric,

Thanks for your input. While Outlook "should not" be installed on the same computer as Exchange, it can be. It isn't a supported configuration scenario other than for test purposes--that should be noted.

File sharing wouldn't be a good example of RPC. The protocol used most in Windows is SMB. With Server 2008 and Vista we also use the WebDav protocol for file transfers.

Remote registry/remote computer management will use Named Pipes.

Thank again for the input.

-Rich Chambers

re: RPC to Go v.1

Eric Henson — Sat, 25 Oct 2008 05:55:06 GMT

quote:

Huh?: For instance, RPC allows one’s Outlook client to talk to an Exchange server… But if Outlook is installed on the Exchange server, RPC knows to get email locally.

:endquote

Outlook cannot be installed on an exchange server:

http://support.microsoft.com/kb/266418

You might want to use file sharing or remote registry service as an example.