Mike_B

It worked! Thanks Paul (and Dennis). That was indeed the issue, just the monitor power saving setting in the master image. Took me a while to apply it due to maintenance windows, but all seems to work OK now. :)

Jeff, thanks for that. Mission accomplished late last night during a scheduled outage. There's a bit of a 'gotcha' though, when running the 'get-brokercatalog' command to see what it's set to currently, I found that machine catalogs set to '2206 or later' show up the same in Powershell as catalogs set to '2106 or later'. Both are listed as 'L7_25'. I set one of them back to the next lowest level, which is L7_20, and then it showed up in the DaaS console as '1811' for minimum functional level. But, once set to that, I could use the console to choose 2106 which is what I wanted. So, all good in the end. Just a bit confusing when you're looking at the list of MC names and functional levels, and they show up the same despite being different in the console. Hopefully that tidbit of info might be useful in future, if someone comes looking for the same info!

A few weeks ago I upgraded many of our catalogs to use the 2311 VDA. Since then, it's become apparent that the 2311 VDA is causing issues on multi-user catalogs (getting stuck on the Welcome screen when reconnecting - which I know was an issue in 2303 VDA, but was apparently fixed - seems not) but I'm unable to simply reinstall the older VDA (2203 CU4) as the catalog is now set to require 2206 or newer. When you first upgrade a catalog, there's a menu option to change the functional level back. However, that seems to disappear after a while. Is it possible to simply change it back using the Powershell SDK, or will that break things? My only other option is to build a new catalog with new VMs (they are MCS, so not hard in itself) but that will get the Operations team upset because the server names will all change.

We are really struggling to get the New Teams client to work on our estate. The deadline for moving over isn't really all that far away now but there is all kinds of stupid stuff broken with it still - 2019 Server doesn't work with FSLogix; we're fighting an issue where it doesn't get provisioned fully for new users on Win10; and if we take out Teams Classic then the Teams Add-in for Outlook doesn't work. If you're an existing user with Teams Classic in your profile, then it doesn't always load and start. I've been doing this stuff for almost 20 years and I've never seen such an badly thought through, broken piece of junk being forced onto people by it's vendor. Honestly, I've seen alpha software from one-man-band companies that is way more reliable than this. There's virtually no documentation from Citrix, Microsoft's exists but changes almost every day(but doesn't highlight what's new, and contains links to documentation for Teams Classic - useless), and even when you follow it to the letter, it flat-out doesn't work or contains mistakes like telling you to run 'msiexec.exe' with the /allusers switch on a single-OS machine. Or is it just me? Can someone with a big non-persistent estate tell me that it's all working fine for them? I need some light at the end of the tunnel...

I know this question is a while old, but we had the same issue using Wyse thin clients. The fix is in the configuration of the thin client itself - it is able to trap the Win-L keystroke, and locks the terminal itself with a password screen - completely resolves the issue. Hopefully HP has something similar, I'd be surprised if they didn't.

I don't suppose you remember what it was that got changed? I don't think we have power settings wrong (full power all the time) but happy to check if there are other, better settings.

Google links are working again now. I bitched at Citrix on LinkedIn right under their post announcing the new changes to Discussions, and somewhat to my surprise, they replied quite quickly and said that'd fixed it. Definitely a lot more links through from Google working now than earlier today...

I have recently tried to configure a screensaver on our Win11 catalogs but am running up against an issue where the display doesn't actually switch over to the lock screen. It remains on whatever was last shown to the user until they walked away, but as soon as they come back and move the mouse or press a key the screen immediately refreshes to the lock screen. Which is quite annoying - anyone can read what they last had on screen, but as soon as the user comes back, that's no use to them as they immediately have to unlock it. Any clues as to what might be wrong - how can I force a screen refresh so it updates to the lock screen at the timeout, rather than when the user returns?