Devolutions PowerShell Universal - Devolutions Forum

Ctrl + k

Devolutions PowerShell Universal

Devolutions PowerShell Universal

Announcement

Monitor this forum to get notified when a new update is available

Support

Support forum for Devolutions PowerShell Universal

Support (Français)

Forum de support dédié aux demandes en français

Support (Deutsch)

Supportforum für deutschsprachige Benutzer

Bug Report

Report bugs for Devolutions PowerShell Universal

Feature Request

Feature request forum for Devolutions PowerShell Universal

Community Showcase

Explore and share solutions built with Devolutions PowerShell Universal

Recent Posts

Published an hour ago

Icon button

Hello! Thank you for the request! Are there specific options/attributes that you're particularly interested in PSU supporting? I will add a ticket for us to look into this, and I want to make sure we have your use case covered.

Feature Request

Published 2 hours ago

UDTable On Row Click

PSU 2026.1.2 I'm looking for a way to pop up additional information when clicking on a row (not selecting a row) in a UDTable. I know there's the expand row option, which opens an expand box below the row and there's the option of adding a custom button, but I was hoping there was a way to support clicking on the row and it could then support a code block (in my case, likely open a modal with the extended details of the row item). For instance, the table would have like New-UDTable -LoadData { $Data } -Columns @( New-UDTableColumn -IncludeInExport -Id Id -Property Id -Title "Id" -Width 50 New-UDTableColumn -IncludeInExport -Id ServerName -Property ServerName -Title "Server Name" -Width 150 New-UDTableColumn -IncludeInExport -Id CPUS -Property CPUS -Title "CPUs" New-UDTableColumn -IncludeInExport -Id Memory_GB -Property Memory_GB -Title "Memory (GB)" New-UDTableColumn -IncludeInExport -Id OperatingSystem -Property OperatingSystem -Title "Operating System" -Width 100 ) -OnRowClick { Show-UDModal -Persistent -FullWidth -Content { New-UDCard -Content { New-UDGridLayout -Content { $VMData = Invoke-PSUEndpoint -Integrated -Url "/api/v1/VM/$($EventData.Id)" | ConvertFrom-Json New-UDTextbox -Id 'Id' -Label 'Id' -Value $EventData.Id -Disabled New-UDTextbox -Id 'ComputerName' -Label 'ComputerName' -Value $EventData.ServerName -Disabled New-UDTextbox -Id 'Department' -Label 'Department' -Value $VMData.Department -Disabled New-UDTextbox -Id 'Owner' -Label 'Owner' -Value $VMData.Owner -Disabled New-UDTextbox -Id 'State' -Label 'State' -Value $VMData.State -Disabled } } } } And then when clicked on, it would display a bunch of additional information, like power state, health of tracked services, drives, other internal server tracking values that bloat the original table well beyond the width of the screen. I know this could probably be done in an expand, but it requires you click on the dropdown button rather than just the row itself (and frankly looks ugly compared to a popup modal / so I'd just do a details button at that point), so I was hoping someone might have an idea or way to accomplish what I'm looking for as an on row click (anywhere in the row preferably).

Published 3 hours ago

LoginPageLogoSize Issue

Hello btull Thank you for the detailed report and screenshots. From the browser inspection, I can see the logo is being rendered at approximately 128 px wide, with the image inheriting its dimensions from the surrounding element. That lines up with your observation that changing `LoginPageLogoSize` does not appear to affect the displayed size. Since you have already tested several value formats, I would like to reproduce this specifically on PSU 2026.2.2 rather than have you continue trying different syntax without confirming the expected behavior first. In the meantime, could you please confirm whether the same behavior occurs after a hard browser refresh or when opening the login page in a private browsing window? This will help rule out cached styling while I compare the behavior in a clean environment. I will also check whether the parameter is being applied to the generated login page markup as expected. Best regards, Ruben Tapia rubentapia Yes, it continues to happen in an Incognito/InPrivate window, as well as closing and reopening the browser. btull Thank you for confirming. Since the behavior also occurs in an Incognito/Private window and after restarting the browser, we can reasonably rule out normal browser caching as the cause. As the next step, could you please capture a HAR while reproducing the issue and also collect the PSU logs covering the same time period? If possible, please include the approximate reproduction time and time zone so I can correlate the events. Because HAR files and PSU logs may contain sensitive information, please send them directly to: ruben.tapia@ironmansoftware.com Please do not attach the HAR or unredacted logs to this public thread. Once I have that evidence, I can compare it with the PSU 2026.2.2 reproduction and review how LoginPageLogoSize is being applied during the login page load. Best regards, Ruben Tapia

