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

precondition

A computer running a 32-bit version of Microsoft Windows on which you can install Exchange Management tools (SP1) for your entire organization.

Microsoft Outlook 2003 SP2 or later needs to be installed on the above workstations.

You need to be an Exchange organization administrator (if mailboxes span multiple servers) or Exchange Server Admin (if mailboxes are all on one server).

For all PST that you plan to import, you need to create a mailbox-enabled user with an associated user alias, which is usually a user login and needs to match the name of the PST file.

You need to have full permissions on the above mailboxes to be imported; however, this will be shown in step # 2.

1. Install Exchange 2007 SP1 management tools

Description of prerequisites for the installation of Exchange management tools

During the testing, I found that Windows 7 had met all the prerequisites. However, if you are using an older operating system, you may need to double-check that you do have the necessary settings mentioned in the prerequisites section.

Get the installation file-Exchange 2007 Administrative tools-Select E2K7SP1EN32.exe from the available options.

Run the Custom installation and select only administrative tools; we don't want to install any other roles on this workstation! After installation, make sure that you are running a summary of all the same updates that have been installed on your organization's Exchange server. If you use SP1, update rollup 9 must be installed on this computer, and administrative tools are installed.

You can find Exchange2007 SP1's summary update 9:Exchange 2007 SP1 update summary 9 here-Select Exchange2007-KB970162-x86- EN.msp from the list.

Description of account permissions

If you try to use an account that does not have the correct Exchange administrator role, you will need to log out of the management station and log back in again after fixing the problem by assigning the Exchange organization administrator or Exchange Server administrator.

two。 Add full access to the mailbox

The next step is to add FullAccess to all mailboxes you want to import. This is done using Add-MailboxPermission cmdlet. I won't go into detail about this cmdlet. It can be said that running the following command will grant the user account "shaun" FullAccess permission to all mailboxes on a specific Mailbox server.

Get-ExchangeServer | Get-Mailbox | Add-MailboxPermission-User Shaun-Acce***ights FullAccess-inheritancetype all

Remove-MailboxPermissions-User Shaun-Acce***ights FullAccess-inheritancetype all-confirm:$false

Of course, you can do this using GUI if you prefer:

Open the Exchange Management console

+ recipient configuration

+ mailbox, and then select the user

+ manage full access (on the actions pane)

+ use the wizard to add an account that grants full access

3. Use Import-Mailbox cmdlet

Now is the time for the Import-Mailbox command. The Import-Mailbox command has several parameters that we are particularly interested in. -

Identity

As the name implies, this is the location of the mailbox that you specify to use for the import routine target.

-PSTFolderPath

This will instruct the Import routine to view the path to the PST file that we are interested in. If you import only one PST file for a specific user, you can reference the exact PST file here, which will import the PST file. Note, however, that you did not specify an explicit PST file and pass multiple mailboxes to the command, otherwise it will import the same PST file for all users who may cause some embarrassing results!

-MaxThreads

The typical value is 4, which is usually more or less acceptable unless you have thousands of mailboxes, and then you may want to increase this value. Remember that you will eventually encounter hardware bottlenecks.

-ValidateOnly

Using this switch is similar to the whatif switch in other cmdlet (actually this is it). It does not move any data, but only emphasizes whether the process is likely to be successful and notifies you when you need to deal with any problems.

Therefore, once we have the PST file in the PSTFolderPath of our choice, please run the command according to your situation:

Import a single PST into a single mailbox:

Import-Mailbox-PSTFolderPath

Import a bunch of PST files into its associated mailbox:

Dir C:\ PSTFiles\ * .pst | Import-Mailbox

Browse all mailboxes, find the relevant PST and import:

Get-Mailbox | Import-Mailbox-PSTFolderPath

As you can see, this routine is in the preparation environment. The actual command that you execute the import is small and efficient. The advantage of using Powershell to accomplish this task is that it is extensible, and if you have a situation where you need to import a lot of PST, it will be very pleasant to get the job done.

Reference:

You were in EHLO...

How to export and import mailboxes into PST files in Exchange 2007 SP1

Http://msexchangeteam.com/archive/2007/04/13/437745.aspx

Import-Mailbox cmdlet Technet referenc

Http: / / technet.microsoft.com/en-us/library/bb629586.aspx

How to import mailbox data Technet reference

Http://technet.microsoft.com/en-us/library/bb691363.aspx

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.