Microsoft KB Archive/278736

= XADM: Alternatives to Using MOVE MAILBOX in the Administrator program =

Article ID: 278736

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Exchange Server 4.0 Standard Edition
 * Microsoft Exchange Server 5.0 Standard Edition
 * Microsoft Exchange Server 5.0 Service Pack 1
 * Microsoft Exchange Server 5.0 Service Pack 2
 * Microsoft Exchange Server 5.5 Standard Edition
 * Microsoft Exchange Server 5.5 Service Pack 1
 * Microsoft Exchange Server 5.5 Service Pack 2
 * Microsoft Exchange Server 5.5 Service Pack 3
 * Microsoft Exchange Server 5.5 Service Pack 4

-



This article was previously published under Q278736



SUMMARY
The article describes two methods that you can use to work around the move mailbox command in the Microsoft Exchange Server Administrator Program.



MORE INFORMATION
WARNING: Before you begin either of the methods described in this section, make sure that you have a verified backup in place. Also, it is recommended that you test the methods first with a test mailbox.

Method One: Using Header.exe
This workaround is useful if you have only a few users.

NOTE: Header.exe is a BackOffice Resource Kit tool. Refer to the Resource Kit Support Policy in the last section of this article for more information about support limitations. It is recommended that you read the documentation to this tool.  Start Microsoft Outlook, and then move of the contents of the mailbox to .pst files. Export the mailbox's rules:  Click Inbox, and then click Rules Wizard on the Tools menu. Click Options, and then click Export Rules. Type the path and a file name where you want to save the set of rules, and then click Save.  Export the folder properties for this mailbox:  Start Header.exe that is located in the BackOffice Resource Kit.</li> Mark all available attributes.</li> Click Add, click File, and then type the path and the file name.</li> Click Open, and then click Generate.</li> Start the Administrator program.</li> On the Tools menu, click Directory Export.</li> Click the home server of the mailboxes that you want to export.</li> Click Export file, type the name and path of the file that you have just created by using Header.exe, and then click Open.</li> Click the Recipients container, and then click OK.</li> In the Export objects section, click to select the Mailboxes check box, and then click Export.</li> Open the export file using Microsoft Excel or Microsoft Notepad, and then delete all the entries for mailboxes that you do not want to move.</li> Change the home server, home-MDB and home-MTA to the appropriate server, and then save the file.</li></ol> </li> Delete the appropriate mailbox on the source server after you verify that you have successfully completed the preceding steps.</li> Import the mailbox properties on the new home server: <ol style="list-style-type: lower-alpha;"> <li>Go to the Administrator program, and then click Directory Import on the Tools menu.</li> <li>Enter the domain of the source server, and then as the Exchange Server computer, enter the source server.</li> <li>Click Import File, type the name and the path of the file that you modified in Notepad or Excel, and then click Import.</li></ol> </li> <li>Use Outlook to import the data of the .pst file.</li> <li>Use the Rules Wizard in Outlook to import the rules.</li></ol>

Method Two: Using Exmerge.exe and Header.exe
This method is useful if you are moving a large number of users (over 50).

NOTE: Exmerge.exe is a BackOffice Resource Kit tool. Refer to the Resource Kit Support Policy in the next section for more information about support limitations. It is recommended that you read the documentation to this tool. <ol> <li>Log on using an Exchange service account.</li> <li>Export the properties of the mailbox (to do so, refer step three in the preceding method).</li> <li>Start Exmerge.exe on the source server, and then click Two steps method.</li> <li>Click the source server and the mailboxes that you want to move, and then click Next.</li> <li>Click a folder, and then use the default settings.</li> <li>Delete the mailbox on the source server.</li> <li>Import the properties of the mailbox on the target server (to do so, refer to step five in the preceding method).</li> <li>Send mail to each of the new mailboxes to activate them. After you activate the mailboxes, the mailboxes are displayed in the Exmerge window (the second step of Exmerge.exe).

NOTE: If you want to use localized names for the Outlook folders (for example Inbox), modify the Exmerge.ini file. The following example describes German translations:

[EXMERGE]

MapFolderNameToLocalisedName = 1

[Folder Name Mappings]

Inbox = Posteingang

Delete Items = Geloschte Objekte

Sent Items = Gesendete Objekte

Outbox = Postausgang

For more information, refer to Exmerge.doc.</li> <li>Mark the mailboxes, and then type the name of the folder where you saved the Exmerge files ( .pst).</li></ol>

Microsoft BackOffice Resource Kit Support Policy
The software supplied on the Microsoft BackOffice 4.5 Resource Kit CD-ROM is not officially supported. Microsoft does not guarantee the performance of the Microsoft BackOffice 4.5 Resource Kit tools, response times for answering questions, or bug fixes to the tools. However, we do provide a way for customers who purchase Microsoft BackOffice 4.5 Resource Kit to report bugs and receive possible fixes for their issues by sending e-mail to rkinput@microsoft.com. This e-mail address is only for Microsoft BackOffice 4.5 Resource Kit-related issues.

The software (including instructions for its use and all printed and online documentation) is provided &quot;AS IS&quot; without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the software and documentation remains with you.

In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the software be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the software or documentation, even if Microsoft has been advised of the possibility of such damages.

Keywords: kbfaq kbinfo kbpending KB278736

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.