PowerShell Universal cmdlets return a 404 over HTTPS
PowerShell Version: Windows PowerShell 5.1
When issue commands against the PowerShell Universal Management API (such as Get-UAJob, Get-UAScript, etc), the cmdlet will return a 404 error. This can happen when running scripts within PowerShell Universal (APIs, scripts, dashboards) or outside of PowerShell Universal.
The cause of this issue is misconfigured TLS settings for the PowerShell process. You will not see this issue with PowerShell 6 or 7 but will present itself in Windows PowerShell.
The workaround for this issue is to set the TLS setting to 1.2 for the Windows PowerShell process. You can do so with the following snippet.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
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 ...
KB0035 - How to add the Calendar and other components
Purpose The purpose of this article is to demonstrate how to install and use the Calendar component (module) Background There is a growing list of add-on components (modules) for PowerShell Universal at ...
KB0034 - How to collect logs
Purpose The purpose of this article is to provide clear ordered steps for users of PowerShell Universal and to submit them to Ironman Software (typically for a support case). Background Having logs from PowerShell Universal is typically needed to ...
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 ...
KB0002 - Security features of PowerShell Universal
In terms of security features, PowerShell Universal currently provides: HTTPS for over the wire encryption Authentication providers such as SAML2, OpenID Connect, Windows (NTLM\Kerberos), WS-Federation, client certificate, and basic auth Role-based ...