Exchange Migrator

Version 2.2 Service Pack 1

Release Notes

Revised: September 24, 2002

 

Why Install This service pack?

Installation Notes

Additions to Documentation

General Notes

Distribution List Notes

Mailbox Notes

Public Folder Notes

Reporting Notes

Undo Notes

Legal Notice

 

 

Microsoft Exchange 2000 Server provides one of the most compelling reasons to upgrade to Windows 2000. This powerful environment promises many capabilities to bring your organization closer together and work more effectively. To reduce the impact on users throughout your organization, you need to carefully plan and implement your migration to Exchange 2000.

NetIQ Corporation provides several products to help you plan for and migrate to Windows 2000 and Exchange 2000. For example, Domain Migration Administrator and Server Consolidator help you consolidate and migrate your Windows NT user accounts, groups, and organization to Windows 2000. The NetIQ Exchange Migrator product (Exchange Migrator) can work in conjunction with Domain Migration Administrator by migrating your Exchange 5.5 organization to Exchange 2000. Exchange Migrator can also help you restructure your Exchange 5.5 sites before you migrate to Exchange 2000.

Exchange Migrator lets you move Exchange objects such as mailboxes, distribution lists, custom recipients, and public folders from one Exchange organization or site to another. Exchange Migrator retains calendar and public folder permissions and reconciles distribution list memberships as part of the migration. Based on the award-winning Domain Migration Administrator technology, Exchange Migrator minimizes user downtime while reducing the load on administrative and help desk staff.

This document outlines why you should install this version of the product, provides additions to the documentation, and identifies any known issues. For more information about requirements for installing Exchange Migrator, see the User Guide for Exchange Migrator.

Why Install This Service Pack?

This service pack provides performance enhancements and new features. The following section describes compelling reasons for installing this service pack.

Supports Migration from an Exchange 5.5 Server to an Exchange 2000 Server in the Same Site within the Same Organization

Exchange Migrator allows you to migrate mailboxes from an Exchange 5.5 server to an Exchange 2000 server in the same site within the same organization. For more information, see Additions to Documentation in this file.

Enables Outlook to Display Contacts Folder in the Address Book for Migrated Mailboxes

The default Contacts folder is displayed in the Outlook Address Book in the following target email clients after using the EMProfile Update utility:

  • Microsoft Outlook 97
  • Microsoft Outlook 98
  • Microsoft Outlook 2000

EMProfile Update Handles Offline Folder Files

The EMProfile Update utility can handle offline folder files for migrated mailboxes. If you are using a Microsoft Outlook 2000 client, the EMProfile Update utility can create a target offline folder file. If you are using a Microsoft Outlook 97 or Outlook 98 client, the EMProfile Update utility disconnect the source offline folder file from the updated mailbox profile. Outlook 97 and Outlook 98 users need to manually create an offline folder file for the updated mailbox profile.

Return to Top

EMProfile Update Supports Additional Operating Systems and Outlook Versions

The EMProfile Update utility correctly updates mailbox profiles for users running the following email clients and operating systems:

  • Microsoft Outlook 97 running on Microsoft Windows 98
  • Microsoft Outlook 97 running on Microsoft Windows NT 4.x SP 6a
  • Microsoft Outlook 98 running on Microsoft Windows 98
  • Microsoft Outlook 98 running on Microsoft Windows NT 4.x SP 6a
  • Microsoft Outlook 2000 running on Microsoft Windows 98SE
  • Microsoft Outlook 2000 running on Microsoft Windows NT 4.x SP 6a
  • Microsoft Outlook 2000 running on Microsoft Windows 2000
  • Microsoft Outlook XP running on Microsoft Windows ME
  • Microsoft Outlook XP running on Microsoft Windows XP

Synchronizes Reorganized Target Public Folders

If you reorganize synchronized public folders without renaming them, Exchange Migrator can synchronize the reorganized public folders. For more information, see the Additions to Documentation section in this file.

Synchronizes Migrated Public Folder Client Permissions

