Quest® Migration Manager
Version 8.1
Release Notes
January 16, 2008
Resolved Issues and Enhancements
Quest Migration Manager is the comprehensive solution for seamless simple or extensive Active Directory restructuring and transparent inter-org Exchange migration.
Quest Migration Manager 8.1 includes the following new features:
The following is a list of issues addressed and enhancements implemented in this release of Migration Manager.
|
Feature |
Resolved Issue |
Change Request |
|
General |
You cannot run Agent Manager, if you have Terminal Services Client 6.0 installed on your computer. Terminal Services Client 6.0 is included in the Microsoft Update KB925876. To resolve the issue, try uninstalling the update | ST#34662 |
| MSI packages for exported resource updating tasks generate the AeEmw4.dll failed to register error during installation. | ST#42917 | |
| Double-byte symbols are displayed incorrectly in the mailbox properties dialog opened from the Migration Manager Console. | ST#39445 |
This release incorporates the following Migration Manager updates: Update 20070705, Update 20070719, Update 20070913, Update 20071005, and Update 20071010, Update 20071115, and Update 20071207.
|
Update |
Resolved Issue |
Change Request |
| Update 20070705 |
If the vmover.ini file has Unicode format, vmover does not
process the following resources: - Shares - Internet Information Services (IIS) - Roaming profiles (in case the SIDHistory parameter value is Yes). |
ST#33375 |
|
Vmover may fail to process shares with either of the following
errors: - Shares -2147024809 (Error) The parameter is incorrect. ATL exception. - Shares -1 (Error) Applied different SD. |
ST#34135 | |
|
Update 20070719 |
||
| If target domain controller (DC) is running Microsoft Windows 2003 and the target group contains more than 1.500 members before the migration (or 1.000 members, if the DC is running Microsoft Windows 2000), then after you complete the migration and undo it, all members will be removed from the target group. | ST#37033 | |
| Update 20070913 | ||
| Directory Synchronization Agent may fail when trying to resolve two conflicts with one object involved. | ST#41326 | |
| Update 20071005 | ||
| Directory Synchronization Agent cannot migrate or synchronize group membership, if the target group and group members are located in different domains of the same forest.
The issue is applicable only to target domain controllers running either of the following: - Microsoft Windows 2003 SP1 without KB906381 installed - Microsoft Windows 2003 SP1 with KB926122 installed (Security bulletin MS07-039) - Microsoft Windows 2003 SP2 |
ST#29848 | |
| Update 20071010 | ||
| If you are using custom filters, the following error may be displayed when you click the Set Filter button in the Synchronization Properties Wizard: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. After you get the error, the Exclude list is emptied. | ST#17361 | |
| Update 20071115 | ||
| When Directory Synchronization Agent applies aliases and SMTP proxyAddresses, the agent writes symbols that are not allowed in Microsoft Exchange 2007. | ST#43830 | |
| Update 20071207 | ||
| If an E-mail address policy on Exchange 2007 target contains a proxy creation rule, and the rule was edited manually, DSA fails to process objects to which such policy is applied. | ST#27756 | |
| DSA does not create mailboxes In Exchange 2007 organization that has e-mail address policies with not configured conditions. Log file contains a message Error 0xe1000010. Attribute purportedSearch not found in object. | ST#44967 |
The following is a list of issues known to exist at the time of Migration Manager release.
|
Feature |
Known Issue |
Change Request |
|
General |
If the SQL Server is unavailable, the Open Project Wizard may display an Incorrect password message box. Considering the fact that by default MSDE is installed with disabled network support this may arise some issues. For details on enabling all the network protocols refer to the Opening a Migration Project section of the Migration Manager Quick Start Guide. | ST#19321 |
| When you specify a new license instead of the old one, you may get the You are now using N% of your license message, where N is larger than 100. You will stop getting these messages in a certain time, or you can resolve the issue by restarting the Quest Directory Synchronization Agent Configurator Service on the computer where DSA is installed. | ST#47876 | |
| After you install Microsoft SQL Server Desktop Engine from the Migration Manager CD, you must start SQL services manually. | ST#43888 | |
|
If you uninstall Microsoft Terminal Services Client 6.0, Agent Manager will not work. Re-installing Terminal Services Client does not resolve the issue. |
ST#44258 | |
| Express setup and Open Project Wizard may report the Failed to configure project error if you are running setup on localized (non-English) version of Microsoft Windows. Despite of the error text, only Statistics Portal will not be configured. | ST#36090 | |
| You cannot remotely deploy Directory Synchronization Agent on a computer running Microsoft Windows XP. | ST#46051 | |
| If you install Quest Migration Manager Statistics on a computer running localized (non-English) version of Microsoft Windows, you will not be able to configure Statistics Portal from the Open project wizard for a project. To workaround the issue, create a local user Everyone on the computer where Quest Migration Manager Statistics is installed before you start configuring Statistics Portal. | ST#45547 |
|
Feature |
Known Issue |
Change Request |
|
Directory Migration and Synchronization |
DSA sets invalid HomeMTA attribute, when a new mailbox created on a second or successive clustered mailbox Exchange 2007 server. To learn more about the issue, see the Microsoft Knowledge Base article available at http://support.microsoft.com/kb/928811. | ST#35734 |
| During the two-way synchronization, source alias may be replaced with the target alias changed by DSA. | ST#44532 | |
| Denied objects within synchronization scope are not placed to Failed objects queue. | ST#44136 | |
| BitLocker and Trusted Platform Module Recovery recovery information backed up in the child object of the AD computer object is lost after migration. | ST#38557 | |
| DSA does not resolve group membership on the target, if the target forest schema was not extended by Exchange installation. | ST#35954 | |
| Antiviral and antispyware software may identify Migration Manager agents and services as malicious software. You may ignore these warnings. | ST#45347, ST#45069 | |
| It is recommended to configure recipient policy to convert non-latin symbols to latin. Otherwise the non-latin symbols will be lost. | ST#46825 | |
| For safety reasons deletion of the matched objects in the target organization is not synchronized from target to source even if "synchronize object deletions" option is enabled in synchronization properties. As a result the source objects are not affected if the matched target objects are removed. To change the default behavior, refer to instructions in the Quest KB article https://support.quest.com/SUPPORT/index?page=solution&id=SOL21332. | N/A | |
| Conflict resolution rules with scope equal to forest are verified using the Global Catalog. As a result, this scope type can be used only for attributes published in the Global Catalog. | ST#19140 | |
| Merging mail-enabled objects during the directory synchronization may cause creation of two primary SMTP addresses for the target object, if the target object had different values in primary SMTP address and targetAddress attribute. | ST#18611 | |
| The Directory Synchronization Agent cannot synchronize object deletion for the group that is set as the primary group for any domain user account, computer account or inetOrgPerson. | ST#15618 | |
| A migrated (synchronized) account's primary group might be set to a source group that has not been migrated yet. If so, when target-to-source domain sync is performed by two-way synchronization job, any modification of account’s primary group will not be synchronized until corresponding source group is migrated (synchronized) within the same migration project. This helps to prevent from losses of primary group values in source domain during initial sync. | N/A | |
| Undo does not restore msExchMailboxSecurityDescriptor Active Directory attribute and mailbox security descriptor in the Exchange store. | CR#0163748 | |
| Trust Migration Wizard does not migrate forest trusts. | CR#151624 | |
| An issue may arise if the Directory Synchronization Agent and Domain Migration Wizard simultaneously process passwords and SIDHistory on the same DC. | CR#165675, CR#165732 | |
|
Although several issues related to the The value provided for the new password does not meet the length, complexity, or history requirement of the domain
error were resolved, you may still get this error message in the following
situations: - If the source password is empty, while the minimum password length on the target is set to more than 0 characters. - If the source password was previously migrated to the target and is stored in password history of the target account. |
N/A | |
| If you merge migrated user accounts with existing target ones and later undo the action, the original passwords of target accounts are not restored. Restoration of all other attributes is not affected. | N/A | |
| When merging accounts, the migration sessions compare source and target password ages even if the Set password to option is selected. To avoid possible inconsistencies in setting passwords during the migration, you can turn off modification time check. To do this, you need to run Registry Editor, browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AeActivation_[COMPUTER_NAME]\Config\PwdSwitch, create the CheckConflicts string value, and set it to 0. | N/A | |
| During an undo operation, the proxyAddresses and userPrincipalName attribute values are not checked for uniqueness on the source and target. | N/A | |
| If objects that have already been migrated are included in another synchronization job, the migration admin who migrated these objects will no longer be able to undo their migration. | N/A | |
| Intra-forest migration: If after migration with the Reconnect Exchange Mailbox option selected, a new mailbox was created for the source user, then an undo operation for the migrated user will merge the proxyAddresses. | N/A | |
| Undo will not be performed for a migrated object if that object was created on target during migration and has child-objects that are not undone yet. | N/A | |
| In case of Windows 2003 as a target: Undo cannot restore a deleted security domain local group from its tombstone. | N/A | |
| If a new user is created using an existing user as a template, its extensionAttribute15, which contains information about matching, is copied from the template as well. If the directory synchronization is running, this will result in incorrect object matching. The workaround is to clean the extensionAttribute15 for the incorrectly matched user. | N/A | |
| Intra-forest migration: If the target domain is running in mixed mode and the option “Add source membership to corresponding target account” is enabled during migration, target security global groups lose links to source contact objects. | N/A | |
| During migration: The Directory Synchronization Agent cannot migrate OUs with the property ShowInAdvancedViewOnly set to TRUE and if these OUs are migrated with hierarchy. The following errors may appear in migration log: Error 0xe30000a4. Object: [object_name] was not created on target. Its parent has probably been deleted after migration. | N/A | |
| If an object has been moved out of synchronization scope and then some its properties are modified, these changes will not be synchronized by the Directory Synchronization Agent after that object is returned to the synchronization scope. Full resynchronization is needed for these changes to be applied. | N/A | |
| Links are not resolved if a session is run in Test mode. This is by design. Links will be resolved after a session is run in normal mode and they will disappear from Statistics. | N/A | |
| In case of Windows 2003 as source and target: Dynamic objects are migrated as static. This is by design. This behavior can be changed by a custom add-in. | N/A | |
| Links that have been deleted from the source object and that cannot be resolved on target are accumulated in the Unresolved links queue. The workaround is to restart the synchronization job and perform a full resync. | N/A | |
| Even if the creator of a domain pair or task has been revoked the Full Admin role in Delegation Wizard, he or she is still Full Admin for that domain pair or task. The workaround is to delete the domain pair or task to revoke Full Admin rights. | N/A | |
| On Windows XP SP2 with Migration Manager installed: When the Directory Synchronization Agent setup is interrupted by an error or manually by a user, the AUtils.dll gets unregistered and Migration Manager loses connection to ADAM. The following error may also appear in user interface: aeLdapSearch.next failed. The workaround is to register the AUtils.dll by running the following command: regsvr32 AUtils.dll. | N/A | |
| If the second installation of the Directory Synchronization Agent is started from Agent Manager until the previous installation is completed, the Unspecified error occur. Migration Manager does not support parallel Directory Synchronization Agent installations. | N/A | |
| If during migration there was not enough permissions to modify some attributes of the target object, but the object was successfully created, the undo operation will not be available for such objects. The workaround is to skip the attributes to which you do not have enough rights during migration. | N/A | |
|
If the Directory Synchronization Agent was uninstalled, you cannot undo the migration sessions processed by that agent. The following error occurs:
Undo session failed. Cannot find file C:\Program Files\Quest Software\Migration Manager\DSA\CONFIGS\UndoStorage\ |
N/A | |
| Intra-forest migration: If during the Mail Box Reconnect or Undo Mail Box Reconnect operation a user logs on to the mailbox with source account, he or she may not be able to logon to the mailbox with target account after the operation is completed. The workaround is to wait until Exchange replication is completed or try to refresh Exchange cache (for example, by restarting the information store). | N/A | |
| If at least one object in source domain is modified often (for example, twice a minute), the Directory Synchronization status will not be switched from the Initial synchronization to the Delta synchronization. In this case, the agent will never be switched to the sleeping mode as well. | N/A | |
| The following attributes should not be skipped from directory synchronization: DSA service attributes (extensionAttribute15, extensionAttribute14, adminDescription, AdminDisplayName), objectClass, objectGUID, userAccountControl, objectCategory, objectSID, msExchMasterAccountSid, msExchMailboxSecurityDescriptor. Otherwise, you may experience problems during directory synchronization. | N/A | |
| Attribute 'name' should be used to skip instead of skipping the following attributes: distinguishedName, cn, ou. | N/A | |
| If name attribute is skipped, the objects will not be created on target. | N/A | |
| If the Discretionary Access Control List (DACL) of the source user mailbox contains only one Access Control Entry (ACE) with the Associated External Account permission, the Everyone Full Control permission will be set for the target user mailbox during the Reconnect Exchange mailbox operation if the account is enabled during migration. | N/A | |
| If the value of the source object's attribute selected to store matching information is not empty, during migration, if no object can be found in target directory according to information written in the matching attribute, such object will not be migrated. The following error occurs: Source object X that should be matched by the following high priority rule: objectGUID=Y is matched by the following low priority rule: objectClass=user with the target object Z. The workaround is to clean the matching attribute of the source object. | N/A | |
| If the contacts - members of the source group are migrated to target domain A and the group is migrated to target domain B, the target group will not have migrated contacts as members. | N/A | |
| If after starting the synchronization job, before the start operation progress has reached 100% you press Start again, the job status will not be changed to Started and Stop will not be available. The workaround is to wait until the start operation progress has reached 100% and press Start again. This will re-start the synchronization job normally. | N/A | |
| When migrating a small number of objects the links may not be resolved due to the replication latency if the target domain controller is not a Global Catalog. The workaround is to re-migrate the objects. | N/A | |
| In some cases the OUs created during migration in the target domain may not be deleted during undo. | N/A | |
| When you make not critical changes to a stopped synchronization job that do not require full resynchronization, such as modifying the Exclude list, these changes may be accepted as critical. The following message may appear: The changes you have made require full resynchronization of the directories. If you keep the settings delta syncs will not be available. The Start option after that becomes unavailable. | N/A | |
| After critical changes were made to a stopped synchronization job that requires full re-synchronization, such as adding a conflict resolution rule, the following message appears: The changes you have made require full resynchronization of the directories. If you keep the settings delta syncs will not be available, but the Start option may still be available. | N/A | |
| If the RPC connection to the target domain controller failed, the Directory Synchronization Agent's services restart does not help to restore the connection. The workaround is to restart the target domain controller. | N/A | |
| Migration and synchronization: if the object has several unresolved links, the only first link that was not resolved will be displayed in Unresolved queue report. The other unresolved links for that object will not be displayed. | N/A | |
| When migrating hierarchy if there is an OU in the target domain with the same name as the source OU selected for migration, the attempt to create the OU with such name in the target domain will fail. The error will appear in both the Failed and Conflicts queue. | N/A | |
| When undoing a session that was made with the Merge option, the undo completes successfully. However the following errors may appear in the log: Target object CN=... modification failed. LDAP error 0x41. Object Class Violation (00002014: UpdErr: DSID-031A0F8A, problem 6002 (OBJ_CLASS_VIOLATION), data 0). Cannot modify attributes. You can ignore these errors. | N/A | |
| If the number of objects being synchronized is a multiple of the Search page size (100, by default), all objects will be synchronized during the initial synchronization. However, the console will keep showing “Initial synchronization”, although the DSA has finished the initial synchronization session. The workaround is to modify any attribute of any object on the source which would introduce another synchronization and wake up the system. | N/A | |
| When creating a report for the migration session the following error may appear: UnknownError: 'name' is a duplicate attribute name. Line x, position y.; :. The empty xml files may be generated. | N/A | |
| Two-way synchronization: if both matched source and target user have mailboxes, mail redirection may be set in different directions. This depends on what object was synchronized first by a two-way synchronization job. If the target object was synchronized first, the redirection will be set from source to target. If the source object was synchronized first, the redirection will be set from target to source. | N/A | |
| If after a migration a two-way synchronization was set, the service attribute values may not be applied to the source objects. The following messages appear in the log: Target JobID:1 <- FeedBack Handler gave preference to the Target on attribute: extensionAttribute15 ", Target JobID:1 <- FeedBack Handler gave preference to the Target on attribute: extensionAttribute14. | N/A | |
| The Controller service is not switched to the Sleeping state if there are objects in the Conflicts and Failed queues. The Sleep duration interval changes do not change such behavior. | N/A | |
| If the suite launcher was used to install Migration Manager and the first Directory Synchronization Agent, when you install the other Directory Synchronization Agents manually, the ADAM port number and other information is requested but not detected automatically. | N/A | |
| The Ctrl+D shortcut does not work in the following dialog: "The changes you have made require full resynchronization of the directories. If you keep the settings delta syncs will not be available. Do not show this dialog in the future". | N/A | |
| The Do you want to cancel the changes you have made? dialog always appears even if there were no changes made and a wizard was cancelled. | N/A | |
| Migration Wizard Undo Wizard, and Domain Pair Properties: There is no Ctrl+D shortcut in the "Do you want to cancel the changes you have made?" dialog. | N/A | |
| The Add prefix/Add suffix fields in the New Conflict Resolution Rule dialog show values for the previously set rules (not cleared). The workaround is to clear them manually when creating a new conflict resolution rule. | N/A | |
| If the object was moved into the synchronization scope and object create in the opposite directory is allowed, the only single-valued attributes and multi-valued attributes that were changed after the object was moved into the scope will be applied to the target object. To synchronize all attribute values the full re-synchronization is required. | N/A |
|
Feature |
Known Issue |
Change Request |
|
General |
Stored credentials, Execute As properties, linked servers and accounts under which the SQL Server Agent jobs are started are not updated on SQL Server 2005. | ST#22458 |
| The SQL Processing Wizard Undo feature does not work for SQL Server 2005 if the account were migrated using SIDHistory and the SQL server is in the target domain. | ST#21379 | |
| In case of migration without trusts permissions in SQL Server 2005 must be updated after the server running SQL Server 2005 is moved to the target domain. | ST#21382 | |
| If a user is migrated to two different target domains within one migration project the SQL Processing Wizard will update permissions only for one of the target accounts. | N/A | |
| Performance of QMM Console may degrade if migration project contains many resource processing history items. | ST#17716 | |
| Resource Updating Manager does not process Windows Vista scheduled tasks created by another user, if the Run whether user is logged on or not checkbox is selected. | ST#42431 | |
| If the Run whether user is logged on or not checkbox is selected for a Windows Vista scheduled task, Resource Updating Manager will not process the task. To workaround the issue, use the Set Credentials command. | ST#42357 | |
| Resource Updating Manager Retry to process unavailable computers option works only if the console computer and the processed computers are members of domains with trust relationship established. | ST#18412 | |
| An issue may arise with the Resource Updating Manager if the service account that RUM uses to connect to ADAM is not a member of the local computer "builtin\administrators" group. | N/A | |
| Resource Updating Manager settings are not transferred during upgrade from a previous version. | CR#151839 | |
| If Resource Updating Manager was exported to an external MSI file, it cannot be upgraded. To resolve the issue, remove the old version and install the new one. | CR0151839 | |
| Resource Updating Manager's Set credentials feature does not allow your to update file shares and printers connection points in Active Directory. To resolve the issue, grant the administrator permissions to the RUM service account. | N/A | |
| Cleanup does not remove source user permissions in the HKEY_Current_User registry branch. | CR#150246 | |
| The computer-moving process will fail if you specify the source or target domain in the Process additional domain links option. | CR#152344 | |
| After you rename a computer using Resource Updating Manager, you have to restart the computer before it can be moved. | CR#155318 | |
| If during INI file export, you rename the output INI file and the Create setup for this task and the Registry permission management options are enabled, an invalid setup file is created. | CR#163205 | |
| Active Directory Processing Wizard may fail to update group membership if the group and its members reside in different domains and the domain controller is running Windows Server 2003 SP1. The issue can be resolved by installing Microsoft's hotfix KB906381 on the DC. Although it is stated that this issue is resolved in Windows Server 2003 Service Pack 2, there is no solution or hotfix available for Windows Server 2003 Service Pack 2 on release date. Microsoft has confirmed that a problem and the hotfix will be available shortly. If the target DC is running Windows Server 2003 SP2, we recommend to use another target DC. | N/A | |
| Exchange 2000 Processing Wizard: When SIDs that cannot be resolved are being applied, security descriptors will not be correctly updated. You will get warning messages in Exchange System Manager when you try to view the security information of an object with such a security descriptor; however, the permissions will work correctly. | N/A | |
| SMS Processing Wizard, SQL Processing Wizard, and Active Directory Processing Wizard: A Resource Admin can change the direction of processing. | N/A | |
| SMS Processing Wizard: The wizard cannot update the SMS server on the local machine if you specify credentials to connect. | N/A | |
| Trust Migration Wizard: If the source domain has a realm trust established, the wizard cannot migrate such trusts from that source domain. | N/A | |
| Trust Migration Wizard: The wizard cannot migrate trusts if the DNS domain name is specified. | N/A | |
| SMS Processing Wizard and SMS 2003: If a migrated user has the Instance security right granted to a Report or a Software metering rule in SMS, the permissions will not be processed for that user. | N/A | |
| Active Directory Processing Wizard: The msExchMasterAccountSid attribute may not be processed correctly if the DNS names of the source and target domain cannot be resolved. | N/A | |
| SQL Processing Wizard: The wizard cannot process the SQL server used to store the Migration Manager for Exchange configuration database. | N/A | |
| Active Directory Processing Wizard: If a setup package for the delegated task is created, and then the task is installed and completed, there is no information about the processed servers in history. | N/A | |
| Exchange 2000 Processing Wizard: If the mailbox contains a large number of messages (more than 10000), the wizard may stop processing the mailbox due to the timeout period. | N/A | |
| Exchange 2000 Processing Wizard and Microsoft Exchange Servers 2000 with SP1 and SP2: Client permissions set to subfolders (such as Calendar and Inbox) in a mailbox are not processed. | N/A | |
| Resource Updating Manager: When Resource Updating Manager is started for the first time and if computer accounts were added to the computer list manually, then after 'Refresh' is performed, the following error may occur: "Error # 3022 The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again." In this case, cancel the Refresh and perform the 'Refresh unknown computers' operation. | N/A | |
| Resource Updating Manager: If Tools -> Options has never been opened before starting resource update from Resource Updating Manager, the RUMService will not be able to connect to ADAM. | N/A | |
| Exchange 2000 Processing Wizard: When messages in public folders are processed, the read/unread status of the messages is lost. All messages will be marked as unread after processing. | N/A | |
| Exchange 2000 Processing Wizard: Messages posted using Outlook Web Access by users without a mailbox are not processed. | N/A | |
| Exchange 2000 Processing Wizard: Cannot process a mailbox that has been moved to another store and that has not been logged on to by a user yet. The Unauthorized (401) error occurs. | N/A | |
| Exchange 2000 Processing Wizard: Cannot process mailbox folders whose names contain unsupported symbols (such as the following: < / > \ '). | N/A | |
| Exchange 2000 Processing Wizard: The wizard may fail to process mailbox permissions if a locale other than English is installed on the Migration Manager console. | N/A | |
| Exchange 2000 Processing Wizard and Microsoft Exchange Server 2003: Not all messages may be processed in the additional mailbox folder, if the number of messages in the folder is big. This is due to the limitation on the number of objects that can be opened in one MAPI session. The limit can be changed by editing the key in system registry of the Exchange server. For more information, refer to Microsoft Knowledge Base article: http://support.microsoft.com/?kbid=830829. | N/A | |
| If both, Domain Migration Wizard and Quest Migration Manager are installed on one computer, after the Quest Migration Manager is uninstalled, the Exchange 2000 Processing wizard that is part of the Domain Migration Wizard does not work any longer | N/A |
|
Feature |
Known Issue |
Change Request |
|
SharePoint Processing |
If a target account already has permissions on SharePoint server before you run the wizard, the account will not be processed by the SharePoint Processing Wizard. | ST#43164 |
| Accounts listed on the Shared Services Administration page are not processed. | ST#42976 | |
| The SharePoint Administrator Group Account in Microsoft SharePoint 2003 is not processed. | ST#47968 | |
| Active Directory groups are not processed. | ST#42464 |
| General | If the mailbox message body contains links to corrupted attachments, the mapi_e_corrupt_data error is written to the log file and this mailbox may not be switched. | N/A |
| Single-instance messages are migrated as normal messages. | N/A | |
| All Exchange 200x servers must support all languages that are used in the source or target mailboxes or public folders. | N/A | |
| It is recommended that you enable circular logging on Exchange 200x servers to avoid growth of the transaction logs because of the Migration Manager agents working on the server. | N/A | |
| Migration Manager agents may not work correctly if mailbox messages, folders, or properties are modified by the user while the agent is processing the mailbox. | N/A | |
| If the account used to install Migration Manager agents does not have administrative rights on the remote server, the agent components may not be correctly registered. This will cause agent processes to hang on the server. | N/A | |
| If the legacyExchangeDN attribute contains both the '@' character and the decimal point, Quest Migration Manager may fail to process or switch such mailboxes. Customers experiencing the issue should contact Quest Support. | N/A | |
| Hotfixes | The Hotfix Installation Wizard will not install the Shared Components hotfix while the synchronization job is set up if the Shared Components has already been installed before. | N/A |
| Clusters | Migration Manager for Exchange supports Windows 2000/2003 cluster servers only if no more than one Exchange Virtual Server is running on a single cluster node. Migration Manager detects such systems and configures agent services for automatic failover together with the Exchange services. | N/A |
Migration Manager does not fully support all types of Exchange 2007 Continuous Replication:
|
ST#48071 | |
| License counters may double on cluster Exchange servers. | ST#46295 | |
| If access to the cluster nodes is denied while the server properties are being modified, the Aelita Exchange Migration Wizard folder will be created on the local disk, not on the shared drive. | N/A | |
| When installing Migration Manager agents on the cluster, the default path to the tracking database should point to the Exchange cluster shared drive that is a member of the Exchange Virtual Server group (that is now the default behavior). If the tracking databases are located on the local disk, they will not be moved to another cluster node when necessary. | N/A | |
| When the Migration Manager 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. | N/A | |
| The Migration Manager agents should not be installed on a cluster if any of the cluster’s nodes is down. | N/A | |
| The agents cannot process mailboxes if Virtual Exchange that holds the public folder store is down. | N/A | |
| Migration Manager For Exchange Console | After you upgrade from Quest Migration Manager 7.x to 8.0, it is strongly recommended to refresh information on one Exchange server from each registered organization. | ST#36077 |
| The Mailbox Properties dialog is not displayed, if Associated Domain Controller of the user’s Home Exchange server is not in the same domain, as the user. | ST#36077 | |
| If an object’s distinguished name is longer than 450 characters, the object will not be displayed in Migration Manager and an error message will be displayed when adding or refreshing a server that hosts the object. This is because the SQL Server allows no more than 450 symbols for an indexed field. | N/A | |
| There might be resource leaks if Migration Manager is started on a remote server via terminal session. | N/A | |
| A mailbox with a Display Name value of more than 100 symbols cannot be specified as the Administrator Mailbox. | N/A | |
| If the mailbox switch was done and undone several times manually, both source and target mailboxes may contain some duplicated messages. | N/A | |
| Migration 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. | N/A | |
| If you change the password for an account used by Migration Manager agents, Migration Manager will not generate an error as expected but will continuously try to start the agents. | N/A | |
| If several Migration Manager consoles are using the same SQL database, it is recommended to refresh SQL after any action (such as deleting a job, deleting a collection, or committing changes) has been performed on the synchronization jobs. To refresh the SQL server, right-click the root node ‘Exchange Migration Project’ and select the Refresh command from the shortcut menu. | N/A | |
| For the entire Exchange organization, you can set up only one public folder job having the ‘All Public Folders’ folder as a synchronization root. | N/A | |
| The public folders with a backslash (\) character in the folder name are not displayed in the console. You cannot select such folders as synchronization roots and exclude from synchronization. | N/A | |
| After a hotfix installation, the agents installed on a cluster server are not started automatically and should be started manually. | N/A | |
| A hotfix should be installed on all Virtual Exchange Servers running on a cluster before starting the agents. | N/A | |
| The path to Aelita Shared folder is saved in the agent's configuration file. When a Virtual Exchange Server is moved to another cluster node and shared components on that node are installed on a different drive, the path to Aelita Shared folder will be invalid and the agent will not work. | N/A | |
| If the server hosting the Calendar or Free/Busy Synchronization Agent cannot be found in the configuration database while applying the default settings to the agents, no settings will be applied to any agent. Do not select the options to apply settings to Calendar and Free/Busy agents if the servers hosting these agents are not present in the database. | N/A | |
| Statistics Collection Agent | The Statistics Collection Agent cleans up statistics SQL tables only for the Migration Manager agents enabled for statistics collection. | ST#35950 |
| The Migration Manager console displays statistics with a slight delay. | N/A | |
| Migration Manager Statistics supports only SQL authentication. It does not support Windows authentication. | N/A | |
| An object already synchronized within one synchronization collection and then processed within another collection will be displayed twice in the Migration Manager Statistics reports. | N/A | |
| If the target administrative group is selected for free/busy synchronization, but the ‘Search for new free/busy messages in the target organization’ check box is not selected (that is, the existing target free/busy messages will be synchronized, but the new target free/busy messages will not be created in the source administrative group), then the ‘Matched’ field value for this administrative group will be displayed as “0” in the Migration Manager Statistics reports. | N/A | |
| Do not install the Statistics Collection Agent on Exchange servers. The Statistics Collection Agent does not collect statistics data from the servers where it is installed. | N/A | |
| If Windows authentication is used by the Migration Manager console computer, the account under which the Statistics Collection Agent is running should have appropriate permissions for SQL server. | N/A | |
| If a mailbox was processed within a Remote Users collection, the Migration Manager Statistics reports will show its LegacyExchangeDN instead of its Display Name in the ‘Display Name’ field. | N/A | |
| If a mailbox was processed within a regular collection, the Migration Manager Statistics reports may show its LegacyExchangeDN instead of its Display Name in the ‘Display Name’ field. | N/A | |
| Any public folders once processed within the public folder collection and then excluded from synchronization will not be excluded from the Migration Manager Statistics reports. | N/A | |
| When the synchronization is in progress the target server counter values may exceed the source server counter values. | N/A | |
| If the total size of the folder messages is less than 1 KB, in the Migration Manager Statistics reports the total size of the folder will be displayed as 0. | N/A | |
| If the ‘Copy only messages not older than’ check box is selected in the Mail Source Agent Properties and the Public Folder Source Agent Properties, Migration Manager Statistics will calculate the percentage of synchronized messages as the relation of number of copied messages to the total number of messages. It may seem that not all messages were synchronized. However, actually only messages not older than the specified number of days were synchronized and the task has been completed correctly. | N/A | |
| If the Statistics Collection Agent and any Migration Manager agent are working simultaneously in the same folder, the Statistics Collection Agent will log the following error: Error -2147217900 [Microsoft][ODBC SQL Server Driver][SQL Server]INSERT statement conflicted with COLUMN FOREIGN KEY constraint 'FK_STATProcessedWorkflow3_STATProcessedSession3'. As a result, the Statistics Collection Agent will not collect statistics data during the session in which the error is logged. The statistics data will be collected during the next session. | N/A | |
| For mailboxes added to a mailbox collection implicitly (for example, via a distribution list), the Refresh Switch Status operation from the console will not update information about the switch status in the statistics database. Therefore, information about the switch status displayed in Project Manager and Statistics portal may differ until the Statistics Collection Agent updates the statistics database. | N/A | |
| Mailbox, calendar, and public folder synchronization | ||
| General | ||
| Shortcuts in attached messages may not work after the migration. | ST#47705 | |
| The agents do not write statistics, if the Do not clear the agent's statistics option is enabled. Also, you may get the CAgentStat::ReleaseSessionEx InternalError 91 Object variable or With block variable not set error in any agent log. To workaround the issue, specify a long period of time (a year, for example) in the Keep statistics for the last: ... days option. | ST#47850 | |
| If the recipient table of a message contains contacts with double-byte characters, Aliases of these contacts will be shown instead of display names. | ST#41020 | |
|
License may be issued twice for the same mailbox or calendar. The issue may
occur in the following cases: - If you move a mailbox in the source environment between servers. - If the mailbox was processed by several Calendar Synchronization Agents (CSA) installed on different servers. - If the mailbox is hosted by Exchange 2000 or 2003 clustered server and a failover occurred during migration. - If the mailbox synchronized by CSA is hosted on the target Exchange 2007 server where Cluster continuous replication is used, and a failover occurred during migration. |
ST#47164 | |
| Migration Manager does not support Exchange servers where Microsoft Outlook is installed. For more information, see the Microsoft KB article available at http://support.microsoft.com/kb/266418. | N/A | |
| If the Administrator mailbox specified for the public folder synchronization job is changed during the course of synchronization, the public folder synchronization agents will not work properly. | N/A | |
| The Administrator mailboxes specified for the public folder synchronization jobs should not be added to the collection processed by the mail synchronization agents. | N/A | |
| Localized symbols in the folder names created via Outlook Web Access will not be correctly copied to the target servers. | N/A | |
| Migration Manager 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. | N/A | |
| Exchange migration can be started only after the mailbox-enabled target users have been created on the target server. That is, the target Global Address List should contain the valid objects by the time Exchange migration is started. | N/A | |
| Query-Based Distribution Groups cannot be processed within mailbox and calendar collections. | N/A | |
| If a Windows NT account has been migrated to the target domain with SIDHistory preserved, and this user logs on to the source mailbox using SIDHistory and creates a message in the source mailbox, the user’s rights for this message will be lost in both the source mailbox (before switch) and the target mailbox (after switch). | N/A | |
| If some messages became conflicting as a result of simultaneous message modification in the same public information store by two users, these conflicting messages may be not copied to the target server, the Public Folder Source Agent, or the Mail Source Agent logging the MAPI_E_CORRUPT_DATA error. | N/A | |
| Message and folder deletions will always prevail over other modifications. For example, even if the messages or folders corresponding to the deleted source messages or folders have been modified, they will be deleted by the agents. | N/A | |
| If during the time interval after the target mailbox recreation (performed with the mailboxes of the Remote Users Collections) and before the source mailbox content copying the MAPI logon occurs, the default mailbox folders will be duplicated. | N/A | |
| If the Hide membership Exchange task was performed on a group and that group is added to a mailbox or calendar collection, none of this group members will be synchronized within the collection. The members of groups having the ’Hide group from Exchange Address Lists' check box selected will not be processed either. | N/A | |
| 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 mailbox and calendar collection. For mailbox creation, you should select only that private information store which is located in the administrative group where the existing target mailbox is homed. If you select the store located in another administrative group for mailbox creation, you will not be able to move the mailbox to its store until you switch your organization to native mode. | N/A | |
| Quest Migration Manager Switch Notification does not support Unicode format in the From and Subject fields. | N/A | |
| Mailboxes having a LegacyExchangeDN that exceeds 255 symbols cannot be processed. | N/A | |
| If a message attachment is corrupted the message may be not copied to the target server or a message may be copied without attachment. If one of several attachments is corrupted, the mail agent will log an error, though the message will be copied along with all valid attachments. | N/A | |
| If nesting of folders exceeds 49 levels, the permissions for the 50th and later nested folders will not be synchronized. | N/A | |
|
The following properties of the target mailbox will contain the source mailbox
Display Name: - PR_ACCOUNT_NAME - PR_ORIGINAL_SENDER_NAME - PR_ORIGINAL_SENT_REPRESENTING_NAME - PR_ORIGINAL_DISPLAY_TO - PR_ORIGINAL_DISPLAY_CC |
N/A | |
|
The following properties will not be synchronized by the agents: - The 'Any form' 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 |
N/A | |
| If a synchronization root folder is specified as a ‘Folder’ in the ‘Folder groups’ of the Activities tab of the folder properties it will not appear in the target folder Properties dialog box. | N/A | |
| The agents working on Exchange 200x server may hang up if the DC associated with this server becomes unavailable. | N/A | |
| If a mailbox is hidden from the Global Address List, the Migration Manager agents will not synchronize this mailbox (including Calendar folder and free/busy message) and permissions granted to this mailbox. | N/A | |
| The Mail and Calendar Agents cannot log on to a mailbox if the name of the information store that homes the mailbox contains any of the following characters: # + < > " , | N/A | |
| If Access Control List of a source folder is full, you get the MAPI_E_TOO_BIG error and the subfolders are not migrated. The issue applies to Mail Target Agent and Public Folder Target Agent. | ST#32485 | |
| PST files with size exceeding the PST file contents size limit value may still be migrated, since Migration Manager checks the currently processed file size only after each 500 items. | ST#36497 | |
|
Mailbox Synchronization |
||
| The Mail Source Agent switch may fail after encountering a corrupted message. To workaround the issue, set the Switch a mailbox if not more then <…> errors occurred during migration option value to more than 0. | ST#28063, ST#30978 | |
| If a mailbox is processed by the agents in a job, and then you add the mailbox to another job with a different target server, Mail Target Agent may experience the following error when logging in to the mailbox: Your profile is not configured. - MAPI_E_UNCONFIGURED. The issue is resolved automatically after several unsuccessful logon attempts. | ST#32937 | |
| The agent may fail to create the Schedule folder on the target server with the MAPI_E_NO_SUPPORT error. This may be caused by excessive size of the 0x61AF0102 property value. If you encounter this issue, contact Quest Support. | ST#33194 | |
| Mail agents may not work correctly if the target Exchange 200x mailbox is modified before the mailbox switch. | N/A | |
| Migration Manager agents do not update some links in copied messages, tasks, notes, and calendar and journal entries. | N/A | |
| A mailbox will be switched even if there are conflicting 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. | N/A | |
| The Mail Target Agent cannot find a mailbox during a period of time right after the mailbox is moved to another mailbox store. This is how Exchange 200x works. | N/A | |
| If the source mailbox Draft folder contains non-dated messages, the corresponding target messages will all have the same date of target message creation. | N/A | |
| During mailbox synchronization, if the size limit for the target mailbox is reached, the mailbox is incorrectly marked as switched. The workaround is to set the target mailbox size limit not less than the size limit of the source mailbox or set it after migration is completed. | N/A | |
| The Mail Source Agent cannot detect whether items in the Deleted folder were removed using Microsoft Outlook Web Access. This is an issue with Outlook Web Access. | N/A | |
|
Public Folder Synchronization |
||
| Mail-enabled root public folders become mail-disabled after the synchronization. | ST#36476 | |
| Folder hierarchy synchronization may fail, if more than 40 rules are assigned to one of the folders and folder size exceeds 100KB. | ST#31421 | |
| Irrespective of the type of the source synchronization root folder, the folder is copied to the target server as an IPF.Note type. | ST#36206 | |
| The Internet News Groups folders may be not synchronized or synchronized with errors. | N/A | |
| The use of the ‘Aelita EMW Recycle Bin’ folder is strongly recommended in order that no public folders deleted accidentally are lost during synchronization. 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 agents automatically create this folder, but it is not replicated to other servers. | N/A | |
| The Exchange account under which the Public Folder Synchronization agents are running should be mail-enabled and have a mailbox in the same Exchange 200x organization. | N/A | |
| The read/unread status of public folder messages will not be synchronized. | N/A | |
| 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 the Migration Manager agents. The user will have to configure the views for each public folder again after mailbox switch. | N/A | |
| Conflict messages may be created if the public folders synchronized by Migration Manager agents are replicated between servers. | N/A | |
| 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. | N/A | |
| Some of public folders directory and admin attributes, such as the folder size limit, are not synchronized. | N/A | |
| The ‘Issue warning at (KB)’ and ‘Age limit for replicas (days)’ properties specified in the Limits tab of the public folder Properties dialog box will not be synchronized. | N/A | |
| 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. | N/A | |
| 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. | N/A | |
| 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 on the target only. | N/A | |
| During two-way synchronization, if some messages or folders 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. | N/A | |
| 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. | N/A | |
| If a public folder being synchronized by Migration Manager agents 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. | N/A | |
| The Administrator mailbox selected for the public folder synchronization job should be homed on the same server where the public information store is located. This public information store should be associated with the private information store where the Administrator mailbox resides. The setting can be verified in the properties of the Private Information Store. | N/A | |
| If the synchronization root folder is created by the public folder agents, there must be a local replica of the folder's parent folder on the agent's server. Otherwise the folder created by the agents will be invalid and may be inaccessible. | N/A | |
| If the Public Folders Target Agent performs several attempts to process the PST file (the number of attempts is specified in the agent's Properties dialog box), and during this time a new PST file has been 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. | N/A | |
| If an Administrator mailbox selected for the public folder job is changed, the agents will perform full resynchronization of all collections added to the public folder job. | N/A | |
| If the ‘Keep deleted items for (days)…’ check box and/or ‘Do not permanently delete items until the store has been backup’ check box are selected for the target public information store, the messages deleted on the source server will be put to the SoftDeletes container of the target public folder and will be kept there for the time interval specified in the check box or until the store has been backed up. | N/A | |
| If a full resynchronization was performed, the new permissions applied to the public folder which is a synchronization root will not be synchronized back to the source synchronization root folder. | N/A | |
| Source and target mail-enabled public folders will have different e-mail addresses. | N/A | |
| If the ‘Hide from address book’ check box is cleared during either the first synchronization or a permissions full resynchronization of the mail-enabled public folders, the following warning will be logged by the agent: ‘Warning: 2147024891 You do not have sufficient permission to perform this operation on this object. - MAPI_E_NO_ACCESS’. | N/A | |
| If a source public folder has no local replica on the server involved in synchronization but is included in the collection, its deletion will be synchronized even though the folder cannot be synchronized. That is, the corresponding target public folder will be deleted by the agent. | N/A | |
| If a 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. | N/A | |
| When a new synchronization root folder is copied to the target server, the agent’s account will be added to the folder permissions. | N/A | |
| If within one parent folder the source public folder is renamed to the public folder name already existing on the target server, this folder renaming will not be synchronized. | N/A | |
| It is not recommended to set two-way public folder rule synchronization. It is recommended to select the ‘Copy rules’ check box for the Public Folder Source Agent running on the source server | ||