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 you provide access locally to an environment using the dev license, then you can use it.
We now return to your regularly scheduled KB article
Developers licenses with limited functionality may be created for PowerShell Universal QA/Test servers by using the 'Generate Developer License' button under Settings -> License (see screenshot below)
🛑 You must have at least 1 licensed instance of PowerShell Universal to do this
When a server license is purchased, you will be able to generate developer licenses for users building solutions for your team. Developer licenses do not allow remote access and are intended to be used locally. Do not use developer licenses when hosting a server for remote access for testing or production.
Related Articles
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 ...
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 ...
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 ...
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 ...
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 ...