I have Windows 2003DomainA without Exchange 2003that all of my client computers are connected to. I have DomainB that is DC with Exchange 2003 and no client computers attached. DomainB server is old and I want to migrate Exchange data to new hardware with a fresh install of Exchange in Domain A. Both Domains are on the same subnet within my network. Would this still be considered a "Swing Migration" where I bring up the new server and replicate the system and public folders 1st? Then move the mailboxes to the new server within Domain A? My ultimate goal is to decommission Domain B entirely.This will allow me to effectively use Active Directory in Domain A to manage users and accounts. Currently, I have to change users passwords in two domains. Many Regards, Larry

Dear customer: According to your post, you have two domain, and Exchange server belongs to the old one, you want to migrate it to the new domain. For swing migration, the new Exchange server still joins the existing Exchange site. So this case is not available for you. Your case should belong to inter-organization migration. To migrate accounts and mailboxes from one Exchange 2000 or Exchange 2003 forest to a separate Exchange 2000 or Exchange 2003 forest, it is recommended that you first use the Active Directory Migration Tool (ADMT), followed by the Exchange Migration Wizard. First, run ADMT to create active user accounts in Active Directory. It is recommended that you select the option for migrating security identifiers (SIDs) so that ADMT adds the source account's SID to the new target account's SID history attribute. (Migration Wizard uses the SID to match mailboxes to accounts in the next step.) It is also recommended that you do not disable the user account in the source forest when you run ADMT. Exchange 2003 does not support disabled mailbox accounts without associated external account. After you migrate the accounts, use Migration Wizard to migrate mailboxes. If you migrated SIDs when you ran ADMT, Migration Wizard uses the SIDs to match mailboxes to the new accounts and converts the accounts to mailbox-enabled user accounts. If you did not migrate the SIDs in the first step, Migration Wizard cannot match a mailbox to an account; instead, the wizard creates a disabled user account to associate with the mailbox. For more information about Inter-Organizational Migration to Exchange Server 2003, please refer to Inter-Organizational Migration to Exchange Server 2003 portion in the following documents: Microsoft Exchange Server 2003 Deployment Guide http://www.microsoft.com/downloads/details.aspx?FamilyID=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en Hope it helps. If you have anything question, please feel free to let me know. Rock Wang - MSFT

Sir, Thank you for the detailed reply.This solution makes sense.I have been stressing on the best way to take care of this project and this really helps. Most of my users (warm body's) are configured in both domains but I have a few email boxes for various things that are only setup in the exchange domain (B). Setting these up manually won't be a problem nor will the distro list mailboxes and resources. My new hardware will be here in a few days and I plan on the migration in mid July. I'm holding off on Exchange 2007 for now due to Server 2008 and Exchange 2007 new licensing requirements and budgeting issues. Thanks again. LAL

Dear customer: I am so glad to know our help is useful to you. If you have any questions regarding our products in the future, please feel free to let us know. We are always glad to be of further assistance. Rock Wang - MSFT

Good Day....My exchange installation in my primary domain was successful. I started testing the ADMT user migration wizard and have encountered another issue I receive the following error: The specified domain either does not exist (old domain with the exchange I want to move from) or could not be contacted. I'm sure it has to do with permissions or trusts but I can't find anything on Technet to helo me troubleshoot the error. Thanks, LAL