PowerShell Universal - 5.5.0

PowerShell Universal releases
1

PowerShell Universal - 5.5.0

Release Notes

Features

Admin Console

  • Improved event hub and scripts pages
  • Added known environment variables to support page

Automation

  • Added Computer Offline trigger
  • Added global preference variable settings
  • Added support for individual script permissions

Apps

  • Add option for to make apps as critical for load balancing purposes
  • Add new parameters to New-UDTextbox, New-UDCheckbox, New-UDTransition, and Hide-UDModal
  • Add new New-UDGauge and New-UDSparkline components

APIs

  • C# endpoints now support references and using statements

Module

  • Improved connection management with scopes and disconnection
  • Added cmdlet for retrieving event hub connections
  • Added parameters to Get-PSUJobOutput to limit output and return as object

Platform

  • Added the ability to use powershell.exe directly for environments
  • Added support for app tokens with multiple roles
  • Improved login page layout and added support for Windows Form Login

Bug Fixes

Admin Console

  • Resolved an issue where git credentials could be saved incorrectly when other settings were updated

Apps

  • Resolved an issue where the tree view would not display
  • Resolved an issue with Nivo heatmap charts would display an error
  • Resolved an issue updating page icons from the admin console

Automation

  • Resolved issues with the job dispatcher for computer groups, offline nodes and continuous schedules
  • Resolved an issue where file parameters for scripts did not work properly

Cmdlets

  • Resolved several issues with Invoke-PSUScript

Platform

  • Resolved an issue with password expiration not displaying the password reset form causing lockout
  • Resolved an issue where PSModulePath contained invalid entries for Windows PowerShell 5.1
  • Resolved an issue loading the MicrosoftTeams, Az.Accounts and ExchangeOnlineManagement modules

Downloads

2 Likes
2

Nice. Looking forward to some of these changes/fixes, but I’m gonna hold off until 5.5.1 so I don’t have to deal with disappearing modules and some of the other issues I see slated to be patched in 5.5.1.

2 Likes
3

So I installed this because one of the issues being fixed with it was a major breaking issue for our environment/workflows. All seems to be good now with that, except I’ve noticed the behavior around listing the jobs has changed. Used to be, when you were looking at a script, and selected the “Jobs” tab above the code, it would show you JUST the jobs for that script. Now it’s showing all of them. I don’t know about anyone else, but that’s a non-starter for me. Why did that have to change? It really breaks the functionality of that page. I don’t know what the formal process is for feedback here (still fairly new), but I’m happy to submit a github issue or something.

1 Like
4

It was an unintentional change likely due to a change in how job filtering works in the admin console overall. Bug opened here: Incorrect filtering of jobs from scripts page ¡ Issue #4661 ¡ ironmansoftware/powershell-universal ¡ GitHub

1 Like
5

Ah, ok. That makes sense. I noticed that changed as well, but I don’t remember seeing that change noted in the release notes. But that doesn’t mean anything, my memory is shot. Thanks for responding quickly and putting in the issue! I would have been happy to do it.

1 Like
6

We are seeing an issue where secrets that were working the same day prior to the update appear to be no longer accessible. Is anyone else having that issue?

7

What type of secret vault are you using?

8

Azure Keyvault.

9

Ok. Let me give it a shot. Can you share your Az module version?

10

For reference, it looks like someone already filed an issue for this same problem (not sure if that was you). 5.5.0 can't access secrets in scripts ¡ Issue #4669 ¡ ironmansoftware/powershell-universal ¡ GitHub

11

That was a co-worker. For some reason I cannot create a ticket in the issue tracker. Lets me fill out the template, then gives an generic error and doesn’t create the ticket.

1 Like
12

We are running 6.3.1.

I also created a test credential using the MS SQL database, and had the same issue.

13

I’m getting that same generic error in GitHub. No idea why. I can create blank issues though.

14

I can’t reproduce this issue with database secrets at all. I still need to check Az. Can you check the log for any errors related to this?

15

We deleted all of the secrets and recreated a couple. When stored in the database it is working. We are getting the error below for the Azure Key Vault.

