Article ID: 958178 - Last Review: November 19, 2008 - Revision: 1.0
A Windows Server 2008 update lets you use the RPC redirection (RDR) interface to enable or disable custom load balancing based on server name and port number
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
A Windows Server 2008 update is available that lets you use the remote procedure call (RPC) redirection (RDR) interface to enable or disable custom load balancing based on
server name and port number.
Currently,
RPC maintains a mapping from resource IDs to server names in the registry. RPC
also maintains a mapping to a specific resource ID if no
resource ID is specified by the calling application. This update
provides more fine-grained control over
resource IDs when no resource
ID is
specified by the calling application.
After you apply this update, the
RDR interface enables applications that use RPC to set a resource ID for an
incoming connection based on a
custom
rule,
such as a mapping between a session ID and a combination of "server name plus
port number."
For more
information about how to download Microsoft support files, click the following
article number to view the article in the Microsoft Knowledge Base:
119591
(http://support.microsoft.com/kb/119591/
)
How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most
current virus-detection software that was available on the date that the file
was posted. The file is stored on security-enhanced servers that help prevent
any unauthorized changes to the file.
You must restart the computer after you apply this update.
Hotfix replacement information
This update does not replace any other updates.
File information
The English version of this hotfix has the file
attributes (or later file attributes) that are listed in the following table.
The dates and times for these files are listed in Coordinated Universal Time
(UTC). When you view the file information, it is converted to local time. To
find the difference between UTC and local time, use the Time
Zone tab in the Date and Time item in Control
Panel.
Windows Server 2008 file information notes
The files that apply to a specific product, milestone (RTM,
SPn), and service branch (LDR, GDR) can be identified by examining the file
version numbers as shown in the following table.
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.0.6001.22xxx
Windows Vista SP1 and
Windows Server 2008 SP1
SP1
LDR
Service Pack 1 is integrated into Windows Server 2008.
The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
For all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Rpchttp.dll
6.0.6001.22276
127,488
30-Sep-2008
05:03
x86
Lbservice.dll
6.0.6001.22276
20,992
30-Sep-2008
05:03
x86
Rpcproxy.dll
6.0.6001.22276
48,640
30-Sep-2008
05:03
x86
Rpcproxymigrationplugin.dll
6.0.6001.22276
38,400
30-Sep-2008
05:03
x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Rpchttp.dll
6.0.6001.22276
164,352
30-Sep-2008
05:22
x64
Lbservice.dll
6.0.6001.22276
24,064
30-Sep-2008
05:22
x64
Rpcproxy.dll
6.0.6001.22276
57,856
30-Sep-2008
05:22
x64
Rpcproxymigrationplugin.dll
6.0.6001.22276
44,032
30-Sep-2008
05:22
x64
Rpchttp.dll
6.0.6001.22276
127,488
30-Sep-2008
05:03
x86
For all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Rpchttp.dll
6.0.6001.22276
370,688
30-Sep-2008
06:29
IA-64
Lbservice.dll
6.0.6001.22276
41,472
30-Sep-2008
06:25
IA-64
Rpcproxy.dll
6.0.6001.22276
116,736
30-Sep-2008
06:29
IA-64
Rpcproxymigrationplugin.dll
6.0.6001.22276
102,912
30-Sep-2008
06:29
IA-64
Rpchttp.dll
6.0.6001.22276
127,488
30-Sep-2008
05:03
x86
The RDR interface
is useful
in the following scenarios:
Renaming Endpoint servers Proxy server names are usually
static. However, internal server names can change based on a company's internal
network. Therefore,
you can use the RDR interface to reduce the
possibility of
clients discovering new names of internal servers.
Nondisclosure of internal server names The
RDR interface lets companies keep
internal server names private, and it discloses only the proxy server name.
Custom access checks, redirecting, and load balancing The
RDR interface allows custom
load balancing rules, access checks, and redirecting. However,
custom load balancing may not work in Windows Server 2008 for
applications that use RPC.