|
Configure
all your global catalogs to use specific
ports for RPC over HTTP for directory
services
Exchange Server 2003
Service Pack 1 note: Exchange Server
2003 Service Pack 1 has a new built-in
RPC over HTTP/S GUI setting on the
Exchange Server properties page in
Exchange System Manager. If you
configure the RPC over HTTP/S option
from the GUI, there is NOT need to make
any manual changes in the Registry.
To make the changes via
the GUI follow these steps:
-
Click Start, point to
Microsoft Exchange, and then click
System Manager.
-
Expand your
organization, expand Administrative
Groups > First Administrative Group
> Servers.
-
Right-click on your
server name and select Properties.
-
On the General
tab, verify that you have SP1
installed. Verify that a tab called
RPC-HTTP is present.
-
On the RPC-HTTP
tab, click on RPC-HTTP Back-End
Server.
You might get an
error:
Exchange
System Manager
There is no RPC-HTTP front-end
in your Exchange organization.
There must be at least one
RPC-HTTP front-end server in the
organization before the RPC-HTTP
back-end server can be accessed.
Acknowledge the
error.
-
Click Ok all
the way out.
If you did not install
Exchange Server 2003 SP1, or if you did
not configure the RPC over HTTP/S option
from the GUI, then you MUST manually
perform the changes in the Registry.
To do this, follow these
steps:
-
Start Registry
Editor.
-
Locate and then click
the following registry subkey:
On the Edit menu,
point to New, and then click
Multi-String Value.
Note Make sure that
you select the correct value type
for the registry subkey. If the
registry subkey type is set to
anything other than Multi-String
Value, you may experience problems.
-
Name the new registry
value NSPI interface protocol
sequences.
-
Right-click NSPI
interface protocol sequences,
and then click Modify.
-
In the Value data
box, type
and then click OK.
-
Quit Registry Editor,
and then restart the computer.
|
