Additional Modules

ScriptRunner licenses are modular and structured according to functions. The function modules must be activated individually. The following function modules are delivered with ScriptRunner:

  • Base controls the licensing in the trial period as well as the licensed users.
  • Maintenance controls the licensing of the update and upgrade capability of the installation.
  • SQL Connector controls the licensing of the SQL Connector for the external reporting or audit database.
  • Web Service Connector controls the licensing of the Web Service interfaces.
  • E-Mail Inbound Connector controls the licensing of the mail service interfaces.
  • Password Server Connector controls the licensing of access to external password safes.

Trial License

After the installation you have to register once in the Admin App, after that the software runs for 30 days with a trial license. This includes the possibility of five users, a web service interface and the Inbound-E-mail-Interface. The update capability is deactivated during this period. After the evaluation period has expired, the automation interfaces must be unlocked with a valid key.

Note: If you do not have access to the Internet, follow the instructions in Offline Environment.

The license status can be viewed in the ScriptRunner Admin App in the main menu under >Settings >ScriptRunner License Status >View.


The license information can also be retrieved with the PowerShell module ScriptRunnerSettings. To do this, open the PowerShell console or PowerShell ISE as administrator on the ScriptRunner server and execute the Get-AsrLicense command.

Get-AsrLicense

Output of the license information

Product Activation

The ScriptRunner license module must be initialized once using the Base License. With the initialization the license is registered and copy protected. For initialization, the ScriptRunner Host must be connected to the Internet. The process is performed with the PowerShell module ScriptRunnerSettings. To do this, open the PowerShell console or PowerShell ISE as administrator and enter the following command:

Note: The ScriptRunner service must be restarted for license activation, use the Restart parameter.

Initialize-AsrLicense -Firstname ScriptRunner -Lastname Demolicense -Email Demolicense@ScriptRunner.com -Company ScriptRunner -ActivationKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX -Restart

Mandatory parameters are *Email, *Company and *ActivationKey.

Initialize-AsrLicense

License key for product activation

As an alternative, you can use the following command for the restart:

Restart-AsrService

Offline Environment

In specially secured offline environments without Internet connection, an additional offline key is required. For the offline key the Offline ID4 of your system is required, it can be queried with the PowerShell module ScriptRunnerSettings. To do so, open the PowerShell console or the PowerShell ISE as administrator on the ScriptRunner server and execute the command Get-AsrLicense.

Get-AsrLicense

Output of the Offline ID4

With this ID you can contact us via support@scriptrunner.com to generate the necessary key before initializing the Base License.

The ScriptRunner license module must be initialized once using the Base Activation Key and unlocked using the Unlock Key. The process is performed with the PowerShell module ScriptRunnerSettings. To do this, open the PowerShell console or the PowerShell ISE as administrator and enter the following command:

Note: The ScriptRunner service must be restarted for license activation, use the Restart parameter.

Initialize-AsrLicense -Firstname ScriptRunner -Lastname Demolicense -Email Demolicense@ScriptRunner.com -Company ScriptRunner -ActivationKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX -UnlockKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX -Restart

Mandatory parameters are *Email, *Company and *ActivationKey.

Initialize-AsrLicense

License key for the product activation in offline environments

As an alternative, you can use the following command for the restart:

Restart-AsrService

Activate Additional Modules

After a successful initialization, further functions (e. g. extension or maintenance) can be added via license key.

The activation of further keys needs to be executed with the PowerShell module ScriptRunnerSettings. The process is performed with the PowerShell module ScriptRunnerSettings. To do this, open the PowerShell or the PowerShell ISE as administrator and enter the following command:

Note: The ScriptRunner service must be restarted for license activation, use the Restart parameter.

Update-AsrLicense -Key XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX -Restart

Repeat this for all keys.

Update-AsrLicense

Activation of additional modules

As an alternative, you can use the following command for the restart:

Restart-AsrService

The license status can be viewed with the following commands:

Get-AsrLicense
Get-AsrLicensedUser
Get-AsrLicense

Output of the license information

After the start of the ScriptRunner Admin App, the current license status will be displayed.

Suggest Edit