-
Title
How does Migration Manager for Exchange count licenses? -
Description
How does Migration Manager for Exchange count licenses?
-
Resolution
The Migration Manager for Exchange license (.asc file) specifies the maximum number of mailboxes that you can migrate. Since Migration Manager for Exchange uses a distributed architecture, the Migration Manager agents obtain all license information from a single server, the license server. By default, a server on which the Migration Manager is installed is used as the license server. Later you can change the license server in the Options dialog available from the Tools menu in Migration Manager for Exchange.
In fact, only the Mail Synchronization Agent (MSA) and Migration Agent for Exchange (MAGE) request license information from the license server and increment the license counters for each synchronized mailbox.
The Mail Source Agent and Migration Agent for Exchange service accounts must have access to the license server.
For Mail Source Agent (MSA) and Migration Agent for Exchange (MAgE) required permissions please refer to Source Accounts Used by Migration Manager for Exchange Agents section of the System Requirements and Access Rights document which can be found at https://support.quest.com/technical-documents/preparing-migration/8.14/system-requirements-and-access-rights/14#TOPIC-711866
A license unit is used whenever the MSA or MAGE logs into a mailbox whose legacyExchangeDN has not already been synchronized, i.e. the license is consumed only if a mailbox is placed into a non-disabled mailbox collection for the first time and processed by any of the above mentioned agents.
Please see 25143 - How to determine how many mailbox licenses are used? at https://support.quest.com/migration-manager-for-exchange/kb/25143
-
Additional Information
Migration Manager for Exchange version 8.11 and earlier used to have a known issue when the licenses are counted twice. Please refer to https://support.quest.com/migration-manager-for-exchange/kb/80931 for details on the issue. Starting from Migration Manager for Exchange version 8.12 the issue described in the above artilce has been fixed and no longer applies to any agents (legacy or MAGE) of version 8.12.