Hi everyone, We have a 2008 active directory domain in 2003 functional mode. the functional mode is serve 2003 although I think this detail dont affect.We had a Exchange 2003, then we decided to expand the organization installing a exchange 2010, and moved the mailboxes to the new server. After this, the 2003 server crashed so it left the domain without being decomissioned and leave the domain in a "civilized manner" (uninstalling Exchange 2003). Now there are references in Active Directory and the Exchange 2010 to the old server. How can i delete them?what i am looking for is a way to "seize" all the roles and tasks that were done by Exchange 2003 and put them to work in Exchange 2010. Problems with the old exchange 2003 that i find are: (ordered A, B, C)A - first admin group of Exchange 2003 still appears in the best practice analyzer of ex2010regarding this i have found contradictory info:Researching on this the references that i found are:1. not recommending to delete it with adsiedit:http://www.eggheadcafe.com/software/aspnet/31590173/migratingcoexisting-firs.aspx"And please remember that you cannot delete any Exchange 2003 or Exchange2000 administrative groups that ever contained mailboxes."2. recommending to delete it with adsiedit:Remove Exchange 2003 Administrative Group http://forums.msexchange.org/m_1800481490/tm.htm"I'm wrapping up my Exchange 2003 to 2007 transisition and I saw this warning from Microsoft: "Do not delete any Exchange 2003 or Exchange 2000 administrative groups that ever contained mailboxes. The LegacyExchangeDN property on a mailbox from an Exchange 2003 or Exchange 2000 administrative group still references the Exchange 2003 or Exchange 2000 administrative group even after you move the mailbox to a server in the Exchange 2007 administrative group. Office Outlook 2003 and earlier versions use the LegacyExchangeDN property to get free/busy information. If the administrative group that the LegacyExchangeDN property references no longer exists, Outlook will not be able to find free/busy information. In addition, all versions of Outlook use the LegacyExchangeDN property when a user delegates access to folders by using the Outlook client. If you delete the legacy administrative group that the LegacyExchangeDN property references, Outlook will not be able to find the assigned delegated user." When I uninstall Exchange 2003, am I given some option to remove that 2003 administrative group or something? I'd like to reformat my current Exchange 2003 server after I've removed Exchange 2003 from it- will that cause problems/delete the 2003 administrative group?" "Admin groups are a domain setting, not a server setting. Therefore installing Exchange using add/remove programs should not cause a problem or the removal of the Admin Group. Exchange MVP ""Thanks Sembee. So I'd pretty much have to use ADSIEdit to remove that administrative group, correct? Or take a hammer to my domain controllers...""I think PowerShell can remove the Admin Groups, so a hack shouldn't be required. Simon. Exchange MVP"B- routing group connector referencing the connection between exch 2003 and 2010, which i have deleted with powershell..c- RUS role of the exchange 2003, that still is registered as it exits:more info found on this: even when exchange 2007 and i assume 2010 does not make use of RUS, it has to be properly uninstalled this role:- Why you need to Decommission Exchange 2003 Servers after your Exchange 2007 Upgradehttp://www.petri.co.il/decommission-exchange-2003-servers-exchange-2007-upgrade.htm"What is the Recipient Update Service?The real trick to removing Exchange Server 2003 from your organization is reassigning the Recipient Update Service. Setup will not allow you to uninstall Exchange Server 2003 until the Recipient Update Service has been reassigned to another server. This is ironic since Exchange Server 2007 doesn't even use the Recipient Update Service. Even so, this task must be performed."apparently RUS service is reponsible of the OAB in exchange 2003. -> Exchange 2003 has to be decommisioned even if exchange 2007 makes no use of it .Re-Homing The Recipient Update ServiceThe Recipient Update Service, or RUS to give it the acronym that it’s well known by, is an important component of Exchange 2000 and Exchange 2003 that can easily be missed during the server decommissioning process.Thanks for reading such a long question and help for your help in advance. Best Regards, David

Hi, I think this link will help you : http://support.microsoft.com/kb/833396/en-us http://www.msexchange.org/articles-tutorials/exchange-server-2007/migration-deployment/removing-last-exchange-2003-server-exchange-2007-part4.html http://support.microsoft.com/kb/924170