Exchange Migrator allows you to merge source and target public folder client permissions. Previous versions of Exchange Migrator overwrote target public folder client permissions during migration and subsequent synchronizations. This service pack modifies permissions handling so that only initial public folder migrations overwrite target client permissions. Subsequent synchronizations on the migrated public folders merge source and target public folder client permissions. For more information, see the Additions to Documentation section in this file.

Merges into Existing Target Mailboxes

Exchange Migrator merges source and target mailboxes that share the same SAM account name, SID History, or SMTP address. Previous versions of Exchange Migrator only merged into mail-enabled Exchange 2000 target mailboxes. This service pack adds the capability to merge source mailboxes into Windows 2000 mailbox-enabled target user accounts and into existing target Exchange 5.5 mailboxes. For more information, see Additions to Documentation in this file.

Return to Top

Retains Target Mailbox Properties

Exchange Migrator allows you to specify if you want to retain non-blank target mailbox properties when you merge source and target mailboxes. Retaining target mailbox properties does not apply to email addresses. Exchange Migrator always overwrites target mailbox email addresses with source mailbox email addresses when you merge source and target mailboxes. Specify to retain non-blank mailbox properties when you specify your migration options. For more information, see the product Help.

Performs Migration Tasks from Multiple Exchange Migrator Consoles

Exchange Migrator allows you to peform migration tasks for a project from multiple Exchange Migrator installations that access the same migration database. Ensure all Exchange Migrator installations are running Exchange Migrator 2.2 Service Pack 1 or later. For more information, see Additions to Documentation in this file.

Can Migrate Mailboxes and Public Folders without Messages

Exchange Migrator allows you to migrate mailboxes and public folders without messages. By default, Exchange Migrator migrates source object properties and message data to the target Exchange server. You can specify to migrate mailboxes and public folders without message data when you specify your migration options in the Specify Migration Options wizard. For more information, see the product Help.

Return to Top

Additions to Documentation

This document provides additional information about the following new features:

Viewing Documentation Files

When viewing the documentation files in the installation kit, you may observe the following issues:

  • The installation kit provides some documentation in Microsoft Word DOC files. To view these documentation files, you need Microsoft Word or Microsoft Word Viewer installed. Other programs, such as Microsoft Wordpad, may not correctly translate the file format. You can download Microsoft Word Viewer from the Microsoft Web site (www.microsoft.com).
  • When you view the documentation files through the setup program, the snap-in for Internet Explorer may display some hidden text, such as index entry tagging, in the files. To hide this hidden text:
    1. On the Tools menu, click Options.
    2. Clear the All and Hidden Text check boxes, and then click OK.

Migration from an Exchange 5.5 Server to an Exchange 2000 Server in the Same Site within the Same Organization

Exchange Migrator allows you to migrate mailboxes from an Exchange 5.5 server to an Exchange 2000 server in the same site within the same organization. For more information, see “Identify Your Migration Scenario” in the User Guide. Consider the following information when migrating objects using this scenario:

Preparing Your Exchange Environment
Use Exchange Migrator along with the Microsoft Active Directory Connector (ADC) to migrate objects using this scenario. Exchange Migrator does not migrate distribution lists, custom recipients, or public folders in this scenario. When you migrate source mailboxes that are associated with target user accounts in this scenario, Exchange Migrator moves the source mailboxes to the target Exchange server. Since Exchange Migrator is moving mailboxes for this scenario, distribution list memberships and permissions granted within the Exchange organization do not need to be updated. For more information about migration options, see “Scenario 5 Migration Options” in this file. You cannot undo mailbox migrations completed using this scenario. The following variations are supported by Exchange Migrator for this scenario:

  • User Accounts Outside the Target Domain
  • User Accounts in Target Domain without SID History with Mailbox Rights
  • User Accounts in Target Domain with SID History and without Mailbox Rights

Verify that your Exchange organization is configured into a supported scenario, and then setup the appropriate ADC recipient connection agreements.

