For sample commands, see "Sample Command for Moves Across Exchange Organizations" and "Sample Command for Moves Across Administrative Groups" later in this topic... Sample Command for Mo
Trang 1Using the Exchange Profile Update Tool
Run Exprofre.exe after you move mailboxes from one Exchange
organization to another or from one administrative group to another You can use a logon script or group policy to run the tool for Outlook users
Note:
It is recommended that you use a logon script to run Exprofre.exe so that users' Outlook profiles are updated when they first log on after the mailbox move For sample commands, see "Sample Command for
Moves Across Exchange Organizations" and "Sample Command for
Moves Across Administrative Groups" later in this topic
Table 7 describes the options that are available whether you run
exprofre.exe from a command prompt or from within a script, such as from the following script example:
exprofre.exe [/?] [/targetgc=<global catalog server>] [/logfile=<path\filename>] [/v] [/f] [/a] [/r] [/o] [/p=<RPC over HTTP Proxy server>] [/n] [/s] [/q]
Trang 2/? Displays Help
server (required)
the log file The default is
exprofre.log in the tmp directory,
which is saved on the client computer You can also redirect the log file to a server share by using the format
/logfile=<path\filename>
Trang 3Command option Description
.xml) If this option is not specified, the tool renames the extension of the favorites file to exprofre
(.oab) files If this option is not specified, the tool deletes the oab files and resets Outlook to check the server for an updated set of .oab files
Trang 4/o Deletes rather than renames the
offline folder store file (.ost) If this option is not specified, the tool renames the extension of the ost file to exprofre (This option is not required for Outlook 2003 or later The ost file for Outlook 2003 or later is always unchanged.)
if you are using Outlook 2003 with RPC/HTTP turned on
(.nk2 or nick) If this option is not specified, the tool keeps the nickname file
Trang 5Command option Description
in server name rather than a change in the legacyExchangeDN attribute
Sample Command for Moves Across Exchange Organizations
If you are moving mailboxes across Exchange organizations (cross-forest
moves), it is recommended that you use only the /v and /n command
options All other options should be omitted to enable the tool to use its default settings Because the user is moving to a new forest, most of the Outlook information stored on the user's workstation will be obsolete and must be updated with information about the new forest By default, the tool deletes most of this obsolete information
The following is a sample command for a mailbox move across Exchange organizations:
Trang 6Migration Wizard Installation Log
After your Exchange migration is complete, review your installation log located on your Exchange computer (for more information, see Batch File and Command Line Migrations for Exchange Server 2003) The Migration Wizard log contains information about your migration and is used to
provide status about your Exchange migrations
In the event of a migration failure, you can use the log to determine which mailboxes moved successfully and which mailboxes failed to move Also, after a migration, you can view the status of accounts that were
successfully migrated, partially migrated, or that were updated in Active Directory without the content being moved
Note:
After you perform the migration, The Migration Wizard log provides
information that helps you take action on only mailboxes that failed to migrate
Trang 7Information that is Logged
The following information is logged during your Exchange migration:
The list of accounts and mailboxes that will be moved
An event is logged each time an account is updated in Active
Directory
An event is logged when an account migration begins
An event is logged when an account migration succeeds or fails
Note:
For MAPI-based migrations from Exchange 5.5 or Exchange 2000 to
Exchange 2003, logging is available only in the SP1 version of
Migration Wizard
Information that is not Logged
The following information is not logged during your Exchange migrations:
Trang 8 Migrations from non-Exchange sources
Sample Log File
The following is an example of a Migration Wizard log file
******************************************************
Microsoft Exchange Migration Wizard, v(version number)
Start Logging: [Time]
******************************************************
[Time] Mailboxes to be migrated from server <name
server>
Ted Bremer
Kim Akers
Trang 9Birgit Seidl
Pilar Ackerman
[Linefeed]
[Time] Updating Active Directory
[Time] Updated mailbox information for Ted Bremer in Active Directory on {DCNAME}
[Time] Failed to update mailbox information for Kim Akers in Active Directory on {DCNAME} Mailbox will not be migrated
[Time] Found existing mailbox information for Birgit Seidl in Active Directory on {DCNAME} for Birgit
Seidl, no update needed
Trang 10
[Linefeed]
[Time] Migrating Mailboxes
[Time] Started migrating mailbox Ted Bremer to server
<name server>
[Time] Completed migrating mailbox for Ted Bremer
[Time] Started migrating mailbox Birgit Seidl to
server <name server>
[Time] Completed migrating mailbox for Birgit Seidl
[Time] Started migrating mailbox for Pilar Ackerman to server <name server>