Exhcange Stops working after adding a new DC and taking old DC offline.

Hi,

We currently run Exchange 2003 SP2 on a W2003 member server. We wanted to introduce a new DC  (2003)onsite to replace existing DC (2003). We installed the server, ran dcpromo, mvoed the DNS from the old DC to the new DC.

We then moved the FSMO roles for the old DC to the new DC. Both DCs are GCs.

We then updated the Recipient Update Service on the exchange box. When we took the existing DC offline exchange stopped working. DSAccess on the exchange box is set yo autodiscover but discovered nothing when the old DC was disconnected. We manually set DSaccess to look to the new DC but it did not wok.

Has anyone got any ideas? Have we missed something?

Regards
rh1798Asked:
Who is Participating?
 
rh1798Connect With a Mentor Author Commented:
No worries  t hewlett,

Just so you know this is now resolved. I did some further trawling of the knowledgebase yesterday and found a thread which suggested running forestprep and domainprep on the exchange box to help it recognise the other GC. I did this and then changed dsaccess to manually select the new DC.

This worked and about an hour later I reverted to automatic discovery and it picked up the new DC also so I am happy.

As this is my first question I am not sure what to do with the points though.
0
 
KCTSCommented:
Have you changed the Exchnage box so it points the the new DC as its preferred DNS server ?
0
 
ddanonimityCommented:
You may have to make sure there are no bridge connections between the old DC and the new one. Also if not already done uninstalling the exchange installation on the old DC would be a good idea as there will probably be some active directory information about the old controller which is screwing things up. Running the uninstall gets rid of these entries. Also make sure that all the mailboxes are set to your new DC and that you have connectors set up to recieve internal and external mail.

Let me know how it goes
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
rh1798Author Commented:
Thanks for the replies.

KTCS, Yes - The Dns on the Exchange box points to the new server. There are no external DNS servers specified.

ddanonimity - Neither DC has exchange installed on it. Exchange resides on its own member server so I am not sure if your post is relevant. We have an smtp connector to handle all inbound and outbound traffic on the exchange box.

Regards,
0
 
ddanonimityCommented:
Sorry I misread the post :P. I'm no expert on Exchange setups (currently in the middle of a desaster recovery on ours) . Just a shot in the dark but did you restart your services when you manually changed the DSAccess settings?
0
 
GeyybeccaCommented:
The most likely cause for this is your some settings within Exchange system Manager - firstly check Exchange System manager ---> Recipients-->Recipient Update service is this pointing to your old DC ?
0
 
rh1798Author Commented:
ddanonimity - Yeah I did restart the services after manually changing the dsaccess settings.

Geyybecca: - The recipient update service  is set to use the new DC.
0
 
t_hewlettCommented:
Have you run the dcdiag and netdiag to ensure the AD side of things is ok.
0
 
t_hewlettCommented:
And I assume there is nothing in the event logs to help? Have you tried enabling the trouble shooting options for the exchange servers? This will enable you to drill down on any errors that do show up, or are being reported in the event logs.
0
 
rh1798Author Commented:
Hi  t hewlett,

I have run dcdiag and netdiag and all the tests were passed successfully.

There were events in the event log on the exchange box when I first attempted to disconnect the old dc. I have not had the old dc offline for a while - too busy with other things - so unfortunately the events have been purged. The event I remember indicated that the exchange box could not contact the new DC.

I have turned up diagnostic logging in Exchange System manager. I assume this is what you mean by "enabling trobleshooting options for exchange server". If you did not mean diagnostic logging - how do I enable troublesooting?

I will attempt it again after hours tonight and update this thread accordingly with any relevant trapped events

Thanks for you help so far.

Regards,
0
 
t_hewlettCommented:
Yes I did mean the logging options. Bad English what can say I am after all English...... sorry about any confussion.
0
All Courses

From novice to tech pro — start learning today.