Quest® Exchange Migration Wizard

Version 4.0.1

Release Notes

August 2, 2007

Contents

Welcome to Exchange Migration Wizard

Resolved Issues and Enhancements

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information

Welcome to Exchange Migration Wizard

Quest Exchange Migration Wizard is a migration and coexistence application for transitioning Exchange 5.5-based environments to new or existing Exchange 2000/2003/2007 environments. The product performs a gradual, unattended migration with a special focus on real-time synchronization for true coexistence during the transition period.

Back to Top

Resolved Issues and Enhancements

This release incorporates the following Exchange Migration Wizard updates: Update 20070321, Update 20070402, Update 20070411, Update 20070423, Update 20070525, and Update 20070619.

The following is a list of issues addressed and enhancements implemented in this release of Exchange Migration Wizard.

Back to Top

Known Issues

The following is a list of issues known to exist at the time of Exchange Migration Wizard 4.0.1 release.

General

1. Only one mailbox per user account can be migrated.
2. Single-instance messages are migrated as normal messages.
3. All Exchange 5.5 and Exchange 2000/2003/2007 servers must support all languages that are used in the source or target mailboxes or public folders. Otherwise, the EMW option to support Unicode will not take effect on a server.
4. If Unicode support is enabled, the EMW agents create bigger service files and have to transfer more data across the network.
5. It is recommended that you enable circular logging on Exchange 2000/2003/2007 servers to avoid growth of the transaction logs because of the EMW agents working on the server.
6. EMW agents may not work correctly if the mailbox messages, folders or properties are modified by the user while the agent is processing a mailbox.
7. If the account used to install EMW agents does not have administrative rights on the remote server, the agent components may not be correctly registered. This will lead to agent processes hanging on the server.
8. When you try to install EMW, if the free disk space on your computer is a multiple of 4-gigabytes, you might receive the following error message: Not enough space on drive C:\ to extract this package. To work around this problem, add or delete files on your computer so that the free disk space is not a multiple of 4-gigabytes.

Double-Byte Character Set Languages

• The Custom installation option is not available on operating systems with double-byte character set locales.
• EMW components don't work if their installation path contains symbols from double-byte character set (e.g., Japanese).
• Mailbox collection names containing symbols from double-byte character set are displayed incorrectly.

Hotfixes

• The Hotfix Installation Wizard will not install the EMW Shared components hotfix while the synchronization job is set up if the Shared Components has already been installed before.
• When you try to install a hotfix on the console computer running Statistic Collection Agent, the installation is terminated with error. To work around the issue, stop the Statistic Collection Agent and retry the installation.

Clusters

• Exchange Migration Wizard supports Windows NT 4.0 Enterprise Edition, Windows 2000 Advanced Server, Windows 2000 Datacenter, and Windows 2003 cluster servers. However, EMW was not tested in the mixed 2000/2003 environment.
• Exchange Migration Wizard does not support Microsoft Exchange 2007 clusters.
• Exchange Migration Wizard supports multi-node clusters running multiple Exchange Virtual Servers. Migration Manager detects such systems and configures agent services for automatic failover together with the Exchange services.
  However, if several Exchange Virtual Servers are running on a single cluster node, the agents can be installed and run only on one Exchange Virtual Server at a time. Thus, such Exchange servers can only participate in migration with Exchange Migration Wizard consecutively, one by one. There are also some Exchange Virtual Server limitations on clusters that have more than two nodes. Refer to Microsoft Knowledge Base article 329208 “XADM: Exchange Virtual Server Limitations on Exchange 2000 Clusters and Exchange 2003 Clusters That Have More than Two Nodes” for more details.
• If access to the cluster nodes is denied while the server properties are being modified, the Aelita Shared folder will be created not on the shared drive but on the local disk.
• When installing EMW agents on the cluster, the default path to the tracking database points to the Exchange cluster shared drive that is a member of the Exchange Virtual Server group. This is the default and recommended location. If the tracking databases are located on the local disk, they will not be moved to another cluster node when necessary.
• If the EMW Shared components are uninstalled from the cluster environment using the Install Agents Wizard, the shared components will be uninstalled from only one of the cluster nodes. To uninstall the shared components completely, run the Install Agents Wizard again.
• The EMW agents should not be installed on the cluster if any of the cluster nodes is down.

Project Manager

