DotNetPanel Manuals Center, Guides, "HOW TO" On-Line Library
Migration between different AD/Exchange environments Edit Page Page Info
Last edited Fri, 15 Jan 2010 17:36:05 GMT by Ilya Finkelstain, revision 14
 

General idea

The main idea is to move mailbox data from old AD/Exchange infrastructure to the new one using the steps below:

  • re-create user accounts and mailboxes on new server
  • export old mailbox data to pst files from old AD/Exchange infrastructure
  • import mailbox data to new AD/Exchange infrastructure

Every step could be done manually or using some automation utility. We do not provide automated solution for the entire process. While it is possible to "big-bang" solution in theory, it is better to do it carefully, half-manually, step-by-step, organization-by-organization, with checkpoints after every step.

Steps to move users within one organization

  • Inform users about time when they should not create new mailboxes and time when actual mailbox movement scheduled.
  • Create new organization in DNP based on appropriate Hosting Plan/Hosting Space.
  • Exchange-enable organization by creating and deleting test mailbox in it.
  • Add organization's domains to newly created Organization
  • Set organization's domains as Internal Relay Domains according to this http://technet.microsoft.com/en-us/library/bb124423.aspx article and create connector for messages to non-existing recipients in organization's domains to be forwarded to old Exchange system
  • Test that mail to non-existing recipients in organization's domains successfully forwarded to old Exchange system. For this send test mail to recipient whose mailbox is on old Exchange system to new Exchange system with telnet. Read this http://technet.microsoft.com/en-us/library/bb123686.aspx article about how to use telnet to test SMTP communication
  • After successfull test change DNS MX record for organization's domains to new Exchange system.
  • Create all mailboxes in DNP for that organization with the same e-mail address (addresses). Use simple standard password for all mailboxes. You can use Bulk Import Tool to automate this process.
  • Create all Organization's Public Folders.
  • Additionally inform users about time when actual mailbox movement scheduled and ask them not to use mailboxes at that time.
  • Reset password for every organization's user on old system to prevent them from connecting there anymore.
  • Connect to every organization's mailbox with Outlook and export it to pst file. This step can be automated with exmerge tool for Exchange 2000/2003 (http://msexchangeteam.com/archive/2004/07/01/171051.aspx) or export-mailbox (http://msexchangeteam.com/archive/2007/04/13/437745.aspx) tool for Exchange 2007.
  • Use one of mailboxes to connect to organization's Public Folders and export them to pst files too.
  • Make note what language is used in what mailbox. It can be done in pst file name. For example user_customer_en.pst
  • Set Autodiscover/OWA redirect DNS records in organization's domains to make Outlook/OWA connection easier.
  • Connect to every mailbox with OWA with appropriate default Internet Explorer language. This will create correct default folders in correct language.
  • Connect to every organization's mailbox with Outlook. Use Outlook to import pst files to mailboxes. Also you can use import-mailbox command let for that task (http://msexchangeteam.com/archive/2007/04/13/437745.aspx).
  • Import Public Folders using Outlook.
  • Copy legacyExchangeDN attribute from old AD to newly create X500 address for every user. You can use csvde utility to retrieve legacyExchangeDN attributes. This is needed to replies to old internal mails works. Additional information could be found here http://support.microsoft.com/kb/555197/en-us.
  • Disable users in old AD.
  • Change organization's domains type back to default Accepted Domains.
  • Instruct users how to connect to new server and how to change passwords.

Alternative way. Note that it was not tested in DNP lab.

Tags (0)
No tags have been added yet.
Comments (0)
No comments have been added yet.
Attachments (0)
No page attachments found.