Warning
Exchange Migrator takes a mailbox offline to move it to the target Exchange server. If a mail client is open when Exchange Migrator takes the mailbox offline, the client could freeze and lose unsaved messages. To avoid a loss of unsaved information, you may want to migrate mailboxes when users are less likely to be logged into the source mailbox.

User Accounts Outside the Target Domain
The source and target Exchange servers in this scenario variation are in different Windows domains. The source Exchange server can be in either a Windows NT domain or a Windows 2000 domain. The target Exchange server is in a Windows 2000 domain. Exchange Migrator allows you to migrate source mailboxes to the target Exchange server while users continue to log into a source domain user account.

Before you begin your migration, configure a one-way ADC recipient connection agreement from the source Exchange 5.5 site to the target Windows 2000 domain. The connection agreement creates user accounts in the target domain. A target domain user account is necessary since an Exchange 2000 mailbox exists as part of a Windows 2000 user account. You can specify to create either enabled or disabled target user accounts. Users can continue to log into the source domain user account.

User Accounts in Target Domain without SID History and with Mailbox Rights
The source and target Exchange servers in this scenario may be in the same Windows domain and the source mailboxes are already associated with a target domain user account. Before you migrate mailboxes, users can log into target domain user accounts that access mailboxes on the source Exchange server. Exchange Migrator allows you to migrate source mailboxes to the target Exchange server.

Your Exchange environment may be supported for this variation if you migrate user accounts before using Exchange Migrator using any of the following methods:

  • You use a domain migration tool, such as Domain Migration Administrator to migrate the user accounts and you do not maintain SID History. After you migrate the accounts, you choose to update mailbox access rights.
  • You upgrade a Windows NT domain in place.
  • You manually create target user accounts and associate the accounts with a source mailbox.

Before you begin your migration, create a one-way ADC recipient connection agreement from the source Exchange 5.5 server to the target Windows 2000 domain to establish an association between the source mailboxes and target accounts. ADC detects the primary Windows NT user account in the target domain and merges the source and target user account information.

User Accounts in Target Domain with SID History and without Mailbox Rights
Your Exchange environment may be supported for this variation if you migrated user accounts with SID History using a domain migration tool, such as Domain Migration Administrator but you did not update mailbox access rights. When you are ready to migrate your mailboxes, Exchange Migrator can use SID History to migrate the source mailboxes into the associated target domain user accounts. After you complete your migration, you should update the target mailbox access rights. Updating the mailbox access rights ensures users can continue to access the migrated mailbox after you remove the source SID from the target user account. You can manually update mailbox security or you can use a domain migration tool, such as Domain Migration Administrator to update target mailbox access rights.

Before you begin your migration, create a one-way ADC recipient connection agreement from the source Exchange 5.5 server to the target Windows 2000 domain to establish an association between the source mailboxes and target accounts.

Migration Checklist
Consider the following checklist when planning your migration:

  1. Identify your migration goals and desired resulting organization structure. Get input from the appropriate people in your organization.
  2. Assess your source and target Exchange organizations. For more information, see “Assessing Your Exchange Environment” in the User Guide.
  3. Backup the servers in your source Exchange organization that contain objects you are migrating.
  4. Setup your environment with the correct permissions and trusts, so that you are able to migrate objects. For more information, see “Set Up Your Environment for a Smooth Migration” in the User Guide.
  5. Setup required services, connectors, and connections to ensure you can maintain mail flow. For more information, see “Preparing Your Exchange Environment for Scenario 5” in this file.
  6. Turn off anti-virus software on the source and target Exchange servers. For more information, see “Anti-Virus Software” in the User Guide.
  7. Install Exchange Migrator. For more information, see “Installing Exchange Migrator” in the User Guide.
  8. Start Exchange Migrator. For more information, see “Starting Exchange Migrator” in the User Guide.
  9. Become familiar with Exchange Migrator by defining a project and migrating a few objects in your lab. Match your test environment to your production environment so that your test migration results accurately identify possible migration issues. Verify the results of your migration to ensure you understand the various options.
  10. Create projects for your migration. For more information, see “Creating a Project” in the User Guide.
  11. Select objects for your migration projects. For more information, see “Selecting Mail Objects Using the GAL” and “Selecting Mail Objects From a File” in the User Guide.
  12. Specify migration options and scripts for each project. For more information, see “Specifying Migration Options” and “Customizing Migration with Scripting” in the User Guide.
  13. Migrate mailboxes. For more information, see “Mailboxes” in the User Guide.
  14. Translate mailbox security. For more information, see “Preparing Your Exchange Environment for Scenario 5” in the User Guide.
  15. Perform post-migration reporting and assessment of your environment to ensure the migration was completed successfully.
  16. Perform post-migration clean up activities, decommission old environments, and remove older hardware that is no longer needed.
  17. Implement management and monitoring tools to ensure a secure and reliable Windows 2000 and Active Directory infrastructure. For more information about NetIQ products, contact your NetIQ sales representative.
