Shulou(Shulou.com)06/02 Report--

Regular Exchange data migration can be divided into the following categories:

1. Migration between different databases within the organization: this can be done by creating mobile requests.

2. Migration between different organizations (cross-domain): it is relatively complex because the domain names are different, so the operation will be more complicated.

Today, we will focus on the mailbox data migration between the following different organizations. There are several migration schemes for reference:

Option 1: IMAP migration

This scheme is suitable for general small companies, when the amount of mailbox data is small, the online migration can be carried out directly.

Advantages: the source email address and the destination email address of the migration can be different. You only need to match the account in the csv file. You can achieve online migration to ensure that the mail business does not stop.

Disadvantages: the account password of each migrated user needs to be obtained, and the user cannot change the password during the migration, otherwise the migration is not successful; the Exchange public folder cannot be migrated; it cannot be migrated when a single message is larger than 35MB; and the relevant custom folders or rules cannot be migrated.

Summary: IMAP migration is only suitable for mailbox data migration and is suitable for small company migration

Option 2: PST migration

This scheme is operable and can migrate almost all mailbox data, custom folders, rules, etc., and is suitable for medium and large enterprises.

Advantages: all mailbox data can be migrated to the new Exchange environment one by one, which is stable and reliable. Through technical means, email data can be migrated between Exchange of different organizational domain names.

Disadvantages: strong operability, requiring professional technical personnel to operate; the mail business will be interrupted during the migration process, and the interruption time depends on the data size of the migration mailbox; unable to migrate Exchange public folders

Scenario 3: BitTitan MigrationWiz migration

BitTitan MigrationWiz (abbreviated as BT) is an efficient cloud-based automatic mail migration solution developed by Microsoft Cloud Services operator in China (Century Internet). BT can migrate all mail systems at will, whether Exchange or Notes or other Any IMAP mail systems. It is suitable for large companies such as mergers and acquisitions or restructuring, cloud on local mail servers and other application scenarios.

Advantages: online migration, can migrate all users' mailbox data, including rules, etc.; can migrate Exchange public folders; support migration between different domain names; easy to operate, directly achieve migration in Century interconnected Web; background 7X24 technical support

Plan 4: Exchange cross-forest migration, the implementation of this scheme is more complex, and there are many errors, I do not know how to describe it.

Today, I would like to share with you the following second plan!

User requirements: as a result of the company spin-off and merger, there will be a new company, to enable a new domain name, e-mail must have nothing to do with the current completely independent.

Solution: if you consider that the user name and password remain unchanged, use the ADMT tool to migrate the user's account and password, and then use the PST method to migrate the mail; if you create a new account, you just want to migrate the original user's mail to the new company, you can do it directly through PST.

To facilitate the demonstration, two simple mail systems are built to import, export and migrate the database. The specific information of the environment is as follows:

Exchange Server 2010:

Domain name: zuche.intra administrator: admin

AD server name: oldad

AD server IP address: 192.168.2.10

Exchange server name: oldex

Exchange server IP address: 192.168.2.11

New Exchange Server 2010:

Domain name: zuche.com administrator: administrator

AD server name: newad

AD server IP address: 192.168.1.10

Exchange server name: newex

Exchange server IP address: 192.168.1.11

We assume that the AD user already exists (regardless of whether or not the password is migrated to the new AD) to achieve cross-domain migration

First of all, you need to centralize the users on a certain OU, because when you do the receiving domain, you do it for a certain OU, and then you do the actual operation.

1. First, open the domain and trust relationship in the active Directory server, and right-click to add a UPN suffix of zuche.com, as shown below:

2. Change the login address of the user to user@zuche.com in the user and computer, as shown below:

3. Open Hub Transport on the Exchange Server management console, select the accepted domain, and then click New accepted Domain, as shown below:

4. Enter the name and domain name of the accepted domain, and select the authoritative domain, as shown below:

5. Create a new e-mail address policy, enter the e-mail address policy name, and the recipient container (select in OU in AD) as shown below:

Email address, select New, and then select zuche.com as the accepted domain in the pop-up dialog box, as shown below:

Select apply now to complete the email address policy creation, as shown in the following figure

In order to verify the configuration and create some mailbox data, log in to owa with any account and omit the process of sending and receiving email.

Inbox

calendar

Personal contact

The next step is to export the data on the source server

Open Exchange Powershell on the source server

Give the administrator import and export permissions:

New-ManagementRoleAssignment-Name "Import Export_Domain Admins"-User "Administrator"-Role "Mailbox Import Export"

Then close Exchange Powershell and reopen it, and run the following command to bulk export existing users

Get-mailbox-OrganizationalUnit "zuche.intra/ Xinhe Times"-resultsize unlimited |% {New-MailboxexportRequest-mailbox $_ .name-FilePath ("\\ localhost\ c$\ export\" + ($_ .name) + ".pst")-BadItemLimit 50}

Or export a user's mailbox separately

Such as: new-maliboxExportRequest-Mailbox wangyuan@zuche.com-filePath\\ localhost\ c$\ export\ wangyuan.pst

With the source data, the next step is to import the data into the new Exchage system

First, enable mailbox accounts for the same users in the new system (all users are stored in the newmailbox mailbox database)

Open exchange powershell and give the administrator import and export permissions:

New-ManagementRoleAssignment-Name "Import Export_Domain Admins"-User "Administrator"-Role "Mailbox Import Export"

Then import user mailboxes in bulk:

Get-childitem\\ localhost\ c$\ export\ * .pst | select name,basename |% {New-MailboximportRequest-mailbox $_ .basename-FilePath ("\\ localhost\ c$\ export\" + $_ .name)-BadItemLimit 50}

Then verify whether the user data is restored, open the owa login account to view the outbox, inbox, calendar, contacts can see that it is all restored!

At this time, people may think: isn't the domain name of the source mailbox the same as that of the new mailbox?

So next, you need to create another email policy in the new mail system to change all users' email addresses to new domain names (or you can directly use the new domain name when creating a new AD, and then add a UPN as the original domain name)

This migration method is stable, reliable and risk-free, and is suitable for one-size-fits-all migration. However, it is not very flexible. If a user wants to change the mailbox prefix, he can only change it after the data migration is completed, instead of having CSV files to correspond to the source mailbox address and the new mailbox address one by one as IMAP does. You can change it at will.

There are many migration solutions, and it is best to find the one that suits your project. After sharing ~ (this method is also applicable to Exchange 2013 and 2016)

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.