I changed the order slightly and dropped steps not directly related to Quest processed.
Because you are using a phased migration approach, permissions in AD and EX change be changed post step 3/4 and prior to step 7. The "Replace" mode of step 7 combined with sid history address this gap.
Thanks Jeff. I do have a follow up question regarding the source objects if you wouldn't mind reviewing? The source user objects have various "legacy" attributes from a previous non qmm migration (native mailbox move) For example the following are present: mail mailnickname msExchMailboxGuid Various other msExch* attributes proxyAdresses targetAddress The values in these attributes are no longer relevant and could be incorrect therefore we would like to skip them during the migration sessions. We plan to perform the migration over a short period so was planning to just perform migration sessions and not Directory Sync. Changes in the source will be minimal. I am aware of two KB articles with attached XML custom add-ins which will skip all attributes. We are considering using these to tightly control which attributes are migrated - Would you consider this to be the best way to prevent the above attributes from synchronising during a migration session? I understand some of the attributes are considered "critical" (mail, mailnickname, proxyadresses, targetaddress) and therefore are greyed out in the migration session skip options. Would the XML file still skip these attributes or is there an easier/better way!? If so would the AD version of the XML file be the correct version to use? Kind Regards
Removing all and reinstalling just the AD bits is more effort then is required. just remove the Exchange bits if they are installed. The mapping data is in the AD LDS data base and stored in the project (upped more node on the left) ADPW and EPW are part of the AD bits and license. Exchange bits are only needed if you are migrating Exchange mailboxes and PFs.
If I understand correctly we will still perform AD and EPW processing as you previously described?
Yes, same process as above.