How do I convince a 2003 Exchange Server to look to a GC/DC other than the one specified in the key: HKLM\software\microsoft\AD
s\provider
s\LDAP\
At what point will Exchange stop using the old value and create a new value that reflects the new 2003 DC/GC in:
%SystemRoot%\SchCache\<DC fqdm>.sch
The reason being, I am deploying RPC over HTTP and I need the Exchange Server to authenticate with the new 2003 DC/GC recently deployed, rather than the older 2000 DC/GC that was the highest DC in place at the time that this Exchange Server was originally deployed a couple years or so ago.
Without revisiting too much in terms of the aspects of configuring RPC over HTTP, it seems that this setting figures in to the equation. When I run Outlook with the /rpcdiag switch from outside the network, during the connection attempt I can see that it successfully contacts the Exchange server, and then that the Exchange server is in fact querying the old non-RPC-solution-capable 2000 DC/GC server.
I have specified in Exchange Manager (Directory Access tab) to manually point to the 2003 DC/GC, and have also changed the PDC designation in Recipient Update Services. The LDAP Port is the default 3268 and has not been changed.
Perhaps a reboot required to make this change take affect? It is deployed in a high availability environment.
Further, I have verified using netdiag that all tests are passed. The exchange server is NOT a domain controller.
Exchange Server 2003 SP2 on Windows 2003 R2 SP1
New DC/GC: Windows 2003 R2 SP2
Old DC/GC: Windows 2000 SP4
Thanks for any insights!
Start Free Trial