• If you open the Statistic Panel, the console may become unresponsive.
• EMW console does not work on the x64 platform.
• If you add an Exchange organization in EMW Project Manager and then delete a mailbox store from the organization, this change will not be reflected in the Project Manager. If you later select the deleted store to be processed be DSA agent, the agent will report errors.
• When you try switching a mailbox from the console and Microsoft Outlook is opened on the console computer, the switch will fail and temporary profiles will not be deleted.
• It is recommended to refresh the target organization after upgrading from previous versions of EMW if the target organization has been added to the old EMW project database.
• The EMW refresh mechanism updates DNs of Exchange stores specified in the Mailbox and Directory synchronization jobs if such stores (or their Administrative Groups/Storage Groups were renamed. Once DNs are updated, commit the jobs' changes using the Commit Changes option.
• The EMW refresh mechanism doesn't support Alias renaming of mailboxes. So if the mailbox specified as administrative mailbox in the Exchange Server properties, and Public Folder and Calendar synchronization job properties is renamed, the old mailbox name is still displayed in the corresponding Properties dialogs of EMW Project Manager.
• It is recommended to install and run the EMW Project Manager on a computer that is member of the target forest. If the EMW Project Manager computer is not in the target domain, EMW may fail to find a DC for that domain when adding the target Exchange organization to the EMW project database. If this happens, you may specify the target DC name (\\DCNAME) when adding the target organization.
• It is recommended to use the same Global Catalog DC when refreshing organizations. In such case, the refresh will work faster and the specified DC will be set as Associate DC for the Exchange server.
• When the target organization is refreshed, DNs of mailbox-enabled users are not updated in EMW project database if the AD container where the users reside is renamed. So, you will not be able to specify such users as administrative mailboxes in Public Folder and Calendar synchronization jobs.
  If this happens, use the Add Recipients to EMW Database option to re-add such users and update their DNs in the EMW project database.
• A warning message may appear while enumerating an Exchange 5.5 organization if an Exchange server has LDAP referrals configured. This does not affect the product functionality and the warning message can be ignored.
• Clicking Update Task for the directory synchronization job that is being performed can prevent the DSA from reading configuration information for the job. In this case, the agent will stop the current session.
• If an object’s distinguished name is longer than 450 characters, the object will not be displayed in Project Manager and an error message will be displayed when adding or refreshing a server that hosts the object. This happens because the SQL Server allows no more than 450 symbols for an indexed field.
• There might be resource leaks if EMW Project Manager is started on a remote server via terminal session.
• When setting up a new Directory synchronization job, Project Manager prompts you for the Directory Synchronization Agent installation path. However, if the QMMEx$ServerName$ shared folder already exists on the server, the path you specify will be ignored and the agent will be installed in the existing share.
• Normally, EMW Project Manager does not allow you to set up two-way All Public Folders synchronization in more than one public folders collection within the same job. However, if connection to one of the servers fails when configuring the job, Project Manager will allow you to do this, which may lead to issues during the public folders synchronization process.
• You can make the Mail Source Agent (MSA) resynchronize mailbox contents by selecting the corresponding options in the mailbox synchronization collection’s properties. But if the agent performs two or more jobs, committing changes for another job will clear these settings in the agent’s configuration database.
• You cannot specify a mailbox with the Display Name value of more than 100 symbols as administrative mailbox.
• When setting up two Public Folder synchronization jobs for two different sites of the same organization, the folder pair being the root of synchronization in one of the jobs will not be automatically excluded from another public folder synchronization job. This should be done manually via EMW Project Manager.
• If you add a synchronization root to a Public Folder synchronization job and the parent folder of this root is already a member of another synchronization job with the same source server, the job containing the parent folder should be re-committed. To do that, you can disable and re-enable any collection of this job, and then click Commit Changes.
• If there are 2000 or more containers in Active Directory or Exchange 5.5 directory, then when setting the directory synchronization job and browsing for a redirection container ('Redirection custom recipient container in Exchange 5.5' or 'Redirection custom recipient in Active Directory') the EMW Project Manager may stop working.
• If the mailbox switch was done and undone several times manually, the target mailbox may contain some duplicated messages.
• The EMW Project Manager marks the mailboxes switched by the MSA with a green tick. However, the statistics displayed by the Project Manager may show that these mailboxes as not switched.
• EMW Project Manager supports Unicode character sets (for example, the Japanese character set) if the language locale that contains the corresponding character set is installed on the console and set as default.
• If you change the password for an account used by EMW agents, Project Manager will not generate an error as expected but will continuously try to start the agents.

Directory synchronization

• After DSA creates a target account and sets the Associated External Account (AEA) attribute, you cannot change the AEA attribute using Exchange Tasks in the Active Directory Users and Computers snap-in. To resolve the issue, take the following steps:
   1. In the Active Directory Users and Computers snap-in, open the account Properties dialog.
   2. Go to the Exchange Advanced tab and click the Mailbox Rights button.
   3. Change the set of permissions and click OK to apply your changes.
• AD accounts created by DSA do not have the All Users value in the showInAddressBook attribute.
  Note: The issue is only applicable on Microsoft Exchange 2007.
• When you migrate resource mailboxes to Microsoft Exchange 2007, the mailboxes are migrated as user mailboxes.
• Because of the Unicode support the Directory Synchronization Agent (DSA) may exceed the maximum length of the attribute used to store auxiliary information about mail redirection (Custom Attribute 15 by default). It is recommended that you increase the allowed length of this attribute in Exchange 5.5 to 4096 symbols.
• The DSA will fail if an Exchange 5.5 container with a distinguished name longer than 255 symbols is selected as a member of the directory synchronization or as a container for object creation.
• The DSA does not always correctly synchronize an Exchange 5.5 object's ACL if the security principal that is granted permissions on the target object is represented by more than one permission entry in the target object's access control settings. (The list of the permission entries is shown when you click Advanced on the Security page of an object's properties in AD Users and Computers.)
• The Delivery Restriction lists of the target Exchange 2000/2003/2007 mailbox will contain only users that correspond to the mailboxes included in the source mailbox's delivery restriction list. Mail coming in via the redirection will be from the mailboxes that are not included in the target mailbox's list. A user might receive mail from a mailbox that was on the source Reject from list or might not receive mail from a mailbox that was on the source Accept only from list.
• If there are two or more Exchange 5.5 distribution lists or custom recipients with the same Display Name, the DSA will match them to the same target object.
• The DSA synchronizes the Exchange 5.5 mailbox EmployeeNumber attribute to the Active Directory user EmployeeID attribute. The EmployeeNumber attribute in Exchange 5.5 can be up to 256 symbols long, while the EmployeeID attribute can be 16 symbols long in Active Directory. If the source mailbox EmployeeNumber is longer than 16 symbols, it will not be synchronized.
• The Exchange 5.5 Assistant attribute is synchronized to the Windows 2000 Active Directory Secretary attribute.
  In Windows 2003 Active Directory, due to schema changes, the Exchange 5.5 Assistant attribute is synchronized to the Windows 2003 Active Directory msExchAssistantName attribute.

Mailbox, Calendar and Public Folder Synchronization

General

• If a mailbox is processed by MSA in a non-OST collection and then by MTA in an OST collection, the license counter will consider the mailbox as two processed mailboxes.
• It is strongly recommended not to stop MSA and Public Folders Source Agent during the first synchronization (and during the first session when the agents perform full resynchronization), since the source agents copy the folder hierarchy during this sync. If the agents are stopped during the first synchronization, some folders’ structure may not be copied to the target server and this will prevent the target agents from putting messages and subfolders in those folders.
• Microsoft Outlook should not be started on the servers where EMW agents are running. Starting Outlook there will result in an EFORM_REGISTRY error and agent failure. If Outlook is installed on the servers where EMW agents are running, the agents may fail with the MAPI_E_INTERFACE_NOT_SUPPORT error. The mail agents also cannot access the information store in the following cases: if Microsoft Outlook is running under the account of the user whose mailbox is being processed by the agent; if the user works with his or her offline folder; or if Outlook is showing a prompt for profile selection.
• If you migrate from Microsoft Exchange 5.5 having Microsoft Exchange Event Scripting set up, event scripting will not work after the migration.
• Forms from the organization forms library are not migrated.
• To perform public folder synchronization the accounts under which the appropriate EMW agents are running on the Exchange 5.5 server should be a Primary Windows NT account for the Administrator mailbox specified for the Public Folder and Calendar synchronization jobs.
• If the Administrator mailbox specified for the Public Folder or Calendar synchronization job is changed during the course of synchronization, the public folder synchronization agents and calendar synchronization agents will not work properly.
• The Administrator mailboxes specified for the Public Folder and Calendar synchronization jobs should not be added to the collection processed by the mail synchronization agents.
• EMW Mailbox and Public Folders synchronization agents do not support folders with a backslash (\) character in the folder name.
• Localized symbols in the folder names created via Outlook Web Access will not be copied correctly to the target servers.
• EMW agents will fail to work with a PST file if the full path to the file is longer than 255 symbols (including the file name). For example, the source agents might fail to create these files, and the target agents might fail to extract data from the PST files.
• If there is a conflict message on one side and the corresponding message is modified on the other side, the EMW agent will copy the modified message to the opposite side so that the conflict message will be overwritten and no longer conflict.
• If message properties such as Don't deliver before and Expires after were set for a message which was then synchronized by the EMW agents, and then these options were removed, the removal will not be synchronized to the target message.
• The messages and folders deletion will always prevail over other modifications. For example, even if the messages or folders corresponding to the deleted source messages or folders are modified, they will be deleted by the EMW agents.
• The following properties will not be synchronized by EMW agents:
  - The Any form property selected in the Allow these forms in this folder group of public folder Properties dialog box.
  - The Drag/Drop posting is a property specified in the Administration tab of the public folder Properties dialog box.
  - The Initial view on folder property specified in the Administration tab of the public folder Properties dialog box.
  - The Save sent message to property specified in the Delivery options group of the message Options dialog box.
  - The Have replies sent to property specified in the message Options dialog box.
• All the properties set in the Activities tab of the Contacts folder properties will not be synchronized by the EMW agents.
• Clearing of the following properties will not be synchronized by EMW agents if these properties are cleared during the synchronization:
  - The form deleted in the Forms tab of the source folder may not be deleted from the Forms associated with this folder list of the target folder.
  - If the Company, Categories and Contacts properties of the messages are cleared, the deletion may not be synchronized by EMW agents.
  - If the Completed, Follow up and Recurrence properties are cleared for the source message, the property deletions will be synchronized but the message will still have these properties.
• Users must have Editor or Owner permissions for a public folder or another user's folder in order to modify or delete messages after they have been migrated. A user with Author permissions for the source folder will not be able to edit his own messages that were copied by EMW agents to the corresponding target public folder.
• The agents working on Exchange 2000/2003/2007 server may hang up if the DC associated with this server becomes unavailable.
• The Mail and Calendar Synchronization Agents may work incorrectly if the size limit of the source or target mailbox is reached. Make sure that the mailboxes being synchronized are not close to their size limit. If the issue has occurred, contact Quest support.
• All agents may work incorrectly if they do not have access to the public store both on the source and target.

Mailbox Synchronization

• EMW cannot synchronize email messages signed with S/MIME from target (Windows 2003 with Exchange Server 2003 Service Pack 1) to source (Exchange Server 5.5) servers during public folder and calendar synchronization. Such messages are skipped by the agents. The following error is logged for every skipped message: MAPI_E_NOT_FOUND. Synchronization from source to target works fine for such messages.
• EMW mail agents may not work correctly if the target Exchange 2000/2003/2007 mailbox is modified before the mailbox switch.
• EMW agents do not update some links in copied messages, tasks, notes, and calendar and journal entries.
• The mailbox synchronization agents do not work with hidden Exchange 5.5 and Exchange 2000/2003/2007 mailboxes.
• A mailbox will be switched even if there are conflict appointment items that were processed but not synchronized by the Calendar Synchronization Agent due to the conflicts. The mail agents will consider such appointments to be in sync.
• EMW mail agents always create English Outlook default folders such as Tasks and Notes in an Exchange 5.5 mailbox even if nobody has ever logged into the mailbox or if it was used as an additional mailbox only. The names of Exchange 5.5 default folders such as Inbox and Deleted items that will be created will depend on the localization of Microsoft Outlook and Exchange 5.5.
• The Mail Target Agent cannot find a mailbox during a period of time right after the mailbox is moved to another mailbox store. The issue is addressed to the Microsoft Exchange 200/2003/2007 design.
• The following warning may be written to the log file even after a successful mailbox move: "Warning -2147217772 Caller requested write access to a read-only object." The issue is applicable to Microsoft Exchange 2000 and 2003.
• The Mail Source Agent cannot copy hidden messages for the default calendar folder. This causes that view, form, and other properties of the folder to not be synchronized.
• If the source mailbox message has a plain text attachment and the subject of the corresponding target message is changed after its synchronization to the target, the attachment may be duplicated.
• If the source mailbox Draft folder contains the non-dated messages, the corresponding target messages will all be dated with the same date.
• Switch notification sent to the Exchange 2000/2003/2007 mailbox can sometimes appear in the user's source mailbox.
• If nobody has ever logged on to an Exchange 5.5 mailbox, the Mail Source Agent will not find the default Drafts folder and will get an error. This may prevent the mailbox from being automatically switched, if mailbox switch with errors is not allowed.
• Mail Target Agent reports an error when trying to move mailboxes from Microsoft Exchange 2007 to Microsoft Exchange 2003.

Public Folder Synchronization

• If you migrate mail-enabled public folders from Microsoft Exchange 5.5 to Microsoft Exchange 2007, the target public folders will be missing from all address books. To resolve the issue, use the Public Folder Directory Synchronization Tool, as described in the Exchange Migration Wizard Resource Kit User Guide. Alternatively, use the Exchange 2007 Apply Address List wizard to reapply the desired address lists.
• If the Limit administrative access to home site check box was cleared for a public folder before its migration and then was selected again after the public folder was copied to the target server and the public folder agent started synchronizing it, then the contents of that public folder may be deleted from both the source and target servers.
• In Exchange 2003/2007, the size limit for public folder items is set by default to 10MB. It is recommended that you increase or remove the size limits on the target before you start the synchronization. Otherwise, if you set a two-way public folder synchronization, you may lose the attachments larger than 10 Mb on the source side.
• It is recommended that the network administrator manually create the Aelita EMW Recycle Bin folder and replicate it to all the organization servers involved in the public folder synchronization. The EMW agents automatically create this folder, but it is not replicated to other servers. If the Aelita EMW Recycle Bin folder is created in a site that does not have the public folders affinity set to the current site, the agent will not be able to synchronize deleted public folders. The Limit administrative access to home site check box should be cleared in the folder properties.
• The Exchange 2000/2003/2007 account under which the Public Folder Synchronization agents are running should be mail-enabled and have a mailbox in the same Exchange 2000/2003/2007 organization.
• The Read/Unread status of public folder messages will not be synchronized.
• A user can customize views for any public folder. The information about user-defined views is stored in the mailbox and is not synchronized by EMW agents. The user will have to configure the views for each public folder again after mailbox switch.
• Conflict messages may be created if the public folders synchronized by EMW agents are replicated between servers.
• If a source public folder has a rule to forward messages to a user, the user will not be able to reply to the messages forwarded from the folder after the mailbox switch.
• Some of public folders admin attributes, such as the folder size limit, are not synchronized.
• Synchronization of moved public folders and messages is supported only if they are moved within the same server.
• Suppose messages are deleted from a source public folder and the corresponding messages on the target folder are moved to another location. During two-way synchronization, the deleted source messages will be moved to the source folder corresponding to the target folder where the messages were moved. During one-way synchronization, only the target messages will be moved.
• If a public folder is moved from one public folder collection to another, this folder may be moved to the Aelita EMW Recycle Bin by the Public Folder Target Agent if the Aelita EMW Recycle Bin folder exists. If the Aelita EMW Recycle Bin folder does not exist, the public folder will be deleted.
• If the public folder job was set up without excluded folders and synchronized by the agents, further exclusion of any subfolders will not prevent the agents from synchronizing the deletion of the excluded folders or their subfolders.
• If the public folder is moved to another folder excluded from the synchronization, the PST file containing the information on this move will be archived.
• Suppose a source public folder is modified and the source agent creates a PST file including these modifications, and then the corresponding target folder is also modified. During two-way synchronization, the modifications made on the source folder will be applied to the target folder, and the modifications made on the target folder will be applied to the source folder. During one-way synchronization, the modifications made on the source folder will be applied to the target folder, and the agent will consider the folders to be in sync.
• During two-way synchronization, the simultaneous move of source and corresponding target messages in public folders will cause duplication of the messages in both the source and target. During one-way synchronization, the messages will be duplicated in the target only.
• If the Copy only messages not older than option of the Public Folder Source Agent is changed to Copy all messages during synchronization, messages older than the messages of the previously specified age will not be synchronized. In this case, full resynchronization is required. For more information about full resynchronization, please refer to the appropriate EMW documentation.
• During two-way synchronization, if some messages have been copied to the target folder and then deleted from the target folder before the Public Folders Source Agent installed on the target server processed them, the deletion will not be synchronized back to the source folder.
• Modifying the replication lists while the public folder synchronization agents are running is not recommended.
• The agents synchronize only the folders for which they have a local replica. The root folder you specify for a public folder synchronization job and all its subfolders should be replicated to the agent's server.
• Deletion of the Forms specified for the source public folder will not be synchronized to the target public folder (that is, the deleted forms will not be deleted from the target public folder Forms associated with this folder list).
• User-defined fields of public folders may not be synchronized.
• If two-way synchronization is configured between an Exchange 5.5 folder and Exchange 2000/2003/2007 'All Public Folders', the public folder agent's account must be the Owner of the Exchange 5.5 folder. If the agent does not have Owner permissions, the top level public folders created in Exchange 2000/2003/2007 will not be created in Exchange 5.5. Note that if the Public Folder Target Agent creates this synchronization root folder, it will not grant Owner permissions to the agent's account.
• If a public folder has once been selected as synchronization root, and then this folder is moved to a location under another synchronization root, the public folder synchronization agents will consider its subfolders deleted. The initial synchronization root folder's subfolders will be moved to the Aelita EMW Recycle Bin folder.
• If a public folder has been excluded from synchronization together with its subfolders, returning it from exclusion will not synchronize the folder hierarchy. The corresponding folder will not be created on the target server, and the PUB files with folder contents will not be processed. You will have to use the EMW Cleanup Wizard to clean the sync status for the folder's hierarchy, rules, permissions, and associated contents. Note that this may cause folder design conflicts on the target server.
• If a public folder synchronized by EMW is replicated to other Exchange servers within the same organization, folder design conflicts will be generated when the folder's properties are modified on the target server and on a server with the folder replica.
• The public folder synchronization agents will not work if the Administrator Mailbox for the job has an associated public folder server different from the agent installation server. The setting can be verified in the properties of the Private Information Store where the Administrator Mailbox resides.
• If the synchronization root folder is created by the EMW agents, there must be local replica of the folder's parent folder on the agent's server. Otherwise the folder created by EMW agents be invalid and may be inaccessible.
• If the Limit administrative access to home site check box is selected in the properties of the public folder homed in another site, not in the site where the public folder agents are running, it will not be correctly synchronized. For all the public folders that are to be synchronized by the public folder agents and are not homed in the site where the public folder agents are running it is strongly recommended to deselect the Limit administrative access to home site check box.
• If the public folders collection contains the "ghosted" public folders (public folders having no local replica on the server where the public folders agents are running) and these public folders are homed on the Exchange server which is switched off or unavailable, the Public Folder Source Agent may hang while processing these folders.
• If the public folders collection contains the "ghosted" public folders (public folders having no local replica on the server where the public folders agents are running) and these public folders are homed on the Exchange server which is switched off, the Public Folder Target Agent will not deliver information to any folders of the collection.
• If the Public Folders Target Agent performs several attempts to process the PST file (the quantity of attempts is specified in the agent's Properties dialog box), and during this time a new PST file is created and received by the agent, the new data contained in the new PST file may be overwritten by the old data contained in the old PST file.

Calendar Synchronization

• Appointment items created via Exchange 2000/2003/2007 Outlook Web Access might not be correctly copied to the Exchange 5.5 servers. • If a mailbox is hidden from the Global Address List, the Free/Busy message for that mailbox will not be synchronized.
• If a one-way calendar synchronization is established, all appointments from the target mailbox are re-synchronized with the source mailbox after the mailbox switch. The workaround is to use a two-way calendar synchronization.
• Suppose, the Calendar Synchronization Agent is set to synchronize Free/Busy between two servers (source server S1 and target server T1). The mailbox is moved from T1 to another AG (target server T2). If the synchronization job is modified so that CSA synchronizes F/B from S1 to T2, the F/B will not be synchronized any more. However, if the job is not modified (the CSA synchronizes F/B from S1 to T1), the F/B will still be synchronized. If the job is modifies in the above stated way, but the CSA is simultaneously set to synchronize appointments between the same servers (S1 and T2), the Free/Busy will be synchronized.
• If the one-way calendar synchronization job is set up, the Free/Busy messages synchronization will be performed in two ways.
• It is recommended to install the CDO patch referred to in Microsoft KB articles Q314606 and Q312273 to improve calendar synchronization.
• If a two-way calendar job is set up after a one-way calendar job began running, the calendar synchronization agent will copy to the source all the target messages, including those already synchronized.
• If the Public Store is dismounted, the Calendar Synchronization Agent will not synchronize appointments.
• The Calendar Synchronization Agent will not synchronize permissions for hidden mailboxes.
• If the users of Exchange 5.5 and Exchange 2000/2003/2007 organizations schedule resource request appointments between the sessions of the Calendar Synchronization Agent, both the Exchange 5.5 and Exchange 2000/2003/2007 resource mailboxes will accept the appointments. The Calendar Synchronization Agent will then synchronize these appointments. Thus, appointments created in different environments may result in different resource requests items in the resource mailbox's schedule. If the “Automatic decline conflict message request” option is selected Exchange Server deletes one of such items when the users try to modify these appointments. CSA will synchronize such deletion and the item will be lost.
• Outlook 2003 may fail to display an appointment schedule if the appointment was created on the source using Outlook 2003 and a DL was used to invite members. The workaround is to update the corresponding distribution group membership on the target using Outlook.

Rules Synchronization

• Only rules that are turned on in the source mailboxes are copied.
• The order of the rules can be changed in the target mailbox.
• If any link in a rule's conditions (such as From or Sent to fields) is set up for a source object that cannot be matched to a target object, the source object's distinguished name or e-mail address will be displayed in the rule after synchronization.
• If a rule contains a non-resolved name (for example, if the From field was manually populated without checking names), that name will be copied to the target mailbox as simple text.
• The After I send the message mailbox rules are not synchronized.
• When copying public folder rules with templates, the agents may fail with a MAPI_E_NO_ACCESS error, caused by the Exchange 2000/2003/2007 server behavior.
• It is not recommended to synchronize public folder rules from Exchange 2000/2003/2007 to Exchange 5.5, because the source folder’s rules might be lost if any errors occur during the synchronization.
• If a rule is configured to reply with a template, it will be synchronized to the target only if the PFSA is set to synchronize folder-associated information. This is because the templates are stored as folder-associated information.
• If any link in a public folder rule's actions (such as Forward to) is set up for a source object that cannot be matched to a target object, the rule will not be synchronized.
• When a user logs on to the Exchange 2000/2003/2007 mailbox for the first time, Outlook may display a message box asking whether to keep either the server-side or the client-side rules. The user should choose to keep server-side rules. The rules will start to work after the user logs off from the mailbox and logs on again (that is, after the user restarts Outlook).
• While updating the client profile, the Client Profile Updating Utility removes all the target mailbox rules.
• EMW agents may fail to copy some of the rules if the 32 KB "packed data" limit for an Inbox or a public folder’s rules is exceeded. For more information please see the Microsoft Knowledge Base article available at http://support.microsoft.com/default.aspx?scid=kb;EN-US;q241325.
• The Edit rule button may be disabled in the target mailbox for an Out of Office rule copied by EMWProf. To make the rule available for editing, the user should right-click the rule in the Out of Office Assistant dialog box and click 'Move rule to this profile' on the shortcut menu.
• A public folder's rules do not work while the EMW PFTA is working with the folder. The rules start working as soon as the agent starts processing another folder.
• If a public folder is moderated, two rules are automatically set up for a folder. If any one of the source folder’s rules cannot be copied (for example, if the moderator’s mailbox cannot be matched to a target user), the 'Moderated folder' settings of the corresponding target folder will not be valid.
• In order that the Reply with template rule is correctly synchronized for the moderated public folder, the corresponding target folder should be mail-enabled, the rules should be synchronized, and after that the source folder rules and the associated contents should be cleaned with the help of EMW Cleanup Wizard.
• If you use the X.400 connector for mail redirection, mailbox rules do not work for mail coming via the connector.
• If all rules specified for a source public folder are deleted, and full resynchronization is initiated before the public folder synchronization agents process this folder, the rules will not be deleted from the target public folder.
• #NET FOLDERS# rules copied from the Inbox folder to a public folder are not migrated.

Collection Processing

• If a public folder synchronization collection is disabled or deleted before the Public Folder Target Agent processes all PUB files for this collection, data from these PUB files can be replicated back to the source server.

Full Resynchronization

• If any messages or folders were deleted from the target server, full resynchronization will not restore these deleted items on the target server until Microsoft Exchange cleans the tombstone objects. For more information on full resynchronization, please refer to the appropriate EMW documentation.
• Items deleted during the resynchronization session may be not deleted on the target server.

Permission Copying

• If permissions are simultaneously changed for the source and target folders, the permissions may not be synchronized properly.
• Permissions will not be copied for a target public folder whose principal is hidden from the target domain Global Address List and not shown in other Address Books.
• In Exchange 2000/2003/2007, the size limit of the client permissions ACL is less than in Exchange 5.5. If a source ACL size exceeds the ACL size limit on the target, the error MAPI_E_TOO_BIG will appear in the Mail Target Agent or Public Folder Target Agent log. The agents will not be able to create subfolders in the target mailbox or public folder. The workaround is to decrease the size of the source ACL, for example by assigning permissions through groups, or contact Quest support.

Processing Remote Users Collections

• If a user or the Calendar Synchronization Agent is logged on to the source mailbox, the Mail Source Agent will skip the mailbox from processing in the current session, by default.
• If the remote user is working online, Microsoft Outlook will stop working for the time when the mailbox is being processed by the agent if the agent is set not to check whether the mailbox is logged on. The agent makes this check by default.
• It is recommended that you leave the default sleep interval between sessions for the Mail Source Agent (30 minutes) if the agent processes the Remote Users Collections. Otherwise, Active Directory replication cycle may not complete after the MSA has re-homed a mailbox and the MSA may transfer the mailbox content to the store that was initially set by the Directory Synchronization Agent rather than to the store specified in the Remote Users Collection.
• If you decide to stop migrating a mailbox after it has been added to the Remote Users Collection and the Mail Source Agent for Microsoft Exchange 2000/2003 has started processing it, has removed it, but has not yet recreated it, you will not be able to log on to the corresponding target mailbox nor to move the mailbox. To recreate this mailbox, you will have to first remove it using Exchange Tasks and then perform a full directory resynchronization.
• If a mailbox was switched within the Remote Users Collection, and some of its messages were copied from the target mailbox to the source mailbox by the Calendar Synchronization Agent, and the user synchronized these messages to the OST file before the mailbox profile was updated by EMWProf, these messages may become conflict messages after the EMWprof updates the profile.
• The Calendar Synchronization Agent cannot synchronize a mailbox being synchronized within the Remote Users Collection and will log the error messages between the target mailbox deletion and the target mailbox recreation.
• Mailboxes that have been migrated within the Remote Users Collection should never be included in ordinary mailbox collections. Otherwise, when a full resynchronization is performed for an ordinary collection that includes such a mailbox, all messages created by the user when working offline and copied by the mail agents from the source mailbox to the target mailbox will become conflict messages after the target mailbox has been synchronized with the OST file.
• If a source mailbox message was modified when working both online and offline, it will become a conflict message after the mailbox has been copied to the target within the Remote Users Collection and modified in the target mailbox when working online. The issue relates to Exchange 2000 mailboxes only.
• If your target Exchange organization is operating in mixed mode, it is strongly recommended to be careful when selecting the target Mailbox Store for the Remote Users Collection. For mailbox creation, it is recommended to select only the Mailbox Store located in the Administrative Group where the existing target mailbox is homed. If you select the store in another Administrative Group for mailbox creation, you will not be able to move the mailbox from this store after migration is finished until you switch your organization to native mode.
• If a mailbox was switched within the Remote Users Collection, its profile was updated by EMWProf, it was synchronized with the OST, the switch was undone for this collection, and the Remote users Collection was synchronized by the Mail Source Agent again, then the messages modified in the target mailbox by the last copying will become conflict messages after mailbox synchronization with OST. If the DLs were created in the Contacts folder of the target mailbox, these DLs may also conflict after mailbox synchronization with OST.
• If the corresponding target mailbox exists for a source mailbox included in the Remote Users Collection, the target mailbox will be removed with all its contents when the Mail Source Agent processes the collection.
• Favorites are not preserved for the target mailbox. If a remote user works offline, Favorites may still be present. However, as soon as the user synchronizes OST with his or her mailbox, the Favorites will be lost.
• Users will not be able to use Microsoft Outlook to log on to their mailboxes while the Mail Source Agent is processing them within the Remote Users Collection.
• The schedule set for the Mail Source Agent will not be enforced if the agent has begun processing a mailbox within the Remote Users Collection. For example, if the agent was scheduled not to work from 1 am through 6 am and at 1 am the agent is processing a mailbox, it will not stop until the mailbox processing completes.
• It is recommended that the target mailbox size limit be greater than the source mailbox size limit. Otherwise, the MSA will repeatedly attempt to copy the source mailbox to the target server when migrating a mailbox within the Remote Users Collection.
• The Offline Address Books and folder properties are not preserved in the OST file when the mailbox is migrated within the Remote Users Collection.
• It is strongly recommended not to stop the MSA while it is processing a mailbox within the Remote Users Collection.
• The target Exchange server application event log will log an error when a Remote Users Collection mailbox is copied to the target server.
• When the agent is processing a Remote Users Collection, it does not check the available disk space on the target Exchange server. Thus, the administrators need to make sure that there is enough free disk space on the target Exchange server before starting the agent.
• It is recommended that you run Calendar synchronization for the mailboxes being synchronized in the Remote Users Collections only after the mailboxes are synchronized and switched by the Mail Source Agent. Otherwise, the duplicate folders may appear in the target mailbox if the Calendar Synchronization Agent and the Mail Source Agent log on to the target mailbox simultaneously.

Statistics

• Statistics are not available for remote collections.

Exchange Migration Preparation Wizard Issues

• If you are using Exchange Migration Preparation Wizard on a computer running Microsoft Windows 2000, information gathering stops with an error when processing items containing both quotation marks (") and either the less than sign (<) or greater than sign (>). As a result, the rest of items will not be processed and reports will be incomplete.

Back to Top

Upgrade and Compatibility

Upgrade is supported from EMW 3.6 and higher.

After installing new product version, perform the following steps:

1. Refresh the target Exchange Organization using the Global Catalog DC.
2. Right-click the Exchange Migration Project node in the EMW Project Manager and select Hotfix Installation Wizard from the shortcut menu. Install the hotfix on all source (Exchange 5.5) and target (Exchange 2000/2003/2007) servers by following the Hotfix Installation Wizard steps.

Back to Top

System Requirements

Before installing Exchange Migration Wizard, ensure your system meets the following minimum hardware and software requirements:

Source Servers

Target Servers

EMW Project Manager Server

EMW Database Server

EMW Directory Synchronization Agent Server

Back to Top

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

Back to Top

Getting Started

Contents of the Release Package

The Exchange Migration Wizard CD contains the following:

1. Exchange Migration Wizard 4.0.1 (4.0.1.142)
2. Exchange Migration Wizard Resource Kit (4.0.0.20)
3. Exchange Migration Wizard Deployment Tools (February 2007)
4. Exchange Migration Preparation Wizard (2.0.07.0)
5. Quest Client Profile Updating Utility (4.3.8.115)
6. Quest Update Utility for Outlook 2003 (1.0.0.10)
7. Quest Offline Folder Wizard (1.0.0.19)
8. Reporting Console (7.2.438.01)
9. Report Pack for EMW (7.2.013.00)
10. Reporting Web Portal (7.2.037.06)
11. Reporting Web Part for Microsoft SharePoint Portal Server 7.2 (7.2.002.03)
12. Windows Installer 2.0
13. MSDE 2000 (8.0) SP3
14. Quest installation wizard for MSDE 2000 (1.0.6.0)
15. MDAC 2.8
16. Flash 5 ActiveX control (4.7.1)
17. Adobe® Acrobat Reader 7.0.8
18. Product Documentation, including:
    • Exchange Migration Wizard - Quick Start Guide
    • Exchange Migration Wizard - User Guide
    • Exchange Migration Wizard - Overview
    • Exchange Migration Wizard - What's New
    • Exchange Migration Wizard - Upgrade Guide
    • Exchange Migration Wizard - Best Practices
    • Exchange Migration Wizard - Resynchronization
    • Exchange Migration Wizard - Rolling Exchange Migration
    • Exchange Migration Wizard Resource Kit - User Guide
    • Exchange Migration Wizard - Add-In Reference
    • Exchange Migration Wizard - Attribute Mapping Rules
    • Exchange Migration Wizard - Directory Object Matching
    • Exchange Migration Wizard - Localization Support
    • Exchange Migration Preparation Wizard - User Guide
    • Client Profile Updating Utility - User Guide
    • Offline Folder Wizard - User Guide
    • Reporting Console - User Guide
    • Reporting Console - Quick Start Guide
    • Reporting Console - Expert Guide
    • Reporting Console OLAP
    • Web Reporting Components - User Guide
    • Online Help

Installation Instructions

Install EMW by running Deployment Tools from this CD (can be run either from autorun or by starting launch.exe from the EMWDeploy folder).

To view reports on the Exchange migration process, install both Reporting Console and Report Pack included on this CD. Reporting Console and Report Pack can be installed on any computer on your network.

If you do not have a SQL Server available in your network, you must install MSDE before you install Quest Exchange Migration Wizard 4.0. Before installing MSDE, close all previously opened applications.

Note: To see the demos included in Deployment Tools or permissions tutorial (available on the Help menu of EMW Project Manager), you might need to install the Macromedia Flash 5.0 plug-in for Internet Explorer. To install the plug-in, run the InstallAXFlash.exe file from the CD REDIST\FLASH folder or from Autorun.

Back to Top

For More Information

Contacting Quest Software:

Refer to our Web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

• Quickly find thousands of solutions (Knowledgebase articles/documents).
• Download patches and upgrades.
• Seek help from a Support engineer.
• Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

Back to Top

This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

© 2007 Quest Software, Inc. ALL RIGHTS RESERVED.

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

If you have any questions regarding your potential use of this material, contact:

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

Back to Top