Published 4 hours ago

LoginPageLogoSize Issue

Hello btull Thank you for the detailed report and screenshots. From the browser inspection, I can see the logo is being rendered at approximately 128 px wide, with the image inheriting its dimensions from the surrounding element. That lines up with your observation that changing `LoginPageLogoSize` does not appear to affect the displayed size. Since you have already tested several value formats, I would like to reproduce this specifically on PSU 2026.2.2 rather than have you continue trying different syntax without confirming the expected behavior first. In the meantime, could you please confirm whether the same behavior occurs after a hard browser refresh or when opening the login page in a private browsing window? This will help rule out cached styling while I compare the behavior in a clean environment. I will also check whether the parameter is being applied to the generated login page markup as expected. Best regards, Ruben Tapia rubentapia Yes, it continues to happen in an Incognito/InPrivate window, as well as closing and reopening the browser.

Published 4 hours ago

LoginPageLogoSize Issue

Hello btull Thank you for the detailed report and screenshots. From the browser inspection, I can see the logo is being rendered at approximately 128 px wide, with the image inheriting its dimensions from the surrounding element. That lines up with your observation that changing `LoginPageLogoSize` does not appear to affect the displayed size. Since you have already tested several value formats, I would like to reproduce this specifically on PSU 2026.2.2 rather than have you continue trying different syntax without confirming the expected behavior first. In the meantime, could you please confirm whether the same behavior occurs after a hard browser refresh or when opening the login page in a private browsing window? This will help rule out cached styling while I compare the behavior in a clean environment. I will also check whether the parameter is being applied to the generated login page markup as expected. Best regards, Ruben Tapia

Published 4 hours ago

Clicking on the column picker under jobs throws the following error.

Hello michaelhanson1458 Thank you for confirming that. That is useful information, especially since the same behavior is occurring on two different PSU instances running the same version, with production using SQL and development using SQLite. This week, I will work on setting up a lab environment and try to reproduce the issue under comparable conditions. I will focus on the Jobs table column picker behavior and compare the results against the exception shown in your screenshot. In parallel, could you please run one additional test on your side? If possible, try opening the Jobs column picker using a different PSU user account and let me know whether the same error occurs. That result will help us determine whether the behavior is tied to a specific user state or whether it affects the environment more broadly. Once I have completed the lab testing, I will update this thread with the findings and next steps. Best regards, Ruben Tapia

Published 6 hours ago

Apps restart when git runs, even though apps set not to auto deploy

Hello squinlan Thank you for the additional details and for testing `Synchronize Now`. The fact that manual synchronization does not restart the Apps, including when Git contains changes limited to scripts, is very useful and suggests that we need to look more closely at what happens during the automatic cycles where the restart actually occurs. At this point, the next best step is to review the PSU logs around one or more confirmed App restart events. Since the logs may contain environment-specific or sensitive information, please do not upload the complete logs to this public forum. Instead, please send them directly to: ruben.tapia@ironmansoftware.com Please include case `56106` in the subject or body, along with the approximate timestamp and time zone of the restart event. If possible, logs covering a few minutes before and after the restart would be ideal. Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread. Once I review the logs, I can correlate the App restart sequence with the Git Sync activity and determine what we should test next. Best regards, Ruben Tapia

michaelhanson1458

Published 7 hours ago

Clicking on the column picker under jobs throws the following error.

