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: https://www.experts-exchange.com/questions/22501384/CANNOT-REMOVE-EXCHANGE-2003-SERVER-FROM-ACTIVE-DIRECTORY.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.
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: https://www.experts-exchange.com/questions/22501384/CANNOT-REMOVE-EXCHANGE-2003-SERVER-FROM-ACTIVE-DIRECTORY.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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In ADSIEdit.
ASKER
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.
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.
ASKER
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For Clarity, by everything below it, I mean all the folders that are children of the CN=EXCHANGE object itself. :D
ASKER
Okay. I have two domain controllers. Do I need to do the same on both? I'm taking System State backup now...
No. Only make changes on one DC (preferably the PDC). Then let the changes replicate or force replication.
ASKER
How can I do that? Where I can do? Thanks.