Updated license file will not stay applied and results in license violation error when migrating users. (4262233)

After applying an updated license file for Migration Manager for Active Directory, initially the updated total license count displays correctly within the Help -> About menu.

However, when attempting to perform a migration of new users the following error is returned - and checking in the Help -> About menu shows the license count may also revert to the previous total license count.

"Error 0xe3000001. License violation"

When the license file is updated in the Migration Manager console, as a result - the licensing information will be updated in the ADAM / ADLDS database.

In some instances, this does not occur successfully while the console is open - and causes the Directory Synchronization Agent to use the stale data within the ADAM / ADLDS database.

To ensure the license file is properly updated - and the Directory Synchronization Agent is updated with the newly applied license information, please use the following steps to update the license file:

1. Stop the Directory Synchronization using the Migration Manager Console, by right clicking "Synchronization" under all listed domain pairs - and select "Stop".

2. Then, navigate to the Help -> About menu and then click on the Migration Manager for Active Directory license file.  Next, click the Update License button and browse to the .asc file that you'd like to use and select to open it.

3. Click the Details button next, and ensure the updated amount of total licenses for Migrated Users is shown.  Then, simply close and re-open the Migration Manager Console, and ensure the updated license count is still displayed.  (This will effectively force the console to rewrite the license information to the ADAM / ADLDS database).

4. To ensure the Directory Synchronization Agent sees the newly updated license count, use the Services management console and restart the Directory Synchronization Agent Configurator Service.

Once these steps are completed, create a new Migration session - and attempt to migrate the users that were previously failing due to the license violation error.