About RPC publishing
| Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
When you install ISA Server, two default RPC protocol definitions are provided:
Any RPC Server. If this protocol definition is allowed in a server publishing rule, then ISA Server will map any inbound RPC requests to the published RPC server. If the UUID is registered on the RPC server, access to the procedure is given. If the UUID is not registered on the RPC server, the request is dropped.
Exchange RPC Server. A list of UUID interfaces used for Exchange are defined as an RPC protocol definition. You can use this protocol definition in server publishing rules to deny or allow access to specific Exchange functions.
These default RPC protocol definitions cannot be modified or deleted.
You can use the New RPC Protocol Definition Wizard to create additional RPC protocol definitions. Using the wizard, you can select UUID interfaces from a list of interfaces available on the RPC server. Or, you can define the interfaces manually. If you do not specify any interfaces for the incoming RPC protocol definition, server publishing rules that allow this protocol definition do not allow any traffic.
After you create incoming RPC protocol definitions, you can use them in a server publishing rule so that external clients, who are requesting remote procedure calls on the internal RPC server, can access these procedures (UUIDs).
For instructions on how to create an RPC protocol definition, see Create an RPC protocol definition. For instructions on how to create a server publishing rule, see Create a server publishing rule. For a description of how ISA Server filters RPC requests, see About RPC.