-
Title
A new license will not stay applied. Or shows the wrong License count -
Description
A new license will not stay applied. The license values will seemingly revert as if the license was not applied, and the old values will be present. This seems to especially occur after the Directory Synchronization Agent Configurator Service is restarted.
-
Cause
This can happen for several reasons including upgrade, a new licensing registry key was created in a new location, but the old one was not removed as part of the upgrade process. This is a known issue and will be resolved in a future release.
The proper method for applying a new License file is as follows:
- Open the Migration Manager Console
- From the Menu Bar choose Help-About
- Click the update License button
- Select the New license file and select OK
- Select each license type and confirm the license count
- Select OK to close the License window
- Close the console -- this step actually writes the License information to the ADAM\AD LDS database
- If possible restart the server to confirm functionality
Should these steps not resolve the issue, we must manually zero out the current License values so that it can accept the new values .
-
Resolution
NOTE
Before performing any steps take the appropriate steps to be able to recover the registry keys edited and to be able to revert the ADAM database back to the prior state. ADAM\AD LDS databse backups should be part of the regular backup routine in your environment.
- Close the Migration Manager console, and stop all services on the console and DSA servers.
- Open regedit and search for the term "SoftLicense"
- Export this key
- Within the above key, there will be a REG_BINARY value called "SoftLicense". Delete it.
- Open ADSIEDIT with the MMAD service account
- Create a new connection to the naming conext CN=Projectname (whatever the projectname is)
- Specify a server and port in the bottom field if needed
- Once connected, expand the project and expand the container resembling "AMMProject_{GUID}"
- Right click "License" and go to properties
- Find the aelita-Amm-LicenceBody value and copy it's contents to a notepad file. This should resemble the old/unwanted license values
- Clear the value using the "Clear" button
- Select Apply and OK
- Start the console and Apply the correct license
- Start the MMAD services
The License should now stay applied.Windows Registry Disclaimer:Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support. -
Additional Information
Ensure all backups are taken before modifying the registry or ADAM/LDS project.