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
cdabb9eb-7f73-41c5-93da-254c21dc0c69.png
All Comments (3)
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
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.
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