Hello,We have a Windows 2003 domain with Exchange 2003 in a backend-frontend topolgy. For example say our domain name is rd.com. We recently bought some other companies with doamin name like rs.com and rq.com all running Windows domain controllers with Exchange 2003. We like to decommision rs.com and rq.com and bring everything under one umberlla rd.com. We definitely like to get mail data either migrated or moved from rs.com and rq.com to rd.com domain. We prefer to do this as a parallel install with Windows 2008 DC's and Exchange 2007 install base. 1. Is it possible to move mailboxes from a doamin to a different doamin name? For example, from rq.com to rd.com.2. Is there a preferred way to approach this?I will apprecaite any valuable response from the community.thanks in advance

The best way will be Inter Org migration from the old domains (acquired companies) to your original organization. The Basic requirement will be a trust between the two AD forest. http://exchangeis.com/blogs/exchangeis/archive/2006/07/30/ad-and-exchange-interorg-migration-a-real-world-example-part-1.aspxhttp://msexchangeteam.com/archive/2006/11/02/430289.aspxRaj

Hello,I forgot to mention one important piece in my prior email. Currently our domain name is rd.com. We like to change it to rnd.com. As mentioned earlier we have Exchange 2003 in a frontend backend topology. How will it affect Exchange and other application servers?Is there a way to do a parallel built, meaning have another PDC with rnd.com in a seprate forest, have a cross forest trust and move AD database from rd.com to rnd.com? In this way we have very minimal production impact. I am not sure whether it's possible, but I am just throwing it our there to get your suggestions.What are the ways or way if an organization, say with Exchange, SQL and 50 some members servers joined to an AD domain decide to change their domain name? Does all desktops/ laptops have an easy way of rejoining doamin without indivudually disjoin and join new domain.Thanks in advance

Once you decide to change the SMTP domain, the Major changes are on DNS with a new A and MX record. MX pointing to a FW or any Anti spam device.Moving AD database (ntds.dit) is not possible. The better way will be forest consolidation. So you need to bring in a new forest , trust betwwen them and move the user with ADMT or using Quest tools.Download this document http://download.microsoft.com/downlo...atingSBS2k.doc . THis is a SBS document but will still help you.Also see this blog http://forums.techarena.in/active-directory/1135548.htm.Regarding SQL , I am not sure. But exchange , the only way is a proper inter org migration and for desktop also, you need to disjoin them from there old domain and then connect them back to the old domain. This will update the small things like DHCP, AD objects (laptops and desktops) , DNS etc.Raj

Hi,If you rename the Domain Controller and Exchange in place, please refer to the below article:http://msexchangeteam.com/archive/2004/08/30/222719.aspxIf you plan to deploy the new Exchange server to replace the current one in different forest, you should set up the trust between the Exchange servers, then use MIIS to sync the GAL.ThanksAllen