RUS configuation in DR scenario - can't change DC 1

[LordMarshal]

I am currently testing DR processes in our lab and while I can restore a functional (the services start) Exchange server, I am unable to modify the RUS to point it at a new domain controller (since the one it wants to point to is "dead").

The exact error is in the System Manager when I attempt to browse for the new server. It gives me an object browser error that it cannot find any place to browse objects from. (The event that pops up is similar to the one associated with System Attendant error 1005 - the domain is not available - which I also fixed by ensuring my DR domain controller was a GC as well)

I have confirmed the following:
- My exchange server can see the domain controller and GC server
- I can authenticate to the domain and use AD Users and Computers
- I have properly seized all the FSMO roles to my DR domain controller using ntdsutil
- I have found references to using ADSI to modify this attribute, but can not find the attribute in the 2000 AD schema (I am thinking it is a 2003 AD attribute)

I have missed something incredibly simple I am sure and am hoping someone has seen this before. Can I simply delete and recreate my RUS's? ANy help is appreciated!

 

[netometer]

Hi!

Just a couple of questions - may be they'll help you figure out what the problem is:
1. Have you cleaned the AD integrated zone from server records belonging to non-existent servers?
2. Have you cleaned the metada using NTDSUTIL?
3. You should delete the non-existent servers using also the ADSI edit tool.

Is it possible that the exchange server is trying to query a non-existent GC? Can you put a sniffer and check what requests the exchange is sending out?

NetoMeter

http://www.netometer.net