Return to Top

Performs Migration Tasks from Multiple Exchange Migrator Consoles

Exchange Migrator allows you to migrate objects that use the same migration database from multiple Exchange Migrator installations. Ensure all Exchange Migrator installations are running Exchange Migrator 2.2 Service Pack 1 or later. You can migrate objects on one installation at a time.

To migrate objects in a project from multiple consoles:

  1. Create an Exchange Migrator project
  2. Install Exchange Migrator on the remote computers.
  3. Run the DBManager.exe utility.
  4. Specify the database that contains the project you want to use.

Synchronizes Reorganized Public Folders

If you reorganize synchronized public folders without renaming them, Exchange Migrator can synchronize the reorganized public folders.

To continue to synchronize reorganized target public folders:

  1. Use Exchange Migrator to migrate the public folders you want to synchronize.
  2. Reorganize the public folders using a tool, such as Microsoft Outlook.
  3. Update the public folder location in the Exchange Migrator SQL or MSDE database. You may want to list the updated target public folder paths and then use a script to update the public folder location in the Exchange Migrator database. By default the Exchange Migrator database is stored in the NetIQ\Exchange Migrator folder on the computer where Exchange Migrator is installed. Public folder paths are specified in the TargetContainer field in the MigrationInfo table.

Return to Top

Synchronizes Migrated Public Folder Client Permissions

Exchange Migrator allows you to merge source and target public folder client permissions. Previous versions of Exchange Migrator overwrote target public folder client permissions during migration and subsequent synchronizations. This service pack modifies permissions handling so that only initial public folder migrations overwrite target client permissions. Subsequent synchronizations on the migrated public folders merge source and target public folder client permissions.

Before you synchronize migrated public folders, ensure that either the source mailbox or the public folder Default role has Folder Visible client permissions. You can view and change public folder properties in Microsoft Outlook. The target mailbox in the Exchange Migrator project owns public folders created as part of the migration. Ensure you have the following client permissions on the target mailbox in the Exchange Migrator project:

  • Create top-level public folder
  • View complete folder path
  • Create subfolders on existing trees where Exchange Migrator will create public folders

Exchange Migrator modifies target public folder client permissions as long as the public folder corresponds to a migrated mailbox. When individual source and target public folder client permissions entries conflict, Exchange Migrator sets client permissions on the target public folders to be equal to the client permissions of the source public folders. For example, if a client permission entry on a source public folder also exists in the target public folder, the client permissions on the target public folder are set equal to the client permissions in the source public folder.

Merges into Mailbox-Enabled Windows 2000 User Accounts and Target Exchange 5.5 Mailboxes

Exchange Migrator merges source mailboxes into existing target mailboxes. However, the mailbox owner property is handled differently when merging to an Exchange 2000 mailbox versus merging to an Exchange 5.5 mailbox.

When merging to an Exchange 5.5 mailbox, the source Windows NT account retains access permissions on the merged target mailbox. When merging to an Exchange 2000 mailbox, the source Windows NT account does not retain access permissions on the merged target mailbox. Users can access the target mailbox by logging into the target domain using the Windows 2000 user account. Since Windows 2000 and Exchange 2000 use the same database as part of the Active Directory, the target Windows 2000 user account includes access permissions to the target mailbox.

