Licensing ServiceControl

There are a few options to add a license to ServiceControl.

Note that the license file might allow running multiple products (NServiceBus Core, ServiceControl and ServiceInsight). Therefore the license file can also be loaded from other platform tools to achieve the same end result, as long as the licensing method imports the license into the registry.

ServiceControl Management app

ServiceControl has a license graphical user interface which can be accessed in the ServiceControl Management app. The app is installed together with ServiceControl and can be found in the Windows Start Menu.

The app will import the designated license file into the registry. The license file is added to the HKEY_LOCAL_MACHINE registry hive so it is available to all instances of ServiceControl regardless of the service account used.

ServiceControl PowerShell

To import a license using PowerShell:

  • Start the ServiceControl PowerShell Management Console from the start menu
  • Execute the following cmdlet with the path to the license file.
Import-ServiceControlLicense <LicenseFile>

Using other platform tools

See the ServiceInsight licensing page or the instructions for licensing manually using the registry for more information.

Instance licensing

In Versions 1.17 and below, a license can be applied to an individual instance rather than using a license installed in the registry. To do this, copy the license.xml file to a license directory under the installation path of the instance.

Instance Licensing is deprecated in Version 1.18 and above. Use ServiceControl Management or the ServiceControl PowerShell module to install the license file to the registry.


ServiceControl license was updated but ServicePulse reports the license has expired

License information is read at service start up and cached. Once a new license is applied the ServiceControl instance must be restarted to detect the license change, until then the license status shown in ServicePulse is based on the cached state.

Last modified