PowerShell Universal - 5.5.0

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

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

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

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

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

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?

What type of secret vault are you using?

Azure Keyvault.

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

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

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

We are running 6.3.1.

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

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