Return to Top

Installation Notes

Installing this release, installs Exchange Migrator 2.2 Service Pack 1. Ensure you have Exchange Migrator on your computer, before you install this release . Verify you meet all requirements before installing this release. For more information about requirements, see the User Guide for Exchange Migrator.

If you have Exchange Migrator 2.2 or later installed on your computer, you can upgrade to this release. If you want to maintain your existing Exchange Migrator projects, do not remove Exchange Migrator from your computer. Keep the SQL or MSDE database and existing database name when you install this release. Make a backup copy of existing projects before installing this release. Install this release on the computer where Exchange Migrator is installed.

The following installation issues are currently being researched. If you need further assistance with any issue, please contact Technical Support:

Issues When Installing MSDE

Ensure that you are aware of the following Microsoft Data Engine (MSDE) issues:

  • MSDE cannot be installed through a Terminal Server session. You must be logged in at the Terminal Server computer to successfully install MSDE.
  • If you have enabled a strong password strength policy, the setup program for MSDE may fail. The default user id for MSDE is sa and the password is blank. Microsoft provides a fix for this specific error. You can locate the fix at the Microsoft Support Web site. For more information, see Microsoft Support Article Q276419.

Uninstall Displays Error if Removing Program Database While SQL Enterprise Manager Has Open Table

Exchange Migrator uninstall displays an error if SQL Enterprise Manager has an open table in the Exchange Migrator database during the uninstall and you choose to delete the Exchange Migrator database.

Return to Top

General Notes

At NetIQ we strive to ensure our products provide quality solutions for your Windows NT and Windows 2000 needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support at the following address:

www.netiq.com/support

At NetIQ we strive to make products compatible with the hardware and software configurations in Windows NT and Windows 2000 environments. The following sections identify the currently known issues:

Uninstall Deletes Database from Remote Console

If you specify to delete the migration database when you uninstall Exchange Migrator, the uninstall program uninstalls the database even if the database is stored on a remote console. Backup your database before uninstalling any instance of Exchange Migrator.

Verify Correct Location for Password File

Verify that you accurately enter the path to the password.txt file or use the Browse button to locate the proper folder. Exchange Migrator does not verify that the path is correct or display a warning, and does not create a password file if the path is incorrect. The path entered in the text box must end with the name of the password file. Exchange Migrator interprets a path ending with a delimiting character, such as \, as an invalid path.

Choose Secured Location for Password File

To enhance security for the password.txt that Exchange Migrator creates, direct Exchange Migrator to write this file to a folder with appropriate security settings.

Return to Top

Use Quotes To Specify a Target Container That Has Special Characters in the Name

You must use quotes to specify a target container on a site or organization that has special characters in the site or organization name.

For example, To migrate objects to the Recipients container on the site ? SITE, INC. on the Exchange organization ? ORG, INC. enter the distinguished name into the Specify Migration Options wizard with quotes around the sections that contain special characters: 

CN=Recipients,OU="? SITE, INC.",O="? ORG, INC."

Delay in New Project Wizard If Source or Target is Unavailable

There may be a delay before Exchange Migrator displays an error message in the Create a Migration Project wizard when you select a source or target Exchange server that is unavailable.

Return to Top

Target Organizational Unit (OU) Path

If you migrate objects to an organizational unit (OU) on the target Exchange server, the LDAP path for the specified OU must be 255 characters or less.

Target Organizational Unit (OU) Domain

If you migrate objects to an organizational unit (OU) on the target Exchange server, Exchange Migrator does not verify that the specified OU is in the target domain. Verify that the desired target OU is in the target domain before specifying a target OU.

Return to Top

Email Format Strings Generated With Exchange 5.5 Field Names

If you choose to customize email address formats, default formats are displayed using Exchange 5.5 field names. Field names must be correct in the email address format to work on the target Exchange server. For more information about customizing email addresses and Exchange field names, see the Exchange Migrator Help.

