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

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

See the documentation at Licensing - PowerShell Universal for more information

Developer Licenses

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

    • 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 ...

    • KB0015 - Offline PSU server has slow dashboards

      Disclaimer Please be careful with changing any settings on your server around the Certificate Revocation List. You should only do this if you know what you are doing. Read the related Github articles (linked below) in their entirety. Symptom PSU ...

    • KB0013 - Moving PSU to another server

      Below are Adam's comments on this topic from August 2nd, 2022: The configuration for PowerShell Universal, including the license, is stored as PS1 files in the repository directory. https://docs.powershelluniversal.com/config/repository We recommend ...

    • KB0022 - Unable to login after upgrading to PowerShell Universal 3.7.1

      Affected Versions - PowerShell Universal 3.7.0 - PowerShell Universal 3.7.1 Issue A user attempts to login with the default admin account and cannot access the system. Solution - Upgrade to PowerShell Universal 3.7.2 - Remove the admin account from ...

    • KB0020 - Firewall Configuration for PowerShell Universal

      Purpose The purpose of this document is to provide information about the necessary filewall settings required by PowerShell Universal. Overview PowerShell Universal does not offer a built in firewall. We recommend using standard firewalls available ...