• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 772
  • Last Modified:

Unable to remove Exchange 2003 references from Active Directory

Hello,

OLD: Exchange 2003 on a dedicated server
NEW: Exchange 2010 on a dedicated server
CURRENT: Server 2003 R2 Domain Controller in a dedicated server

NOTE: Exchange 2003 IS NOT Installed on domain controller.

1.) Lot of messages in Exchange 2010 Unreachable Queue
2.) Unable to remove refences of old Exchange 2003 from Active Directory

We recently upgraded from Exchange 2003 to 2010. Installation is successful and we migrated everything to new Exchange 2010 server. Uninstalled Exchange 2003 from old server. Still I found some references to old Exchange 2003 in Management Console in 2010. i.e., It's trying to deliver messages to old mail.

Issue 1:
We have a lot (between 20-40) messages in the Queue in Exchange 2010 Management Console. I tried to reprocess all the messages in the Unreachable queue using Microsoft commands, but nothing works.

Issue 2:
After further digging I found that, messages are queued in the Unreachable queue whenever the Exchnage 2010 server is down and the those messages are trying to deliver to old Exchange server 2003 since there are some references exist in Active Directory. But we already uninstalled Exchange 2003.

For the Issue 2, I'm facing same issue as described in this thread by someone else: http://www.experts-exchange.com/Software/Server_Software/File_Servers/Active_Directory/Q_22501384.html

I opened ADISEDIT.MSC from Domain Controller, and it shows the Microsoft Exchange in the CN=Server section, BUT I'M CONSFUSED ON WHETHER THIS SHOWING 2003 or 2010.

The Old Exhcnage 2003 server is turned off, but already uninstalled Exchnage 2003 properly.

Final Question: How can I remove old Exchange 2003 references from entire domain (active directory etc)?

In this site: http://www.msexchange.org/tutorials/Remove-Exchange-server-entire-Exchange-organization.html

The next steps are the following:

¿      Shut down the member server or domain controller where Exchange 2003 was installed.
¿      Restart the domain controller that you were using to remove the Exchange organization.
¿      Allow sufficient time for replication to occur between the domain controllers.
¿      Save the setup logs.
¿      Rerun setup /forestprep.
¿      Rerun setup /domainprep. If this is the same server that was used previously, move the old setup logs out.
¿      Verify permissions in the Exchange 5.5 organization. The user who is logged on must be in the group that was designated during forestprep and must have permissions on the Exchange 5.5 Organization, Site, and Configuration containers.
¿      Make sure that you can connect to all the Exchange 5.5 computers by using the Administrator program from the intended Exchange 2003 installation server, and then view the properties of the Exchange 5.5 servers.
¿      Remove the Administrator program from this server.
¿      Install Exchange 2003.

Thank you so much for reading my long thread and any further help would be greatly appreciated. Thank you.
0
SrinathS
Asked:
SrinathS
  • 6
  • 4
2 Solutions
 
Adam BrownSr Solutions ArchitectCommented:
The Microsoft Exchange entry in ADSIEdit it the definition for your entire Exchange Environment. I'm not sure what you mean by seeing it under the Server component, since that should show up under Services. At any rate, if you go to Configuration\Services\Microsoft Exchange\<Organization Name>\Administrative Groups\Exchange Administrative Group  (FYDIBOHF23SPDLT)\Servers
you'll see a list of Exchange servers in your environment. If your old Exchange server is listed, remove it and see if that resolves your issue.
0
 
SrinathSAuthor Commented:
At any rate, if you go to Configuration\Services\Microsoft Exchange\<Organization Name>\Administrative Groups\Exchange Administrative Group  (FYDIBOHF23SPDLT)\Servers
you'll see a list of Exchange servers in your environment.

How can I do that? Where I can do? Thanks.
0
 
Adam BrownSr Solutions ArchitectCommented:
In ADSIEdit.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
SrinathSAuthor Commented:
Do I need to open ADSIEDIT tool in Domain Controller? Note that I already uninstalled Exchange 2003 from the old exchange server. But that old server (2003 r2) is still connected to the domain controller.
0
 
Adam BrownSr Solutions ArchitectCommented:
Yeah. You should be able to run ADSIEdit from any Domain Controller. Basically, the entries for the old exchange server still exist in the AD schema, and you can only remove those in ADSIEdit.
0
 
SrinathSAuthor Commented:
Okay.

I found two groups named "Exchange Administrator Group" and "First Administrator Group". I think the First Administrator Group is related to Exchange 2003. Am I right? Do I need delete that group completely?

Is there way to backup those details before deleting? Sorry I'm novice on Exchange. Thanks. ADSIEDIT
0
 
Adam BrownSr Solutions ArchitectCommented:
No. Only remove the CN=EXCHANGE entry and everything below it. You should be able to leave the Administrative Group there, but it will be inactive when the server object is removed.
0
 
Adam BrownSr Solutions ArchitectCommented:
For Clarity, by everything below it, I mean all the folders that are children of the CN=EXCHANGE object itself. :D
0
 
SrinathSAuthor Commented:
Okay. I have two domain controllers. Do I need to do the same on both? I'm taking System State backup now...
0
 
Adam BrownSr Solutions ArchitectCommented:
No. Only make changes on one DC (preferably the PDC). Then let the changes replicate or force replication.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now