Exchange Migrator Creates an Email Address for Migrated Objects on the Target When You Choose to Create a Custom Recipient on the Source

Exchange Migrator creates an email address with a random string for migrated objects on the target Exchange server when you choose to create a custom recipient for those migrated objects on the source Exchange server and do not use a translated email address for the Reply-To address.

Checking the Option to Create a New Windows NT Account Always Creates a New Account

Checking the option to create a new Windows NT account on the target Exchange server for migrated mailboxes always creates a new Windows NT account. If you successfully migrate a mailbox and then remigrate that mailbox, two Windows NT accounts are created.

Return to Top

Using Exchange Migrator with Imported Domain Migration Administrator Mappings

When you migrate user accounts using Domain Migration Administrator with the SID History feature, and import the file into Exchange Migrator, the migrated mailboxes are associated with the user accounts Domain Migration Administrator created. If you later remove the SID History using Domain Migration Administrator, permissions on the target mailbox may not be set correctly for the new user account to access the mailbox. We are currently researching this issue. To ensure user account permissions enable mailbox access after migration, do not remove the SID History from these migrated accounts using Domain Migration Administrator.

Mappings Only Work For the First Server When an Object is Migrated to Several Servers

Mappings imported from Domain Migration Administrator are copied only to the first server where the object is migrated for mapped objects migrated to more than one server.

Migrated Free/Busy Information May Not Display Correctly For Calendars Containing Only One Item

Migrated calendars containing only one item may display a solid white bar instead of displaying Free/Busy information when you make an appointment. Outlook updates Free/Busy information periodically, which may fix the display automatically. You can also choose to manually restore this information. To manually restore the Free/Busy display, run Outlook using the /CleanFreeBusy switch from the command-line on the client computer as in the following example: 

"C:\Program Files\Microsoft Office\Office\Outlook.exe" /CleanFreeBusy
Return to Top

Objects with Special Characters May Not Synchronize

Some objects that have special characters in the object name, such as the tilde (~), question mark (?), backslash (\) percent (%), or ampersand (&), may not synchronize correctly during a directory synchronization.

EMProfile Update Opens Multiple Outlook Windows

If Microsoft Outlook is already running, EMProfile Update opens additional instances of Microsoft Outlook for each profile on a computer. This problem may affect you when you test EMProfile Update, but is unlikely to occur when you implement EMProfile Update in a login script. To avoid this issue, close Microsoft Outlook before testing EMProfile Update.

Return to Top

Distribution List Notes

The following distribution list migration issue is currently being researched. If you need further assistance with any issue, please contact Technical Support:

Migrated Distribution Lists Containing a Forward Slash Do Not Maintain Membership

Exchange Migrator does not update membership in migrated distributions lists with names that contain a forward slash.

Return to Top

Mailbox Notes

The following mailbox migration issues are currently being researched. If you need further assistance with any issue, please contact Technical Support:

Running Anti-Virus Software During Migration May Prevent Migration of Some Mailbox Information

Running anti-virus software that is based on anti-virus application programming interface (API) on the source or target Exchange servers during migration may prevent migration of some information associated with a mailbox. If you migrate mailbox information and notice that some information is not migrated, disable virus software on the source and target Exchange servers and remigrate the objects. For more information about this problem, see the appropriate Microsoft support article.

Delay While Exchange Migrator Starts Mailbox Synchronization with Exchange 2000 Target

Mailbox synchronization may take a long time to start when synchronizing more than 100 objects to an Exchange 2000 target.

Modifying Mailbox Objects in an Exchange Migrator Project

If you include mailbox objects in an Exchange Migrator project and then delete or move them, you can adversely affect the results of the migration, or cause errors or failure. Delete unnecessary mailboxes or other mail objects before you include them in an Exchange Migrator migration project.

Exchange Migrator May Migrate Address Types Not Defined on the Target

Exchange Migrator may migrate address types not defined on the target when you specify to only keep email types defined on the target in the migration options wizard.

