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 Universal license will be expiring soon (screenshot needed)
Impact
There will not be any immediate impact to the instance because the license is perpetual (forever). However, the instance is no longer supported with further upgrades. Past versions of PowerShell Universal will always be available for download from https://ironmansoftware.com/powershell-universal/downloads.
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 ...
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 ...
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 ...
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 ...
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 ...