2025-04-21 10:40:31.114 -05:00 [ERR][PowerShellUniversal.Secrets.SecretManagerService] Failed to read secret: Your Azure credentials have not been set up or have expired, please run Connect-AzAccount to set up your Azure credentials.
Method not found: ‘Void Azure.Identity.Broker.SharedTokenCacheCredentialBrokerOptions..ctor(Azure.Identity.TokenCachePersistenceOptions)’.
Microsoft.Azure.Commands.Common.Exceptions.AzPSArgumentException: Your Azure credentials have not been set up or have expired, please run Connect-AzAccount to set up your Azure credentials.
Method not found: ‘Void Azure.Identity.Broker.SharedTokenCacheCredentialBrokerOptions..ctor(Azure.Identity.TokenCachePersistenceOptions)’.
—> System.MissingMethodException: Method not found: ‘Void Azure.Identity.Broker.SharedTokenCacheCredentialBrokerOptions..ctor(Azure.Identity.TokenCachePersistenceOptions)’.
at Microsoft.Azure.PowerShell.Authenticators.SilentAuthenticator.GetTokenCredentialOptions(SilentParameters silentParameters, String tenantId, String authority, PowerShellTokenCacheProvider tokenCacheProvider)
at Microsoft.Azure.PowerShell.Authenticators.SilentAuthenticator.Authenticate(AuthenticationParameters parameters, CancellationToken cancellationToken)
at Microsoft.Azure.Commands.Common.Authentication.DelegatingAuthenticator.TryAuthenticate(AuthenticationParameters parameters, CancellationToken cancellationToken, Task1& token) at Microsoft.Azure.Commands.Common.Authentication.DelegatingAuthenticator.TryAuthenticate(AuthenticationParameters parameters, CancellationToken cancellationToken, Task1& token)
at Microsoft.Azure.Commands.Common.Authentication.DelegatingAuthenticator.TryAuthenticate(AuthenticationParameters parameters, CancellationToken cancellationToken, Task1& token) at Microsoft.Azure.Commands.Common.Authentication.DelegatingAuthenticator.TryAuthenticate(AuthenticationParameters parameters, CancellationToken cancellationToken, Task1& token)
at Microsoft.Azure.Commands.Common.Authentication.DelegatingAuthenticator.TryAuthenticate(AuthenticationParameters parameters, CancellationToken cancellationToken, Task1& token) at Microsoft.Azure.Commands.Common.Authentication.DelegatingAuthenticator.TryAuthenticate(AuthenticationParameters parameters, CancellationToken cancellationToken, Task1& token)
at Microsoft.Azure.Commands.Common.Authentication.DelegatingAuthenticator.TryAuthenticate(AuthenticationParameters parameters, Task1& token) at Microsoft.Azure.Commands.Common.Authentication.Factories.AuthenticationFactory.Authenticate(IAzureAccount account, IAzureEnvironment environment, String tenant, SecureString password, String promptBehavior, Action1 promptAction, IAzureTokenCache tokenCache, String resourceId)
at Microsoft.Azure.Commands.Common.Authentication.Factories.AuthenticationFactory.Authenticate(IAzureAccount account, IAzureEnvironment environment, String tenant, SecureString password, String promptBehavior, Action1 promptAction, String resourceId) at Microsoft.Azure.Commands.Common.Authentication.Factories.AuthenticationFactory.GetServiceClientCredentials(IAzureContext context, String targetEndpoint, String resourceId) --- End of inner exception stack trace --- at Microsoft.Azure.Commands.Common.Authentication.Factories.AuthenticationFactory.GetServiceClientCredentials(IAzureContext context, String targetEndpoint, String resourceId) at Microsoft.Azure.Commands.Common.Authentication.Factories.AuthenticationFactory.GetServiceClientCredentials(IAzureContext context, String targetEndpoint) at Microsoft.Azure.Commands.KeyVault.Models.KeyVaultDataServiceClient..ctor(IAuthenticationFactory authFactory, IAzureContext context) at Microsoft.Azure.Commands.KeyVault.Models.KeyVaultCmdletBase.get_DataServiceClient() at Microsoft.Azure.Commands.KeyVault.GetAzureKeyVaultSecret.ExecuteCmdlet() at Microsoft.WindowsAzure.Commands.Utilities.Common.CmdletExtensions.<>c__31.b__3_0(T c)
at Microsoft.WindowsAzure.Commands.Utilities.Common.CmdletExtensions.ExecuteSynchronouslyOrAsJob[T](T cmdlet, Action`1 executor)
at Microsoft.WindowsAzure.Commands.Utilities.Common.CmdletExtensions.ExecuteSynchronouslyOrAsJob[T](T cmdlet)
at Microsoft.WindowsAzure.Commands.Utilities.Common.AzurePSCmdlet.ProcessRecord()
2025-04-21 10:40:31.490 -05:00 [INF][PowerShellUniversal.Automation.ExecutionService] Job 941 completed with status Error.

16

Thanks. I will have to have to track this down. It’s an assembly mismatch. We downgraded some assemblies to support other libraries and I worry it may have affected the Az module as well. :face_with_spiral_eyes:

1 Like
17

Thanks Adam. Is there a process to downgrade to the previous version?

18

We have some information here.

You shouldn’t have to downgrade the database schema since it wasn’t a major version change, which should simplify it a lot.

19

I’m still seeing issues connecting to Exchange using ExchangeOnlineManagement module version 3.7.2 using the command below;

Is there anything I’m overlooking or that might need updating on the server? Or was this particular issue not addressed in 5.5.0?

Thanks.

Connect-ExchangeOnline -CertificateThumbprint $Session:Thumbprint -AppID "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -Organization "xxxxxxxxxxxxxx.onmicrosoft.com" -ShowBanner:$False

image
image2053×1909 164 KB

20

Further to the above, it only errors if I run in this environment;

image
image3069×573 26.9 KB

Integrated works ok and I have additionally installed Powershell 7 directly on the server and pointed a new environment at it - that works ok also.