No this was found in my dev instance of PSU. However, its running the same version of psu and the only difference is one is prod is using sql and dev is sqlite

Published 9 hours ago

LoginPageLogoSize Issue

Version 2026.2.2 I'm having an issue with the 'LoginPageLogoSize' parameter with New-PSUBranding. I've tried integers, percentages, 'x' (times), 'X px, Y px'. Nothing seems to be changing the size of the logo. Using a test image right now for anonymity, but on our old 4.5.5 environment, the logo size is exactly the same size as the picture. This version seems to shrink it down but I can't seem to figure out the syntax. Has anyone got this to work? Thanks! $Parameters = @{ LoginPageImage = "/Images/Powershell.jpg" LoginPageLogoSize = "2x" LoginPageDescription = "" AdminConsoleTitle = "PSU Admin Console" Copyright = " " AppNotRunningDescription = "HALP :( This dashboard is not running!" LoginPageTitle = "Test" LoginPageTheme = "System" } New-PSUBranding @Parameters [image]

Published 13 hours ago

Apps restart when git runs, even though apps set not to auto deploy

Thanks for the quick reply Are all Apps restarting, or only specific Apps such as InfraTools? All apps restart Under Settings > Files > Configuration Changes, is automatic configuration reload enabled? I don't have "Configuration Changes" under Settings - Files. Just the list of files in the git repository. Clicking on an individual file and clicking the cog just gives some display options. What hosting method are you using for PSU 5.5.2, for example Windows Service, IIS, or ZIP? Windows service Is this a production environment, and do active users lose their sessions when the restart occurs? The user is not logged out (we use AD authentication), the app just refreshes within the browser. Same thing as if I click Reload on an app manually. If the app is processing something, then this is cancelled. If a form is filled in, then the form is cleared. If the local and remote repositories are fully synchronized, does clicking Synchronize Now manually also restart the App when Git reports no changed files? No, this does not force a reload of the app. I tried clicking the Synchronize Now button a few times and the apps do not reload. The git sync is set to every 10 mins, but the reloads of the apps are not every 10 mins (more along the lines of every 25-60 mins), so there does seem to be something else triggering the reload. Interestingly, I pushed a change to the main branch today and then immediately clicked the Synchronize Now button (rather than wait for the automatic sync). The change in git was only to two scripts (no apps were change) and the script changes were pulled down correctly without the apps reloading. Support for disabling scheduled synchronization by setting the Git sync interval to 0 was added in an earlier PSU release, so this may also be useful as a temporary diagnostic control while we investigate the unexpected App restarts. If I set the git sync interval to 0 in the GUI, it resets back to 1 when I click Save. Possibly I can set it to 0 in appsettings.json, but I don't want to modify the production server during the week if I can avoid it. I will do more testing on our Dev server but need to do a bit of work to get it into the same state as the prod one for a proper test.

Published a day ago

Clicking Child Jobs shows blank page

Hello michaelhanson1458 Thank you again for providing the HAR file. I completed the initial review and sent you a follow-up by email with the findings and the additional information we need to continue the investigation. Because the HAR and related server-side evidence may contain sensitive environment information, I am keeping those technical details out of the public forum. I have also requested a small, sanitized set of PSU server logs from the timeframe of the reproduction so we can correlate the browser-side behavior with the server-side activity before providing the next update to Development. Once I receive and review those logs, I will continue the investigation and update this thread with any findings that are appropriate to share publicly. Best regards, Ruben Tapia

Published a day ago

Roles/Permissions assignment not working

Hello tt_gopsu Thank you for the additional testing and for documenting the different Tag, Role, and Execute combinations. We have now shared the updated findings directly with the Development team for review. The new results suggest that the interaction between Tags, Portal visibility, script roles, and Execute permissions may require clarification beyond documentation alone. Your current workaround remains valid for your environment, and the additional matrix you provided is helpful for the ongoing review. We will update the thread once we receive further guidance from Development. Best regards, Ruben Tapia

Published a day ago

Write-PSULog -Properties How To

Hello jamesnewbanks We have completed the lab validation on PSU 2026.2.5 and were able to reproduce the behavior consistently. The findings have now been escalated and are being reviewed directly by our Development team to confirm the intended behavior of Write-PSULog -Properties, particularly the differences we observed between persisted logging, -Console, and the built-in logging data. I’ll update this thread as soon as we receive their feedback. Best regards, Ruben Tapia

Published a day ago

Clicking on the column picker under jobs throws the following error.

Hello michaelhanson1458 Thank you for reporting this and for providing the additional screenshot. I noticed that this appears to match the behavior you previously reported in topic 56022 regarding the Jobs table column selector. The new screenshot is particularly useful because it provides a more detailed exception involving the `AntDesign.RangePicker<DateTime?>` component. To avoid duplicating the troubleshooting already completed, could you please confirm whether this new report is from the same PowerShell Universal instance and environment as topic 56022? If it is the same environment, we can associate this additional exception with the existing investigation and continue from the information already collected. If this is a different environment, please confirm: * PSU hosting method, such as Windows Service, IIS, or ZIP. * Server operating system. * Database type. * Whether the behavior affects all PSU users or only your account. Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread. References: https://forum.devolutions.net/topics/56022/error-clicking-column-selector-in-jobs-table Best regards, Ruben Tapia

Published a day ago

Roles/Permissions assignment not working

rubentapia this seems like a bug. Consider the following: [image] Whether the user has Execute permissions or not on the script seems to be irrelevant. Also, the failure behavior seems to be very inconsistent. The key contributors seem to be: The script has no tag or the tag is visible in the portal The script has a role assigned In the diagram Script Accessible references your ability to navigate directly to the script using `/portal/scripts/{ScriptName}` and execute the script. Script Is Listed refers to the script being listed on the portal home page either directly or via a Tag. Note that the script does not have to be listed to be accessible. This was tested on 2026.2.5

michaelhanson1458

Published a day ago

Sessions: add which node/computer the user is connected through.

[image]

Feature Request

michaelhanson1458

Published a day ago

Clicking Child Jobs shows blank page

Sent you the email.

michaelhanson1458

Published a day ago

Clicking on the column picker under jobs throws the following error.

[image]

Published a day ago

Apps restart when git runs, even though apps set not to auto deploy

Hello squinlan Thank you for the detailed report and screenshots. The timestamps are especially useful. I can see that the git pull operations launched by Universal.Server.exe are closely followed by the App startup sequence in several of the examples you provided. With Auto Deploy disabled, I would not expect an unchanged App to be unnecessarily restarted simply because a Git synchronization occurred, so I would like to narrow down what is triggering the reload. Could you please confirm the following? Are all Apps restarting, or only specific Apps such as InfraTools? Under Settings > Files > Configuration Changes, is automatic configuration reload enabled? What hosting method are you using for PSU 5.5.2, for example Windows Service, IIS, or ZIP? Is this a production environment, and do active users lose their sessions when the restart occurs? If the local and remote repositories are fully synchronized, does clicking Synchronize Now manually also restart the App when Git reports no changed files? Regarding your second question, PowerShell Universal provides Synchronize Now for manually triggering Git synchronization. Support for disabling scheduled synchronization by setting the Git sync interval to 0 was added in an earlier PSU release, so this may also be useful as a temporary diagnostic control while we investigate the unexpected App restarts. Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread. https://github.com/ironmansoftware/universal-docs/blob/v5/config/git.md Regards, Ruben Tapia

Published a day ago

White text box in code windows

Hello garryo Glad to hear you were able to get this resolved, and thank you for sharing what worked. It does appear the browser cache was responsible in this case, and a Ctrl+F5 refresh cleared the issue. Since you’ve confirmed everything is working normally now, I’ll mark this topic as resolved. Thanks again for the update. Best regards,

External resources

Devolutions Documentation

Technical SupportEmail : service@devolutions.netPhone : + 1 844 463.0419