PowerShell Universal - 5.0.15
PowerShell Universal - 5.0.15
Release Notes
Admin Console
- Fixed an issue with tagged variables (#4002)
- Added Telemetry option to General Settings
- Added Report Bug button to error alert
- Added tooltip help to maintenance mode and readonly mode for computers (#3996)
- Added Help menu
- Documentation links now open in a new tab
- Fixed an issue with job execution time (#4016)
- Reduced Blazor log level
- Fixed an issue when jobs had multiple requests for feedback
APIs
- Fixed an issue where event hub agent would not log Write-* calls (#3983)
- Added -RemoteDomainName and -RemoteUserName to Get-PSUEventHubConnection (#4009)
- Fixed an issue where event hubs would only run one command at a time (#3988)
Apps
- Fixed an issue with button colors (#3974)
- Fixed an issue where apps would auto-deploy when secrets were changed (#4022)
Automation
- Fixed an issue grooming jobs (#3929)
Cmdlets
- Added -Integrated mode for cmdlets
- Added -Silent to Invoke-PSUScript and Wait-PSUJob
- Fixed an issue with switch parameters and Invoke-PSUScript (#4011)
Platform
- Fixed an issue where the service could crash when losing database connection (#4012)
- Fixed an issue where secrets could be deleted in multi-node environments during git sync (#3959)
Downloads
Adam Driscoll
PowerShell Expert and Developer at Devolutions
All Comments (6)
Fingers crossed that this upgrade goes smoothly.
Edit: No errors, post upgrade, and nothing seems to be missing (such as variables), so I’d say it’s a success as of this moment.
I’d also like to just highlight the integrated mode change for cmdlets. It’s the same mechanism used in v4. You can read more about it here:
docs.powershelluniversal.com
Adam Driscoll
PowerShell Expert and Developer at Devolutions
Just to make sure I understand the implications, this would make it so scripts used in scheduled tasks and such would no longer need to have Connect-PSUserver at the top, correct?
Correct. It just uses the backchannel and doesn’t need the API or credentials defined .
Adam Driscoll
PowerShell Expert and Developer at Devolutions
me too!
Could this allow me to run a script on one node but use the Invoke-PSUScript cmdlet to execute it on another node without API access to that other node?
I may have submitted a feature request for this functionality yesterday…