We are getting ready to install a Exchange 2010 server in our Exchange 2007 environment. When we try to raise the level of the domain, it fails and states that it can communicate with the Exchange 2003 server, which was replaced by the 2007 before my time. I did notice on the 2007 server that it keeps looking for the 2003 server and genereates the following error: The Exchange 2000 or Exchange 2003 server EXCHANGE.domainName.org was found in Exchange 2007 routing group CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domainName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainName,DC=org in routing tables. It appears that the 2003 was not removed properly, so 2010 (and 2007) still thinks it is there. Is there an easy way to fix this?

If all of the server's configuration data is still in AD, you can do a disaster recovery for the 2003 server, then uninstall it properly.

You could also delete the 2003 server from AD using ADSI Edit as this is what the setup is running into before it will proceed. The path was provided in your post so that is the where you will need to delete the object as the RG still thinks the 2003 server is active inside it. You also may need to delete the 2003 Server from AD all together but I would start with error path first. Be careful usiing ADSI Edit, I would take a System State backup of your GC before performing any ADSI Edit functions as its best practice. If you are not comfortable in performing these functions I would call Microsoft PSS to assist.MVP Exchange Server

Using ADSI Edit, looking in the Exchange Routing Group, the Exchange 2003 server is not listed in the Connections. The only area that I could find reference to the 2003 server was in CN=EXCHANGE,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=domainName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainName,DC=org. This is under the CN=First Administrative Group, not the CN=Exchange Administrative Group (FYDIBOHF23SPDLT).

That is where it should be located so you can go ahead and delete the Server object and the Exchange 2010 install should proceed.MVP Exchange Server

Deleting the CN=First Administrative Group wont break the Exchange 2007 install will it?

I would leave it at this point, not going to hurt anything. At some point cleaning or deleting the First Administrative Group would be preferred but lets get the Exchange 2010 install going first.MVP Exchange Server

Just for clarificarion, the only thing I should have to do is remove the CN=Exchange container under the CN=Servers container in the First Administrative Group.

No, delete the Exchange 2003 server from CN=Servers container.MVP Exchange Server

Also take a System State backup of your AD just as a precaution, I always do this before performing any operations in ADSI Edit.MVP Exchange Server

Hi harveyerice, Any updates on this issue? After follow John Oliver’s suggestion, you can run Exchange Best practices Analyzer to see if everything comes back clean. Thanks, EvanPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, http://www.petri.co.il/forums/showthread.php?t=37992 this link may help you. Sajjad Sajjad