Mike, You have a typical situation here. I would think of doing the following, 1) Create a most recent full backup of your exchange IS and ship it to the new location. 2) Create CSVDE files of user object, groups DLs and ship it to the new location. 3) In the new location Install Exchange, import the CSVDE files to the AD. DO not mail enable any users yet, you have to make sure the CSVDE does not have email attributes. 4) Then restore the backup from the other location and redirect to the new server. Make sure you create a Mailbox store with the identical name as the other location for this to work. 5) Once the restore is done, run a clean up of the mailboxes, then use the MBConnect (Mailbox connect) utility to connect the existing user objects to the restored mailboxes. MBConnect should automatically link the mailbox to the corresponding user based on the alias name. 6) I have done this in a test environment. I suggest you play around with MDBconnect before implementing in production. 7) The reason I don't favor PST file method is, it is more time consuming, and it grows the size of your priv.ed as all single instance storage is lost. HTH Regards, Raj -----Original Message----- From: A. Michael Salim [mailto:msalim@xxxxxxxxxxxx] Sent: Thursday, March 24, 2005 11:06 AM To: [ExchangeList] Subject: [exchangelist] Exch2k3 migration to different AD, Forest http://www.MSExchange.org/ Hi, I am migrating an Exchange server with about 100 users from one Geographical location to another. There are about 100 mailboxes and over 100GB of mailbox space so migrating all content over the Internet is not feasible. Furthermore, the new and old Exchange servers are not related to each other in any way such as AD, GC, Forest, and no trust relationships. It is a pure Internet (TCP/IP and no NetBios etc) interconnection between old and new servers, not even a VPN. Here is the procedure I am following: a) On the old sever, use Exmerge to export the mailboxes to PST files and save to a USB drive Use CSVDE and LDIFDE to export the users and groups and save to same USB drive. b) Ship USB drive to new location. c) On new server, used LDIFDE and/or CSVDE to recreate users and groups. d) On new server, import all the PST files 9which by now are a few days old). My questions are: 1) Is this a "best practice" method for these circumstances or is there a better way to do this? 2) After all the users are created and mailboxes imported, how do I "synchronize" the two servers (old and new) so that the mailboxes on the new server are "up to date" before I switch over the DNS? Otherwise I will either have a gap of a few days in the mailboxes, or I will need to all Exchange services completely on the old server for 1-2 days while the USB drive is being exported, shipped, and imported? (the incoming email would be diverted to a store-and-forward secondary mailserver during this process, of course). Needless to say, stopping the Exchange server for any length of time is not feasible since these are busy users who rely heavily on their email. best regards Mike ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: raj.periyasamy@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx