Is there a solution for the Common Support issues in Quest Migration Manager for Active Directory and Exchange?

This guide explains common support issues when migrating Active Directory and Exchange and identifies knowledge base solutions which address theses issues.

Purpose

The purpose of this document is to assist you, the customer, with your migration by bring to your attention some of the common support issues that are encountered during a migration.  To assist with this, numerous Knowledge Base solutions will be identified to assist you with areas of the migration which provide a more detailed explanation of how agents and the console work.

It is also very important that you review the Release Note which can be found in the software folder.

This document used in conjunction with the Quick Start Guide will greatly ease many of the problems you may experience during the migration.

 
Migration Manager for AD Issues

Service Account permissions

One of the biggest issues with the migration of Active Directory objects is the correct permissions of the Service Account in the Source and Target organizations.

Solution SOL38171 - How to set permissions for Quest service accounts - https://support.quest.com/SUPPORT/index?page=solution&id=SOL38171

AD

The following solutions address numerous issue that arise while migrating and synchronizing user accounts.  

General Issues

The following solutions address general issues and questions.

Solution SOL12001 - Quest Migration Manager for Active Directory common issues and suggestions for troubleshooting. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL12001

Solution SOL31349 - How many projects to have - what is the best practice? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL31349

Solution SOL17458 - What considerations should be made when determining where to place the Migration Manager console? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL17458

Solution SOL14446 - How do I move Project to different PC? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL14446

Solution SOL15174 - How to focus a migration session or synchronization to use a computer running QMM DSA.- https://support.quest.com/SUPPORT/index?page=solution&id=SOL15174

Solution SOL25286 - Where is the DSA log file located? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL25286

Solution SOL31926 - Recommendations on using single DSA agent with multiple domain pairs. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL31926

Password complexity

Password complexity is an issue which is commonly experienced.  In Windows 2003 password complexity is enabled by default.  If password complexity has not been implemented in the source then there will be issues in the target when the passwords are migrated.  Here are the settings on how to reduce the password complexity.

1. Open Active Directory Users and Computers management console.
2. Right-click the name of the domain, and then click Properties.
3. Click the Group Policy tab, click Default Domain Policy, and then click Edit. The Group Policy Editor opens.
4. Expand Computer Configuration, click Windows Settings, click Security Settings, click Account Policies, and then click Password Policy.

a. Enforce password history needs to be set to zero (24 is the default in 2003)
b. Minimum password age needs to be set to zero (1 is the default):
c. Minimum password length needs to be set to zero (7 is the default in 2003)
d. Password must meet complexity requirements needs to be set to Disabled (click Apply), and  then undefined (unchecked and click OK)

5. Restart

Migration

The following solutions address some common issues and questions which arise during the migration of AD user accounts.

Solution SOL35169 - When undoing a migration does it give back the licenses? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL35169

Solution SOL23826 - Windows Management Migration Solutions Discussion Forum - https://support.quest.com/SUPPORT/index?page=solution&id=SOL23826

Solution SOL34180 - Error 0xe3000001. License violation error is displayed when attempting a Migration Session - https://support.quest.com/SUPPORT/index?page=solution&id=SOL34180

Solution SOL36277 - "License Violation Error" occurs when migrating users in QMM 8.0, even though the license count has not been exceeded. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL36277

Solution SOL36986 - Installing a new temporary or full license does not reset the license counter back to zero - https://support.quest.com/SUPPORT/index?page=solution&id=SOL36986

Solution SOL28070 - What is the difference between the license for migration and synchronization? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL28070

Resource Update Manager (RUM)

The RUM is used to process the user’s profile, ACLs of files and numerous other items on a PC (local or remote).  The processing and moving of the PC can be a complicated matter.

Solution SOL13550 - Troubleshooting Suggestions and Recommendations for Computer Migration using RUM (Resource Update Manager) - https://support.quest.com/SUPPORT/index?page=solution&id=SOL13550

Solution SOL14050 - Troubleshooting Issues with User Profiles after Resources have been Updated - New Profile Created Even though Resources were Updated - https://support.quest.com/SUPPORT/index?page=solution&id=SOL14050

Solution SOL12001 - Quest Migration Manager for Active Directory common issues and suggestions for troubleshooting. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL12001

Solution SOL16079 - Resource Updating Manager (RUM) Limitations and Best Practices when Processing and Migrating Computers - https://support.quest.com/SUPPORT/index?page=solution&id=SOL16079

Solution SOL13775 - HOW TO: Step by Step Guide for Reverting Computer Profile Updates - https://support.quest.com/SUPPORT/index?page=solution&id=SOL13775

Solution SOL37936 - How to enable extended logging for Vmover in DMW/QMM when processing resources? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL37936

Solution SOL15336 - How to install a second instance of Resource Updating Manager (RUM) - https://support.quest.com/SUPPORT/index?page=solution&id=SOL15336

Solution SOL15862 - How to Process Resources Locally on a Workstation or Server - https://support.quest.com/SUPPORT/index?page=solution&id=SOL15862

Solution SOL20808 - Processing resources and moving computers from command line - https://support.quest.com/SUPPORT/index?page=solution&id=SOL20808

Solution SOL15301 - How to create and populate an INI file for command line processing - https://support.quest.com/SUPPORT/index?page=solution&id=SOL15301

Solution SOL15924 - Format of an import file used to import computers into RUM. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL15924

Solution SOL17006 - How to use VMover for processing roaming profiles on large file servers. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL17006

Solution SOL23271 - FixProf utility and "Update profile on next restart if failed" option or how to avoid problem with locked user profiles during resource updating. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL23271

Solution SOL35337 - Update Resources or Migrate Computers - which step should be done first - https://support.quest.com/SUPPORT/index?page=solution&id=SOL35337

Solution SOL40081 - Resource Update Manager (RUM) fails to process machine and doesn't show any errors or anything in vmtotal.log except the time and date. Where Can I find out what's wrong? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL40081
 
Migration Manager for Exchange Issues

Service Account permissions

One of the biggest issues with the migration of Exchange mailboxes is the correct permissions of the Service Account in the Source and Target organizations.

Solution SOL38171 - How to set permissions for Quest service accounts - https://support.quest.com/SUPPORT/index?page=solution&id=SOL38171

Clusters

The installation of the agents on a cluster can be a complex issue.

Solution SOL41529 - Can Migration Manager 8.1 agents be installed on Exchange 2007 clusters and instances? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL41529

Solution SOL24119 - Why multiple instances of Quest agents are showing in the services list of every cluster node? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL24119

Free/Busy

Solution SOL42144 - Some important considerations when synchronizing F/B (Free/Busy) information into Exchange 2007/Outlook 2007 target organization - https://support.quest.com/SUPPORT/index?page=solution&id=SOL42144

Exchange 2007 Issues

Solution SOL34855 - Mail, Calendar or PF agents are experiencing issues while working with Exchange 2007 target server. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL34855

Solution SOL44408 - How do I delete and purge mailboxes from Exchange 2007? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL44408

Exchange 2007 running on Windows 2008

Solution SOL43479 - Does Quest Migration Manager for Exchange support migrating to Exchange 2007 when it is installed upon a Windows 2008 Server? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL43479

EMWProf

The Client Profile Updating Utility (EMWProf) allows you to update these profiles automatically and transparently. The utility is used to update end user Microsoft Outlook profiles from the source to the target Exchange server once the user mailbox is migrated and switched by the Mail Source Agent or manually.

Solution SOL40135 - After using EMWProf to process an Outlook 2007 profile the user cannot see the GAL - https://support.quest.com/SUPPORT/index?page=solution&id=SOL40135

Solution SOL22429 - Troubleshooting Suggestions for EMWProf - how to enable extended logging - https://support.quest.com/SUPPORT/index?page=solution&id=SOL22429

Calendar

The following solutions address some common issues and questions which arise during calendar migration. 

Solution SOL42312 - Source Calendars may appear as normal messages/"posts", "Calendar1" folder may be present - https://support.quest.com/SUPPORT/index?page=solution&id=SOL42312

Solution SOL28918 - Can a one-way Calendar Synchronization job be converted to a two-way? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL28918

Solution SOL34612 - Is Calendar synchronization also copying Free/Busy information? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL34612

Solution SOL43372 - In some cases after calendar synchronization, the mailbox will contain duplicate calendar folders, and/or calendar entries may appear as messages. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL43372

Solution SOL22596 - Mail or Calendar agent logs an error: CSession::Logon Error -2147221231 The information store could not be opened. - MAPI_E_LOGON_FAILED (MAPI 1.0) Low level error: 0x0 File: 'aeWrapHelpers.h' Line: '264' - https://support.quest.com/SUPPORT/index?page=solution&id=SOL22596

Mailboxes

Mailbox Switching Issues

Switching is done by the MSA.  Using automatic switching you can specified mailboxes to be switched as conditions are met. For example, you can specify to switch unsynchronized mail with certain size or switch mailboxes with no more than specified number of errors. Automatic mail switching is done by MSA when the mailbox is in sync based on the conditions set.

The MSA and MTA do not communicate.  Therefore the MSA does not know if the mail has been created in the target.  If the two agents communicated, then the mail migration process would place considerable load on the network and agents.
 
This can cause a problem if the MTA has not updated the target mailboxes.  There are many reasons for this.  They can range from; target agent not started, or malfunctioning; source mailboxes, and target user accounts not properly matched by the directory synchronization agent; target server processing slow due to hardware restrictions, improper settings, etc.

When the MSA switches the mailbox and the users log in to the target mailbox, the users will not have their mail.

If you look at the target server using the Service File Viewer, in the resource kit, you will probably see a large number of .PRV files or a large number of archived files.  This is the PST files that had a problem in the target.  These problems would be recorded in you EMWMTA.log file and you will find solutions to these problems on out support site.

To help solve this problem it is recommend that two collections are created called, "synced" and "switched" (or similar names).  Place mailboxes into the "synced" collection and make sure they are synced before moving them to the "switched" collection.  This way you can be sure that any problems with the mailboxes are resolved before switching them.

Solution SOL10368 - How to Handle Target Mailboxes Existing prior to Exchange Migration using QMM (Quest Migration Manager) - https://support.quest.com/SUPPORT/index?page=solution&id=SOL10368

Solution SOL22845 - How to do a manual mailbox switch on an individual mailbox that was added to collection via DL (Distribution List) membership? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL22845

Solution SOL17329 - A switched mailbox is empty or does not contain all the synchronized mail immediately after user logs into his mailbox on the target. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL17329

Solution SOL25059 - Blackberry devices stop working after the mailbox is switched and the profiles is updated - https://support.quest.com/SUPPORT/index?page=solution&id=SOL25059

Solution SOL15440 - Moving Target Mailboxes in the Middle of Mailbox Sync Job - https://support.quest.com/SUPPORT/index?page=solution&id=SOL15440

Solution SOL27905 - EMWProf fails because some mailboxes have improper permissions set - user does not have permissions to his own mailbox - https://support.quest.com/SUPPORT/index?page=solution&id=SOL27905

Solution SOL14954 - When synchronizing a mailbox there is a discrepancy in the amount of items reported. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL14954

Solution SOL26466 - How does the mailbox switch work in Quest Migration Manager for Exchange? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL26466

Solution SOL31091 - How to update resource mailboxes? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL31091

Solution SOL15792 - Is it possible to increase the size of the .pst file that is created by the mail source agent? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL15792

Solution SOL17426 - "MAPI_E_FAILONEPROVDER" error received in Mail Source, Mail Target or Calendar Agent log files. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL17426

Solution SOL25169 - What is the right procedure to reinstall a Migration Manager for Exchange agent? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL25169

Solution SOL39870 - How to watch the log files in QMM Exchange -  https://support.quest.com/SUPPORT/index?page=solution&id=SOL39870

Solution SOL25710 - Some of the mailboxes are not being switched even when the synchronization is configured to switch them automatically - https://support.quest.com/SUPPORT/index?page=solution&id=SOL25710

Solution SOL32004 - Mail Target Agent occasionally stops processing PRV files in the target queue. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL32004

Solution SOL19979 - Unable to commit changes to synchronization job.- https://support.quest.com/SUPPORT/index?page=solution&id=SOL19979
 
Transmission Agent

The Transmission Agent can be though of as the DOS utility XCOPY.  It’s purpose is to move the PRV and PUB files from the source to the target server.  The following solutions address some of the common issues that occur during the agents operation.

Solution SOL27447 - Mail Transmission Agent running on the source server shows warning: 'NTA::Application::CopyFilesFromFolder Warning 53 The network path was not found. Path:\\Target_server_name\QMMEX$Target_server_name$, User:domain\service_account' - https://support.quest.com/SUPPORT/index?page=solution&id=SOL27447

Solution SOL23128 - Error: "NTA::Application::EnumFolders Error 522 There are no servers in the Servers table. Agent will be terminated." - https://support.quest.com/SUPPORT/index?page=solution&id=SOL23128

Solution SOL23956 - Mail Transmission Agent is not moving PRV/PUB files and -2147467259 errors are reported in the agent log file. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL23956

Public Folders

The following solutions address some of the common issues and questions which arise during public folder migration.

IMPORTANT: Do NOT delete any public folder data in the target. This will cause tombstone issues that cannot be resolve.

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.

Solution SOL31539 - When syncing public folders, the folder type is not preserved on the target. Items appear as posts. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL31539

Solution SOL12080 - Public Folder Synch failing - "Error -2147024891 aeMAPIFolder::SetDirectorySKey failed <folder name> You do not have sufficient permission to perform this operation on this object - MAPI_E_NO_ACCESS" - https://support.quest.com/SUPPORT/index?page=solution&id=SOL12080

Solution SOL44851 - Migration to Exchange 2007 - what is the requirement regarding Public Folders? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL44851

Solution SOL43476 - What is the procedure for deleting a public folder in the target? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL43476

Solution SOL27902 - Will the Public Folders not having local replicas on the source server selected for the Public Folders Synchronization Job be synchronized to the target server? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL27902

Solution SOL14266 - Important reasons for Using Aelita Recycle Bin Public Folder - https://support.quest.com/SUPPORT/index?page=solution&id=SOL14266

Solution SOL16980 - During the public folder synchronization, target permissions or folders are missing - https://support.quest.com/SUPPORT/index?page=solution&id=SOL16980

Solution SOL21385 - How can I synchronize the email address of the Mail Enabled Public Folders during Public Folder synchronization? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL21385

Solution SOL34607 - Cannot select the Administrator Mailbox for the Target when creating a Public Folder or Calendar Sync Job - https://support.quest.com/SUPPORT/index?page=solution&id=SOL34607

Solution SOL21481 - General recommendations on setting memory limit for Quest Mail and Public Folder Agents. - https://support.quest.com/SUPPORT/index?page=solution&id=SOL21481

Solution SOL9621 - How to handle the deletion of already synchronized public folders - https://support.quest.com/SUPPORT/index?page=solution&id=SOL9621

PFDavAdmin tool

PFDavAdmin means Public Folder Distributed Authoring and Versioning Administrator and is used perform various management tasks related to public folders and mailboxes. Use this tool to confirm that a public folder has been deleted.

It can be downloaded from:

Microsoft Exchange Server Public Folder DAV-based Administration Tool - http://www.microsoft.com/downloads/details.aspx?FamilyID=635be792-d8ad-49e3-ada4-e2422c0ab424&DisplayLang=en

or

just run a search on MS download site for PFDavAdmin.

Run it on the target server (it does not require an installation), just specify the server name and credentials, select a PF on left side, right mouse - select "show deleted subfolders" and you will see the deleted PF's.

If the folders have been deleted you will have to use the Aelita Recycle Bin to work around this issue.