Migration will include some remote locations - is it a good idea to install multiple QMM consoles?
How will licensing work?
Multiple connections whether using RDP, Terminal Services or other remote connection tools to the same project, on the same machine puts you at risk of corrupting the ADAM instance, and therefore it is not supported. Also note that the scenario where multiple consoles have been installed on the same machine is not supported as the same result is possible.
If multiple consoles are absolutely necessary then it is recommended to install different (multiple) ADAM instances and configure a replication between ADAM instances.
It is important to understand that one can use one single console and a single SQL and ADAM database and still be able to perform migrations in remote locations. In such situation separate DSA can be deployed on each location and configured to use preferred DCs in same location so all the work will happen on local machines on the same site.
The same applies to Exchange migration: QMM console and SQL will only contain the settings, the agents will be installed on local source and target servers on site, so remote location should not affect the performance.
QMM Best Practices contains a section How Many Projects to Have, below is an excerpt:
Migration Manager allows you to configure a separate directory synchronization job for each pair of the source and the target domains. With Migration Manager you can also split your source forest or Exchange organization or merge a number of forests or Exchange organizations into one target.
The best practice is to use a single migration project for all your migration activities because of the following:
Because you can work with only one project at a time from the console, configuring all the domain pairs, synchronization jobs, synchronization agents, etc. is easier using a single project.
The project database is the central storage of the object mapping information that is used during resource processing to translate rights and permissions. Using multiple projects requires you to update resources separately for each project for which you have to update rights, permissions, local group membership, etc.
You can delegate rights to perform migration tasks (such as configuring domain pairs, migrating accounts, and updating resources) to different persons and migration teams. A single project helps you track who has what rights (roles) in the project more easily. For more information about delegation, refer to the Delegating Migration Tasks section.
Using multiple consoles with the replicated ADAM instances while sharing the same project database should not affect the licensing, the same license file can be used. Quick Start Guide contains more licensing information (please see Licensing section).
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center