Jeremy Lippert

@Fumiaki Arita Is there an ETA for a resolution of this case from Microsoft?

Also seeing this if the user is a local administrator it seems as well. Your initial logged in user a local administrator?

@Rob Blokland We are seeing similar rdesvc Horizon Errors (Inside VDI, so Horizon agent side) after going to the latest Horizon Agents Installer 25.1.0 (Horizon 8.15, App Volumes 4.17, etc). We are only seeing this with a specific App Volumes package and only on user reconnect. We have an Omnissa case open for this, could be related, unknown.

Best feature of 2506 and something we have been waiting for almost 17 months now since being in HCNG. Something that gets a little closer to parity with Horizon 8 App Volumes: Helpdesk administrators can now view a user’s published application and App Volumes entitlements directly in the user card/Helpdesk view to assist the end-user with application issues.

Has anyone successfully implemented Cloud Cache? Everyone including Microsoft reps tell you to stay away from it. We attempted just last year and couldn't get it to work properly and consistently.

I was seeing this same behavior with the initial logged in admin user after the first initial just completely black screen, yeah. Apparently, you just continue to use the other admin user until its fixed

Yep, everyone eventually gave up and that was the solution we used for years for that environment. Had the InfoSec blessing.

Funny to find this thread, brings back memories. Story time: At a previous company we had CrowdStrike very early, maybe 2018/2019 or so, and we were trying to use it for our non-persistent Horizon environment and were seeing the same behavior with very long login times while using their agent. We had App Volumes, DEM, etc as well. They even flew a developer from overseas to our HQ to attempt to help after many months of a support ticket open. The end result was to disable the service on the image and have something (group policy, I think at the time) enable and start the service post user login. :)

As a temporary workaround to some recent Windows 11 issues with File Explorer, I was wondering the best way to use DEM (Logon Task or maybe Triggered Task) to restart Explorer post user login the simplest way. Was looking for some thoughts from others. Original thought was a Triggered Task via the (App Volumes Login-time apps delivered) trigger and have it run a custom command. Maybe Powershell to run stop-process on explorer, and it should restart? Anyone done this before and have a quick down and dirty way of doing it?

Things like this make me pretty salty though. Keep your Microsoft Teams in VDI client up to date to ensure the best user experience | Microsoft Community Hub Obviously as best practice with basically anything these days, I keep Teams up to date when touching an image but when Microsoft is starting to keep strict standards that are only 60-90 days and giving users prompts, that rubs me the wrong way. There are plenty of times when you need to slow down a roll out of something or pause it for issues and sometimes it takes multiple months to remediate/workaround...

This is exactly why we are still using Semi Annual Channel even though it seems like Microsoft no longer recommends it as the standard for enterprises.

Horizon Cloud Service - next-gen Release Notes

Been hesitate with 24H2 just because of all the issues that specific version has had in the past 6 months, plus it's only recently been supported with everything (OSOT, etc). Kind of getting sick of the amount of work it takes to get a solid non-persistent Windows 11 environment these days...

@ishki We have seen this behavior now when attempting to upgrade to the 2503 agents (Horizon Agent Installer 25.1.0) in Horizon Cloud next-gen. The behavior is the same, when reconnecting to an existing desktop session, is when specific users get the rdesvc message like you posted. I narrowed it down to a specific App Volumes package. In our case it was Tableau Client (with some other drivers and installations related to Tableau in this same package). I will be entering in a ticket for Omnissa support to assist with it.

Just kind of an FYI. Microsoft has changed the most recent Teams bootstrapper to uninstall and reinstall the system wide Teams Meeting Add-in (now requires a switch). For those of you that have non-persistent and you disable auto updates of Teams via the registry key. Learned this the hard way by utilizing the latest bootstrapper (per their recommendations) each time I update my images and didn't realize it rips off the TMA causing issues since there was no longer any TMA in Outlook. New Microsoft Teams for Virtuali...New Microsoft Teams for Virtualized Desktop Infrastructur...Learn about upgrading to the new Teams for Virtualized Desktop Infrastructure (VDI)