Exchange Migrator May Create A Random Address on Migrated Mailboxes on the Target Server

Exchange Migrator may create a random address and add it to migrated target mailboxes. The source mailbox forwards mail to this address during your migration. You can remove the address after you complete your migration.

Return to Top

Public Folder Notes

The following public folder issues are currently being researched. If you need further assistance with any issue, please contact Technical Support:

Shortcuts to Public Folders in a Mailbox Favorites Folder are not Migrated

Shortcuts to public folders that are in a mailbox Favorites folder on the source Exchange server are not migrated.

Public Folders with Names Containing a Backslash (\) May Not Migrate

Public folders with names containing the backslash (\) character may not migrate. Rename public folders with names containing this character before selecting these public folders for migration.

Public Folders that Have Names Ending with a Space May Not Migrate

Public folders that have names ending with a space may not migrate. Rename public folders that have names ending with a space before selecting these public folders for migration.

Migrating A Large Number of Public Folders Using the Migration Wizard May Cause Migration Problems

When you migrate a large number of public folders at one time using the migration wizard, Exchange Migrator requires more memory than is specified in the User Guide. If your migration task requires more memory than is available, you may receive migration errors.

Return to Top

Reporting Notes

The following reporting issues are currently being researched. If you need further assistance with any issue, please contact Technical Support:

Conflict Reports May Not Report Microsoft Mail Conflicts

Conflict reports may not report Microsoft Mail conflicts between objects on your source and target Exchange organizations.

Conflict Report Not Reporting Any Data

The Objects Referenced By Target Custom Recipients Report does not successfully retrieve data when migrating either to Exchange 5.5 or Exchange 2000.

Delay While Exchange Migrator Gathers Report Data

Gathering report data for projects including 11,000 or more objects may take a long time. Divide objects into smaller migration projects in Exchange Migrator to avoid delays when gathering report data.

Return to Top

Undo Notes

The following undo issues are currently being researched. If you need further assistance with any issue, please contact Technical Support:

Undo Does Not Delete Objects Migrated to Exchange 2000

Undo does not remove objects migrated to an Exchange 2000 server.

Mailboxes Migrated Using Merge are Deleted from Target if You Undo the Migration

Undo deletes pre-existing mailboxes on the target Exchange server if you used the merge option to migrate mailbox properties from mailboxes with the same email address on the source.

Return to Top

Legal Notice

First Edition

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

© 1995-2002 NetIQ Corporation, all rights reserved.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

ActiveAgent, ActiveAnalytics, ActiveKnowledge, ActiveReporting, ADcheck, AppAnalyzer, Application Scanner, AppManager, AuditTrack, AutoSync, Chariot, Chariot VoIP Assessor, ClusterTrends, CommerceTrends, Configuration Assessor, ConfigurationManager, the cube logo design, DBTrends, DiagnosticManager, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, End2End, Exchange Administrator, Exchange Migrator, Extended Management Pack, FastTrends, File Security Administrator, Firewall Appliance Analyzer, Firewall Reporting Center, Firewall Suite, Ganymede, the Ganymede logo, Ganymede Software, Group Policy Administrator, Intergreat, Knowledge Scripts, Log Analyzer, Migrate.Monitor.Manage, Mission Critical Software, Mission Critical Software for E-Business, the Mission Critical Software logo, MP3check, NetIQ, the NetIQ logo, the NetIQ Partner Network design, NetWare Migrator, OnePoint, the OnePoint logo, Operations Manager, Qcheck, RecoveryManager, Security Analyzer, Security Manager, Server Consolidator, SQLcheck, Visitor Mean Business, Visitor Relationship Management, VoIP Manager, W logo, WebTrends, WebTrends Analysis Suite, WebTrends Data Collection Server, WebTrends for Content Management Systems, WebTrends Intelligence Suite, WebTrends Live, WebTrends Network, WebTrends OLAP Manager, WebTrends Report Designer, WebTrends Reporting Center, WebTrends Warehouse, Work Smarter, WWWorld, and XMP are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies.

Return to Top