KB0064 - Migrating A PowerShell Universal License Between Servers

KB0064 - Migrating A PowerShell Universal License Between Servers

Purpose

The purpose of this article is to provide information about moving a PowerShell Universal license from one server to another. 

Process

In order to move a license from one server to another, you will need to first have your licensed server up and running.
Next, install PowerShell Universal on a second server.
At this time, you can install the license file onto second server. To locate your license file, you can do one of the following. 
- Login to your Ironman Software account and download your license file. 
- Retrieve your license file from licenses.ps1 within the PowerShell Universal repository directory (this may not exist on newer versions) 
- Retrieve your license file from the Database. It will be present in the Licenses table, and you will need to copy the LicenseText contents and store them in a file. 
Once you have a file with your license contents, you can install it into the new server. This will not affect the old server as we provide a buffer of time to allow for migrations of licenses. 
Once the new server is licensed, navigate to the old server and delete the license from the License page within the admin console.

SQL Persistence

If both servers are using the same database, there is no need to migrate the license. Version 4 and later of PowerShell Universal will store the license file directly in the database. Connecting the new server and stopping the old server are all that is required in order for the new server to begin using the license. 

    • Related Articles

    • KB0011 - Are licenses different between Production, QA and Test/Development servers?

      Update January 24th, 2023 Adam recently summarized the Developer's license per below: The only real limitation on the developer license is that it cannot be accessed remotely. The server is only available on loopback when using the dev license. If ...

    • KB0048 - License is about to expire

      Scope This article only applies to PowerShell Universal instances with a perpetual license (monthly licenses excluded). See https://ironmansoftware.com/license/info for more information about PowerShell Universal licensing. Problem Your PowerShell ...

    • KB0036 - How to set the license via environment variable

      Purpose The purpose of this article is to explain how to set the license for PowerShell Universal by way of environment variable instead of the traditional file-based method. Scope For now, only Windows is in the scope of this article. Linux and ...

    • PowerShell Universal Service crashes on startup after an upgrade to 1.4.6

      Version: PowerShell Universal 1.4.6 Issue The PowerShell Universal service will crash with the following error in Event Viewer.  Application: Universal.Server.exe CoreCLR Version: 4.700.19.56402 .NET Core Version: 3.1.0 Description: The process was ...

    • KB0074 - Connecting to PSU API w/Windows Auth

      Scope This article applies only to PSU environments where Windows Authentication[1] is enabled and known to be working[2]. Problem You are not able to interact with the PSU instance using the Invoke-WebRequest PowerShell cmdlet even though logging in ...